Re: [LaTeXML] Fwd: Special TeX/LaTeX fonts in MathML (calligraphy vs. script)

Le 18/07/2014 00:21, David Carlisle a =E9crit :
> That's not an unreasonable position to take although (in the absence of
> an update to Unicode and matching updates to fonts, which would be years
> at least) that would mean that any document using a mathml fragment to
> be rendered in calligraphic would need at the document level to apply
> some css to achieve that. That's certainly less convenient for mathml
> generating tools (as basically it means they can't support calligraphic
> within the math expression) but I'm not strongly arguing that you should
> do differently as it is I agree a coherent position to take.
> But suggesting a class name can't hurt in any case as something like
> that would be needed in any case for other systems as I said. No need to
> highlight mathjax theer are many non css based systems Word for example.

Well, in that case the discussion and your proposal are clearly =

motivated by MathJax's specificity. But in general, there are many =

problems in the MathML specification due to the fact that the spec was =

written with non-css based systems in mind (before MathJax ever exists) =

or, depending on the point of view, due to the fact that browser vendors =

did not involve enough to influence the decisions. So I would personally =

not buy any argument around "this is needed to make it work with non css =

based systems". If calligraphic is considered something important then I =

believe it should be and should have been standardized like the other =

mathvariant attributes. Adding a temporary solution because the Math WG =

was not able to get that accepted before does not seem a very good way =

to handle the issue ; tools and implementers can just agree on such =

hacks themselves without having to put them explicitly in standards.

>
> when I said standardising class names was hardly a novel idea I was
> alluding   to
>
> http://microformats.org/
>
> and similar initiatives.
>
> you could make exactly the same objection against microformat
>
> <a  class=3D"h-card"  href=3D"http://benward.me">Ben Ward</a>
>
> that if a random user stylesheet has a selector for .h-card then odd
> things might happen.

As I understand, your "novel idea" is to make some class to suggest some =

specific rendering behavior without the use of CSS, not to just to =

indicate class names (anyway, I think Microformats are controversial and =

other people are suggesting using other methods to convey metadata). If =

instead it is just adding class names and explicitly saying that the =

rendering behavior is undefined and that they are just suggestions for =

possible stylistic use but that implementers are free to ignore that, =

then I won't mind but that just seems a vacuous statement that does not =

really help ensuring cross-compatible rendering.

-- =

Fr=E9d=E9ric Wang
maths-informatique-jeux.com/blog/frederic