Bug 4785 - SVG Issue:some files don't bind the default namespace
Summary: SVG Issue:some files don't bind the default namespace
Alias: None
Product: openclipart.org
Classification: Unclassified
Component: clipart (show other bugs)
Version: unspecified
Hardware: All All
: high normal
Assignee: default user for a product
QA Contact:
Depends on:
Reported: 2005-10-16 11:31 UTC by Stephen Silver
Modified: 2010-08-18 03:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

list of files in release 0.18 with this problem (56.08 KB, text/plain)
2005-10-16 11:35 UTC, Stephen Silver

Description Stephen Silver 2005-10-16 11:31:25 UTC
SVG files should bind the default namespace (and should not just rely on the DTD
to do this, since non-validating parsers need not read the DTD). See the
discussion on the OCAL mailing list


and this Mozilla bug:


So SVG files in the OCAL collection that don't do this need to be fixed. A list
of these files can be obtained using my SVGscan script


by running

  python svgscan.py -none -warn=no_namespace .

in the top clipart directory. In release 0.18 there are 240 such files, not
counting the 1375 star_*step.svg files.
Comment 1 Stephen Silver 2005-10-16 11:35:19 UTC
Created attachment 3565 [details]
list of files in release 0.18 with this problem
Comment 2 ryanlerch 2006-10-12 22:02:19 UTC
encompassed by the new feature request - https://bugs.freedesktop.org/
Comment 3 Ruud Steltenpool 2006-12-19 13:54:27 UTC
This can be very easily fixed well in advance of proper SVG validation on upload.

Can't some maintainer (code and then) run the following and fix many, if not all
problem files:

if ($SVGnamespaceURL isn't substring of fileContent, but "<svg" is exactly once){
        replace '<svg' with '<svg xmlns="$SVGnamespaceURL"'

Comment 4 Tollef Fog Heen 2010-08-18 03:23:32 UTC
Closing all openclipart bugs as openclipart is now on launchpad, as per request from  Jon Philips.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.