Re: [LaTeXML] Fwd: Special TeX/LaTeX fonts in MathML (calligraphy vs. script)
David Carlisle <[email protected]> Thu, 17 Jul 2014 01:42:02 +0100
| Newsgroups | gmane.comp.mozilla.devel.mathml |
|---|---|
| Message-ID | <[email protected]> |
On 16/07/2014 22:44, Fr=E9d=E9ric Wang wrote: > It's because you are talking about the syntax of the MathML markup = > while I'm talking about its semantics. AFAIK, using a class name = > "MJX-..." to change the rendering behavior of elements other than by = > CSS styling is non-standard =3D not defined in any standard. = It's not defined by MathML but it is explicitly not defined (thus = allowed) by MathML, the definition of class(in 2.1.6) is > Associates the element with a set of style classes for use with = [XSLT] and [CSS21]. > Typically this would be a space separated sequence of words, but this = is not specified by MathML. so it explicitly sanctions XSLT transforms rather than css to pick up = the class: times and language fashions change, but using javascript rather than = xslt isn't really any different. If different systems are using <mi class=3D"wibble" mathvariant=3D"script">= = to distinguish calligraphic rather than script, then some kind of note or even informal agreement to use the same class = names is probably a pragmatic solution. whether they use css or c++ or javascript to cause that class attribute = to have any effect isn't really the concern of the MathML spec. From the mathml spec viewpoint that's really saying that a script A and = calligraphic A are the "same" but one is just styled differently In some cases that is definitely a reasonable description of reality. = I'm sure though there are some documents that use the two alphabets in an intentionally distinct manner. using class for that is = arguably less than ideal however the alternative of getting a new calligraphic alphabet added to unicode and (perhaps) a new = calligraphic mathvariant to match , and then getting fonts updated to use the new Unicode code has lots of procedural and time = disadvantages, it would take years to get deployed and if used would probably have bad fallback in systems without updated fonts. That's not = to say it shouldn't be attempted. Especially if browser and font implementers all asked for that, and there were published documents = using both forms in the same expression.... David