SVG:Namespace: Difference between revisions

Jump to navigation Jump to search
→‎Declare DOCTYPE for SVG: no response on discussion, so left the rumor as "unconfirmed"
(→‎Declare DOCTYPE for SVG: this should never be required)
(→‎Declare DOCTYPE for SVG: no response on discussion, so left the rumor as "unconfirmed")
Line 17: Line 17:
== Declare DOCTYPE for SVG ==
== Declare DOCTYPE for SVG ==


Similarly, declaring a correct DOCTYPE for .svg files may be important as well, instances have been observed where an SVG file without namespace and incorrect doctype did work in Adobe SVG, but with the namespace added it didn’t work, until the DOCTYPE was corrected as well. The doctype is supposed to be:
Similarly, declaring a correct DOCTYPE for .svg files may be useful for DTD validation. Thic can catch some, but not all errors and is a useful supplement to well-formedness checking.
 
''There are uncomfirmed reports that  an SVG file without namespace and incorrect doctype did work in Adobe SVG, but with the namespace added it didn’t work, until the DOCTYPE was corrected as well.''
 
The doctype for SVG 1.1 Full is:


  <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
  <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
This should solve the cases where the addition of the namespaces required by Mozilla breaks rendering with Adobe SVG.


= use namespace-aware methods in javascript=
= use namespace-aware methods in javascript=

Navigation menu