-
Notifications
You must be signed in to change notification settings - Fork 6
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
difficulty using glyphs in the Corporate Use or Microsoft Symbol Areas #7
Comments
I asked on the context list: https://www.mail-archive.com/ntg-context@ntg.nl/msg89146.html |
Same problem reported by Claudio Beccari:
Current Output:Expected Output |
The generic fontloader moved "all private chars in the font to a dedicated private range" and so broke the access of this glyphs. If this change is permanent all packages and documents which access such glyphs will have to adapt their code. Currently available work-aroundsuse older fontloader
with a lua function
|
I uploaded a new version to ctan, it should be available tomorrow. If you want to try directly: Both the texmf-tree and the zip in the dev-branch contain the new files. |
That fixes it for fontawesome. Thanks! |
Thanks for fixing this so quickly! The updated |
With version 2.9 of luaotfload, it has become more difficult to use glyphs in the Corporate Use and similar areas. For example, the
\fontchar
macro no longer gives the desired result. See https://tex.stackexchange.com/q/453224 for more details.The text was updated successfully, but these errors were encountered: