Skip to the Main Content

Note:These pages make extensive use of the latest XHTML and CSS Standards. They ought to look great in any standards-compliant modern browser. Unfortunately, they will probably look horrible in older browsers, like Netscape 4.x and IE 4.x. Moreover, many posts use MathML, which is, currently only supported in Mozilla. My best suggestion (and you will thank me when surfing an ever-increasing number of sites on the web which have been crafted to use the new standards) is to upgrade to the latest version of your browser. If that's not possible, consider moving to the Standards-compliant and open-source Mozilla browser.

May 2, 2007

SVG Redux

In a previous post, I announced support for inline SVG in posts and comments on the blogs I host here on Golem. Unfortunately, to be compatible with the built-in copy of the W3C Validator, the SVG had to adhere to the idiotic restrictions of the W3C profile for XHTML+MathML+SVG. Which was a problem, if you wanted to avail yourself of GUI tools, like Inkscape or to reuse much of the SVG that’s available on the 'net.

Sam Ruby suggested some code to convert Namespace well-formed XHTML+MathML+SVG into the format demanded by the W3C Validator. I added a couple of tweaks, and rolled the result into a MovableType plugin.

So, now, you don’t need to add completely superfluous svg: prefixes to your SVG code. The plugin will handle the conversions necessary to keep the W3C Validator happy.

1 These restrictions are the result of letting the limitations of your conformance-checking tool dictate how your Specification gets written, rather than the other way around. As long as a compound document is Namespace well-formed, there shouldn’t be any further restrictions on how, precisely, the SVG, MathML and XHTML namespaces are declared.

Posted by distler at May 2, 2007 10:04 AM

TrackBack URL for this Entry:

0 Comments & 1 Trackback

Read the post SVG Comments
Weblog: Musings
Excerpt: Kicking it up a notch.
Tracked: May 17, 2007 6:03 PM

Post a New Comment