SVG:Namespace: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎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=

Revision as of 11:57, 8 October 2005

Declare namespaces for SVG and XLink

The namespace declaration for SVG is required. If you don't specify it, nothing will be rendered. The XLink namespace is required if you use <use/>, <image/>, <a/> ...

A simple SVG file may look like this:

<?xml version="1.0" standalone="no"?>
<svg xmlns="http://www.w3.org/2000/svg" 
    xmlns:xlink="http://www.w3.org/1999/xlink">
 <title>title of drawing</title>

</svg>

Declare DOCTYPE for SVG

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">

use namespace-aware methods in javascript

when using js, make sure you use the namespace aware methods like:

  • getElementsByTagNameNS()
  • createElementNS()
  • setAttributeNS()
  • getAttributeNS()
  • ...

svg elements are in the svg namespace. Unqualified svg attributes are in the null namespace. Qualified attributes are in whatever namespace their prefix id declared as - so for example xlink:href is in the XLink namespace, http://www.w3.org/1999/xlink.

For example, to dynamically create an <image> element, do it like this:

const svgns="http://www.w3.org/2000/svg";
const xlinkns="http://www.w3.org/1999/xlink";
var newIM=document.createElementNS(svgns,"image");
newIM.setAttributeNS(null,"width",100);
newIM.setAttributeNS(null,"height",100);
newIM.setAttributeNS(xlinkns,"href","bild2.png");


Links

SVG:Home Page