-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Enabling mathbbm or support mathbb for numbers #792
Comments
Thanks for the feature request. As with |
Well, I understand that technical difficulties would be around the corner, and this is far from a priority. I just wanted to let you know this would be cool to have. |
@jerskouille thanks for your kind words. You could definitely write an extension if you want (and contribute it to our third party extension repository). That way, people can use it via our CDN. A simple extension would just mapp to unicode characters (hoping that most systems will have a font with those characters, which is not too unlikely). An advanced extension could included its own font+fontdata, I suppose, and eventually find its way into the MathJax core. |
Has there been any progress since two years? At least an extension? |
This has come up on meta.math.SE recently here and the short of it is that the unicode extension works: |
The HTML-CSS output renderer tries to avoid downloading fonts over the web, so it detects whether you have the MathJax TeX fonts or STIX fonts installed locally and uses one of those if you do. MacOS comes with STIX fonts installed, so you will end with those being used unless you have taken steps to disable the STIX fonts. You can check which fonts are used by selecting the "About MathJax" item in the MathJax contextual menu. The MathJax fonts are fairly limited (so that they are smaller for downloading), but the STIX fonts are more complete, and they do include the blackboard-bold numerals (while the MathJax TeX fonts do not). That means on your Mac, with the HTML-CSS output renderer, you will get properly rendered double-struck numerals. Checking the local fonts for STIX fonts was a nice idea, but id did lead to the fact that different people would see different things, like in your case, so this idea was abandoned in the later output formats. The CommonHTML output only uses MathJax TeX fonts, and the SVG output doesn't use actual fonts at all (it uses SVG path elements). In theses formats, when a particular glyph is not available in the MathJax fonts, MathJax may try to substitute a different one in order to be sure that something is able to be presented, and so that it knows the size of the glyph. In the case of double-struck characters, MathJax will substitute bold characters if it doesn't have the double-struck ones. (Blackboard bold was originally the means of writing characters on the blackboard that should have been bold character if they were in print. So technically, blackboard bold should never appear in print, as they were just a convenience for writing bold characters with chalk. But mathematicians like having extra lattes, so they have migrated into print anyway). So in MathJax In MathJax v3, the remapping of characters to other ones has been removed, so This summer we are entering Phase II of the v3 rewrite, which involves updating the fonts that are available. This is a major undertaking, and will take some time, but a number of issues like this should be able to be addressed. |
Hi,
I would first like to thank you for this awesome work.
About my problem,
\mathbb{1}
(or any number) just displays as any other number.As you can see in this thread, it is not specific to MathJax, but to the mathbb package.
But the only real workaround I found for this was to use the
bbm
package for numbers instead of thebb
one.Its usage would be for the indicator function, and as you can see in the wikipedia articles of different languages (like french), use tricks for the notation like
1\!\!1_A
.So would it be possible to either add support for numbers in
mathbb
, or add thebbm
package ?Thank you in advance !
Thanks in advance
The text was updated successfully, but these errors were encountered: