Bug #1446209 “cannot produce valid HTML5 <svg ...> element...” : Bugs : Inkscape

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#1

Example html file containing SVG that generated above validator errors Edit (17.4 KiB, text/html)

Example html file containing SVG that generated above validator errors

su_v (suv-lp) on 2015-04-20

tags:	added: exporting
tags:	removed: exporting

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#2

Download full text (67.4 KiB)

Matters are not helped by changing the DOCTYPE to xhtml 1.1 + MathML 2.0 + SVG 1.1 :
Validation Output: 71 Errors

Error Line 17, Column 68: there is no attribute "xmlns"

….org/1999/02/22-rdf-syntax-ns#" xmlns="http://www.w3.org/2000/svg" height="100…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Error Line 17, Column 104: there is no attribute "height"

…s="http://www.w3.org/2000/svg" height="100mm" width="200mm" version="1.1" xmln…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Error Line 17, Column 118: there is no attribute "width"

…w3.org/2000/svg" height="100mm" width="200mm" version="1.1" xmlns:cc="http://c…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired...

Matters are not helped by changing the DOCTYPE to xhtml 1.1 + MathML 2.0 + SVG 1.1 :
Validation Output: 71 Errors

Error Line 17, Column 68: there is no attribute "xmlns"

….org/1999/02/22-rdf-syntax-ns#" xmlns="http://www.w3.org/2000/svg" height="100…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 17, Column 104: there is no attribute "height"

…s="http://www.w3.org/2000/svg" height="100mm" width="200mm" version="1.1" xmln…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 17, Column 118: there is no attribute "width"

…w3.org/2000/svg" height="100mm" width="200mm" version="1.1" xmlns:cc="http://c…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 17, Column 134: there is no attribute "version"

… height="100mm" width="200mm" version="1.1" xmlns:cc="http://creativecommons.o…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 17, Column 234: there is no attribute "viewBox"

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 17, Column 259: element "svg" undefined

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 18, Column 7: element "defs" undefined

<defs>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 19, Column 14: there is no attribute "id"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 19, Column 23: there is no attribute "refY"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 19, Column 34: there is no attribute "refX"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 19, Column 46: there is no attribute "style"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 19, Column 72: there is no attribute "orient"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 19, Column 78: element "marker" undefined

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 20, Column 16: there is no attribute "style"

<path style="stroke-linejoin:round;fill-rule:evenodd;stroke:#000000;stroke-w…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 20, Column 114: there is no attribute "transform"

…ke-width:.625;fill:#f2f2f2" transform="scale(1.1) rotate(180) translate(1)" d=…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 20, Column 154: there is no attribute "d"

…cale(1.1) rotate(180) translate(1)" d="m8.7186 4.0337l-10.926-4.0177 10.926-4.…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 20, Column 239: element "path" undefined

…6 4.0337l-10.926-4.0177 10.926-4.0177c-1.7455 2.3721-1.7355 5.6174 0 8.0354z"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 22, Column 78: element "marker" undefined

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 23, Column 185: element "path" undefined

…6 4.0337l-10.926-4.0177 10.926-4.0177c-1.7455 2.3721-1.7355 5.6174 0 8.0354z"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 25, Column 14: there is no attribute "id"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 25, Column 24: there is no attribute "style"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 25, Column 58: element "filter" undefined

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 26, Column 26: there is no attribute "values"

<feColorMatrix values="1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 -0.21 -0.72 -0.07 2 0 "…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 26, Column 88: there is no attribute "result"

… 0 0 0 0 0 1 0 0 0 0 0 1 0 0 -0.21 -0.72 -0.07 2 0 " result="fbSourceGraphic"/>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 26, Column 106: element "feColorMatrix" undefined

… 0 0 0 0 0 1 0 0 0 0 0 1 0 0 -0.21 -0.72 -0.07 2 0 " result="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 27, Column 104: there is no attribute "in"

…-1 0 0 0 0 -1 0 0 0 0 1 0" result="fbSourceGraphicAlpha" in="fbSourceGraphic"/>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 27, Column 122: element "feColorMatrix" undefined

…-1 0 0 0 0 -1 0 0 0 0 1 0" result="fbSourceGraphicAlpha" in="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 28, Column 127: element "feColorMatrix" undefined

…1 0 0 0 1 0 -1 0 0 1 0 0 -1 0 1 0.21 0.72 0.07 1 0 " result="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 29, Column 122: element "feColorMatrix" undefined

…-1 0 0 0 0 -1 0 0 0 0 1 0" result="fbSourceGraphicAlpha" in="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 30, Column 127: element "feColorMatrix" undefined

…1 0 0 0 1 0 -1 0 0 1 0 0 -1 0 1 0.21 0.72 0.07 1 0 " result="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 31, Column 122: element "feColorMatrix" undefined

…-1 0 0 0 0 -1 0 0 0 0 1 0" result="fbSourceGraphicAlpha" in="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 32, Column 127: element "feColorMatrix" undefined

… 0 1 0 0 0 1 0 0 0 1 0 0 0 0 -0.21 -0.72 -0.07 2 0 " result="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 33, Column 122: element "feColorMatrix" undefined

…-1 0 0 0 0 -1 0 0 0 0 1 0" result="fbSourceGraphicAlpha" in="fbSourceGraphic"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 34, Column 118: element "feColorMatrix" undefined

…values="1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 -0.21 -0.72 -0.07 2 0 " result="color2"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 37, Column 11: element "metadata" undefined

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 38, Column 11: element "rdf:RDF" undefined

<rdf:RDF>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 39, Column 23: there is no attribute "rdf:about"

<cc:Work rdf:about="">

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 39, Column 25: element "cc:Work" undefined

<cc:Work rdf:about="">

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 40, Column 15: element "dc:format" undefined

<dc:format>image/svg+xml</dc:format>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 41, Column 27: there is no attribute "rdf:resource"

<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 41, Column 68: element "dc:type" undefined

<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 42, Column 15: element "dc:title" undefined

<dc:title/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 46, Column 15: there is no attribute "transform"

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 46, Column 37: element "g" undefined

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 47, Column 15: there is no attribute "style"

<text style="font-size:12.5px;font-family:&apos;Andale Mono&apos;;fill:#fffff…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 47, Column 146: there is no attribute "xml:space"

…acing:0px;line-height:125%" xml:space="preserve" y="898.07648" x="88.571426"><…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 47, Column 159: there is no attribute "y"

…e-height:125%" xml:space="preserve" y="898.07648" x="88.571426"><tspan x="88.5…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 47, Column 173: there is no attribute "x"

… xml:space="preserve" y="898.07648" x="88.571426"><tspan x="88.571426" y="898.…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 47, Column 184: element "text" undefined

…"preserve" y="898.07648" x="88.571426"><tspan x="88.571426" y="898.07648"/></t…

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 47, Column 194: there is no attribute "x"

…eserve" y="898.07648" x="88.571426"><tspan x="88.571426" y="898.07648"/></text>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 47, Column 208: there is no attribute "y"

…eserve" y="898.07648" x="88.571426"><tspan x="88.571426" y="898.07648"/></text>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 47, Column 220: element "tspan" undefined

…eserve" y="898.07648" x="88.571426"><tspan x="88.571426" y="898.07648"/></text>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 48, Column 23: there is no attribute "xml:space"

<flowRoot xml:space="preserve" style="font-size:12.5px;font-family:&apos;Anda…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 48, Column 40: there is no attribute "style"

… <flowRoot xml:space="preserve" style="font-size:12.5px;font-family:&apos;Anda…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 48, Column 174: element "flowRoot" undefined

…ight:125%;word-spacing:0px;fill:black"><flowRegion><rect y="117.19" width="108…

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 48, Column 186: element "flowRegion" undefined

…rd-spacing:0px;fill:black"><flowRegion><rect y="117.19" width="108.57" x="57.1…

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 48, Column 195: there is no attribute "y"

…g:0px;fill:black"><flowRegion><rect y="117.19" width="108.57" x="57.143" heigh…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 48, Column 210: there is no attribute "width"

…k"><flowRegion><rect y="117.19" width="108.57" x="57.143" height="160"/></flow…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 48, Column 221: there is no attribute "x"

…ion><rect y="117.19" width="108.57" x="57.143" height="160"/></flowRegion><flo…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 48, Column 237: there is no attribute "height"

….19" width="108.57" x="57.143" height="160"/></flowRegion><flowPara/></flowRoo…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 48, Column 243: element "rect" undefined

…19" width="108.57" x="57.143" height="160"/></flowRegion><flowPara/></flowRoot>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 48, Column 267: element "flowPara" undefined

…19" width="108.57" x="57.143" height="160"/></flowRegion><flowPara/></flowRoot>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 49, Column 183: element "text" undefined

…="preserve" y="886.64795" x="82.85714"><tspan x="82.85714" y="886.64795"/></te…

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 49, Column 218: element "tspan" undefined

…preserve" y="886.64795" x="82.85714"><tspan x="82.85714" y="886.64795"/></text>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 50, Column 168: there is no attribute "transform"

…:125%" xml:space="preserve" transform="scale(1.0918 .91590)" y="1046.0537" x="…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Error Line 50, Column 218: element "text" undefined

…8 .91590)" y="1046.0537" x="17.819574"><tspan x="17.819574" y="1046.0537">A </…

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 50, Column 253: element "tspan" undefined

…="1046.0537" x="17.819574"><tspan x="17.819574" y="1046.0537">A </tspan></text>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 51, Column 219: element "text" undefined

…6 .93062)" y="1041.7878" x="491.08682"><tspan x="491.08682" y="1041.7878">B</t…

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 51, Column 254: element "tspan" undefined

…y="1041.7878" x="491.08682"><tspan x="491.08682" y="1041.7878">B</tspan></text>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 52, Column 135: element "path" undefined

…opacity:0;fill-opacity:0" d="m142.86 832.36c382.85 0 377.14-2.85 377.14-2.85"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Error Line 53, Column 152: element "path" undefined

…-linecap:round;stroke-width:10;fill:#f2f2f2" d="m162.86 889.51l365.71 2.8571"/>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
        incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
        by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
        by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#3

XHTML 1.1 + MathML 2.0 + SVG 1.1 version that generates errors Edit (4.5 KiB, application/xhtml+xml)

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#4

HTML-5 version of same also giving errors Edit (4.2 KiB, text/html)

Errors from HTML 5 version :

Info Using experimental feature: HTML5 Conformance Checker.

The validator checked your document with an experimental feature: HTML5 Conformance Checker. This feature has been made available for your convenience, but be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies. If you find any issues with this feature, please report them. Thank you.

↑ Top
Validation Output: 5 Errors

Error Line 12, Column 259: Attribute xmlns:rdf not allowed here.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
Warning Line 12, Column 259: Attribute with the local name xmlns:rdf is not serializable as XML 1.0.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
Error Line 12, Column 259: Attribute xmlns:cc not allowed here.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
Warning Line 12, Column 259: Attribute with the local name xmlns:cc is not serializable as XML 1.0.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
Error Line 12, Column 259: Attribute xmlns:dc not allowed here.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
Warning Line 12, Column 259: Attribute with the local name xmlns:dc is not serializable as XML 1.0.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
Warning Line 33, Column 11: Element name rdf:rdf cannot be represented as XML 1.0.

<rdf:RDF>

✉
Error Line 33, Column 11: Element rdf:rdf not allowed as child of element metadata in this context. (Suppressing further errors from this subtree.)

<rdf:RDF>

✉
Warning Line 34, Column 25: Attribute rdf:about is not serializable as XML 1.0.

<cc:Work rdf:about="">

✉
Warning Line 34, Column 25: Element name cc:work cannot be represented as XML 1.0.

<cc:Work rdf:about="">

✉
Warning Line 35, Column 15: Element name dc:format cannot be represented as XML 1.0.

<dc:format>image/svg+xml</dc:format>

✉
Warning Line 36, Column 68: Attribute rdf:resource is not serializable as XML 1.0.

<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>

✉
Warning Line 36, Column 68: Element name dc:type cannot be represented as XML 1.0.

<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>

✉
Warning Line 37, Column 15: Element name dc:title cannot be represented as XML 1.0.

<dc:title/>

✉
Error Line 43, Column 174: Element flowroot not allowed as child of element g in this context. (Suppressing further errors from this subtree.)

…ight:125%;word-spacing:0px;fill:black"><flowRegion><rect y="117.19" width="108…

Errors from HTML 5 version :

Info Using experimental feature: HTML5 Conformance Checker.

The validator checked your document with an experimental feature: HTML5 Conformance Checker. This feature has been made available for your convenience, but be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies. If you find any issues with this feature, please report them. Thank you.

↑ Top
Validation Output: 5 Errors

Error Line 12, Column 259: Attribute xmlns:rdf not allowed here.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
    Warning Line 12, Column 259: Attribute with the local name xmlns:rdf is not serializable as XML 1.0.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
    Error Line 12, Column 259: Attribute xmlns:cc not allowed here.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
    Warning Line 12, Column 259: Attribute with the local name xmlns:cc is not serializable as XML 1.0.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
    Error Line 12, Column 259: Attribute xmlns:dc not allowed here.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
    Warning Line 12, Column 259: Attribute with the local name xmlns:dc is not serializable as XML 1.0.

…xmlns:dc="http://purl.org/dc/elements/1.1/" viewBox="0 0 708.66142 354.33071">

✉
    Warning Line 33, Column 11: Element name rdf:rdf cannot be represented as XML 1.0.

<rdf:RDF>

✉
    Error Line 33, Column 11: Element rdf:rdf not allowed as child of element metadata in this context. (Suppressing further errors from this subtree.)

<rdf:RDF>

✉
    Warning Line 34, Column 25: Attribute rdf:about is not serializable as XML 1.0.

<cc:Work rdf:about="">

✉
    Warning Line 34, Column 25: Element name cc:work cannot be represented as XML 1.0.

<cc:Work rdf:about="">

✉
    Warning Line 35, Column 15: Element name dc:format cannot be represented as XML 1.0.

<dc:format>image/svg+xml</dc:format>

✉
    Warning Line 36, Column 68: Attribute rdf:resource is not serializable as XML 1.0.

<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>

✉
    Warning Line 36, Column 68: Element name dc:type cannot be represented as XML 1.0.

<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>

✉
    Warning Line 37, Column 15: Element name dc:title cannot be represented as XML 1.0.

<dc:title/>

✉
    Error Line 43, Column 174: Element flowroot not allowed as child of element g in this context. (Suppressing further errors from this subtree.)

…ight:125%;word-spacing:0px;fill:black"><flowRegion><rect y="117.19" width="108…

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#5

So I can't get any HTML document containing any SVG produced by either SVG-Edit or Inkscape through the W3 HTML validator without errors .
Is there any SVG editor that can produce documents that pass the W3C's validation tests ?

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#6

ab1.xhtml Edit (3.4 KiB, application/xhtml+xml)

OK, I see what the problem is now .

The attached document is a version of ab1.xhtml that validates OK against the W3C's "XHTML 1.1 plus MathML 2.0 plus SVG 1.1" DTD
( "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd" ) .

It is changed from the SVG produced by Inkscape in the inclusion of 'svg:' namespace prefixes on every svg tag name.

Is there a way to get Inkscape to use 'svg:' prefixes on svg element attributes and tag names ?

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#7

It is a rather tedious, non-trivial and error prone job to strip out the unsupported syntax and add all the missing 'svg:' prefixes to tag names .
Why does the validator require these namespace prefixes, are they mandated by the SVG standard, if so why does Inkscape not comply with
it by default ? Is there any way of getting Inkscape to use these 'svg:' namespace prefixes ?

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#8

edited version that passes W3 validation as HTML5 Edit (3.1 KiB, text/html)

Here is the HTML5 passing version . You cannot use ANY namespace prefixes or extra namespaces in the svg element attributes in HTML5 ,
unless you change the doctype to XHTML ( then it is a not an HTML5 document).
Can Inkscape be made to produce valid HTML5 svg elements (ie. without namespace references or prefixes used) ?

Revision history for this message

JVD (jason-vas-dias) wrote on 2015-04-20:

#9

It doesn't seem possible to get Inkscape to either entirely not use XML namespaces (for HTML5) or use them only with appropriate prefixes (XHTML 1.1 + SVG + MathML) - so what standard HTML doctype + DTD should I use to include SVG produced by Inkscape ?

Revision history for this message

jazzynico (jazzynico) wrote on 2015-05-11:

#10

Some details on inline SVG: http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Web-Use.html#Web-Use-Inline

Did you create the document with Inkscape?
Some of the errors reported by the w3c validator (inappropriate "text-align" attributes in text elements, invalid "se_type" attributes in marker elements and invalid "null" values in stroke-linecap and stroke-linejoin attributes) are apparently due to an external tool.

su_v (suv-lp) on 2015-10-08

tags:

added: exporting svg

Inkscape

cannot produce valid HTML5 <svg ...> elements

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Inkscape

cannot produce valid HTML5 &lt;svg ...&gt; elements

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

cannot produce valid HTML5 <svg ...> elements