A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Talk:New Vocabularies: Difference between revisions
Danaleeling (talk | contribs) (Authors will learn and use MathMl, SVG in web pages) |
No edit summary |
||
| Line 1: | Line 1: | ||
I hand author MathMl and SVG in XHTML pages. Most recently FireFox 3 added the ability to display [http://www.comfsm.fm/~dleeling/tech/mathml-in-svg.xhtml mathml in svg in xhtml] - nested XML namespaces. The languages can and will be learned by many like me who generate math and science materials for academic web sites. Since I author HTML5 using essentially HTML 4.01 strict standards, I can fairly easily shift from an HTML5 compliant document to an XHTML+MathMl+SVG compliant document. This is neither hard nor scary. I suspect the real issue is the draconian error handling that XHTML+MathMl+SVG brings with it, and may be why many authors want to see MathMl and SVG namespaces in HTML. That is an implementor issue, however, and not a language issue. It seems to this naive person that an implementor could choose other options besides a "yellow screen of death" simply because an img tag was not closed/terminated properly. | I hand author MathMl and SVG in XHTML pages. Most recently FireFox 3 added the ability to display [http://www.comfsm.fm/~dleeling/tech/mathml-in-svg.xhtml mathml in svg in xhtml] - nested XML namespaces. The languages can and will be learned by many like me who generate math and science materials for academic web sites. Since I author HTML5 using essentially HTML 4.01 strict standards, I can fairly easily shift from an HTML5 compliant document to an XHTML+MathMl+SVG compliant document. This is neither hard nor scary. I suspect the real issue is the draconian error handling that XHTML+MathMl+SVG brings with it, and may be why many authors want to see MathMl and SVG namespaces in HTML. That is an implementor issue, however, and not a language issue. It seems to this naive person that an implementor could choose other options besides a "yellow screen of death" simply because an img tag was not closed/terminated properly. | ||
: "an implementor could choose other options" [https://bugzilla.mozilla.org/show_bug.cgi?id=418305 Agreed]. Opera already does a decent job (even giving you the option to re-parse the page as HTML. [[User:Jeff schiller|Jeff schiller]] 16:42, 25 March 2008 (UTC) | |||
Revision as of 16:42, 25 March 2008
I hand author MathMl and SVG in XHTML pages. Most recently FireFox 3 added the ability to display mathml in svg in xhtml - nested XML namespaces. The languages can and will be learned by many like me who generate math and science materials for academic web sites. Since I author HTML5 using essentially HTML 4.01 strict standards, I can fairly easily shift from an HTML5 compliant document to an XHTML+MathMl+SVG compliant document. This is neither hard nor scary. I suspect the real issue is the draconian error handling that XHTML+MathMl+SVG brings with it, and may be why many authors want to see MathMl and SVG namespaces in HTML. That is an implementor issue, however, and not a language issue. It seems to this naive person that an implementor could choose other options besides a "yellow screen of death" simply because an img tag was not closed/terminated properly.
- "an implementor could choose other options" Agreed. Opera already does a decent job (even giving you the option to re-parse the page as HTML. Jeff schiller 16:42, 25 March 2008 (UTC)