301125 - SVG files XML Parsing Error - no display

Status: RESOLVED INVALID

(Core :: SVG, defect)

Description

[EKriss]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+

See also discussion on firefox builds forum "DEER PARK SVG PROBLEMS".  Simply
put, Deer Park 2 does not display the vast majority of svg files on the
internet.  A few examples display properly, but most have an error similar to this:

XML Parsing Error: not well-formed
Location: http://www.adobe.com/svg/demos/svgfiles/dancing_line.svgz
Line Number 1, Column 1:

Reproducible: Always

Steps to Reproduce:
1. go to http://workmode.com/1010.svg
2.
3.

Actual Results:  
GOT THIS MESSAGE:

XML Parsing Error: prefix not bound to a namespace
Location: http://www.workmode.com/1010.svg
Line Number 1620, Column 1:<use x="0" y="0" xlink:href="#Paper"
style="stroke:Ivory;fill:None;stroke-width:0.005" />
^

Expected Results:  
Should have been a CAD drawing display

Comment 1

[crf]

Link to the ff builds forum thread mentioned:
http://forums.mozillazine.org/viewtopic.php?t=275020

Comment 2

[Scooter Morris]

This is an appropriate error -- you have not defined the xlink namespace, but
you have used it in your <use>.  Also note that your fonts probably won't look
as you expect them to because you are attempting to use unitless values in your
CSS.  The CSS specification explicitly forbids unitless values, so you are
getting parse errors.  There are two ways to fix this: 1) change your font-size
to include units (e.g. 1.9px), 2) use font-size attributes rather than CSS
properties.  

Comment 3

[Jonathan Watt [:jwatt]]

This bug is invalid I'm afraid. Adobe's SVG Viewer doesn't have to deal with XML
properly so it doesn't. Lots of other people - us for example - do. I've
contacted high profile Adobe staff members about the errors in the SVG content
on their site on several occasions, but so far they haven't fixed them. As
Scooter says, Firefox is showing you there's a problem with the SVG here, not
the other way around.

For info on the issue you've encountered and the (easy) fix see:
http://jwatt.org/svg/authoring/#namespace-binding