https://bugzilla.redhat.com/show_bug.cgi?id=1026871
--- Comment #7 from Nicolas Mailhot nicolas.mailhot@laposte.net --- (In reply to Elliott Sales de Andrade from comment #6)
(In reply to Nicolas Mailhot from comment #4)
I read this as "browsers do not want to update their code to work with Stix
1.0"
No, MathJax asks for 1.0, and fontconfig gives it 1.1, which is incompatible. If MathJax had asked for *any* version, then it would be a bug in MathJax, but it didn't.
Sorry, that was a typo on my part. Should have written 1.1 here.
Well, this is a browser bug. Upstream stix changed to take into account issues reported after their .0 release, it fixed actual correctness bugs and problems indentified in big apps such as office suites, it took it months of work and there's not way upstream is going back now
Upstream does not ship these aliases. If you look at the release notes, you see that several glyphs have changed locations, making these fonts incompatible. The aliases are purely a Fedora thing.
I know that 1.1 has been restructured to fix various compatibility and spec problems. The aliases are not expected to provide full compatibility because you can only do so much at fontconfig level. But they are good enough for most simple documents.
The point is, 1.0 stix structure is obsolete and dead upstream, it's high time Mathjax adapted, and I won't create another TEX-like morass in Fedora with piles of obsolete fonts kept around to help code that does not want to update and does not feel the need to update because the obsolete parts are kept around by distributors.
Stix upsteam was very clear when they released 1.0 that it was not finished and that they would perform heavy changes in the near future. Mathjx had more than three years to fix itself now.