New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: TeX \liminf
procudes invalid SVG output / treatment of known-unkown chars
#6
Comments
same for \S. |
Thanks. (This issue actually confuses me; I thought our policy was to not support macros that our font's don't cover). One workaround is to switch to STIX fonts. |
Any updates here? |
Thanks for reminding us. I've reported this upstream on MathJax's issue tracker as it's not MathJax-node specific. (Unless you mean the problem with tex2svg's output -- that should probably move to a separate issue on MathJax-node.) |
The most complete test that we have in Wikipedia |
I don't think they're related. The original posting was about a) SVG that works but does not validate due to empty attributes a) is an upstream issue with MathJax b) is a MathJax-node issue (albeit a minor one since tex2svg is just an example and the actual output is generated just not printed to the command line). Could you file a separate issue and provide some background? I don't see how MathJax-node could generate that message unless TeX is processed as MathML. |
Just for future reference A list of all errors I see for Latin-Modern:
All those should be fixed before, we can use Latin-Modern for wikipedia. |
These errors (soon to be warnings) tell you which Unicode characters are not covered by the Latin Modern font, so they are expected behavior (unless you mean to report that the SVG output is missing characters that ARE in the original Latin Modernfonts in which case this would be an upstream bug with MathJax.). |
Several of these are actually problems in the LatinModern fonts. For example, the Fraktur problems at the bottom are due to the LatinModernMathJax_Fraktur font not including several Fraktur characters from the Letterlike Symbols. Some were included, but some not (I'm not sure why Fred didn't include them; probably an oversight). They are in one of the other fonts, but it was not included in the search path for the Fraktur font (I did point out that the search list wasn't complete for these fonts, but nothing was done about it). These issues can be fixed in the font data files (without needing to update the fonts). Others are (as you indicate) limitations of the LatinModern fonts, which don't include some symbols that are in the MathJax fonts. There is no easy solution other than going to the STIX fonts for better coverage. |
I've created mathjax/MathJax#904 to track the part of this that we can fix. Again this issues is not about these error messages or missing font support -- it is about (very slightly) invalid SVG due to empty attributes where SVG expects non-empty ones (and that part is also an upstream issue). |
I've included a fix for the empty attributes in the SVG output for missing characters in mathjax/MathJax#898. (It also fixes the space problem.) |
It is, but the |
I'm closing this as fixed, since the MathJax issue 904 now covers the remaining content of this issue. |
This is more of a MathJax-core issue but I wasn't sure how to file it so I wanted to discuss this here first.
Issue Summary
Converting
\liminf
leads to invalid SVG.(Also,
tex2svg
does not produce output if unknown characters are reported.)Steps to Reproduce
\liminf
to SVG will contain<text transform="scale(53.81925) matrix(1 0 0 -1 0 0)" stroke="none" font-weight="" font-style="" font-family="STIXGeneral,'Arial Unicode MS',serif"> </text>
which is invalid sincefont-weight
andfont-style
are empty.IIUC, the problem is that converting TeX input
\liminf
to MathML producesu+2006
which is not covered by the MathJax TeX fonts (at least according to the error message of the SVG output) but also (in the output) not converted into characters that are covered. In turn, this unknown characters is causing thetext
tag.The text was updated successfully, but these errors were encountered: