We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
from the RoboFont forum: https://forum.robofont.com/topic/940/glyph-builder-unixxxx-glyph-name-doesn-t-trigger-unicode-value
The text was updated successfully, but these errors were encountered:
it does but it gets overwritten back to None as the construction has no unicode value...
None
https://github.com/typemytype/GlyphConstruction/blob/master/GlyphConstruction.roboFontExt/lib/glyphConstructionController.py#L456-L461
I guess making the unicode value implicit in the glyph construction code is the best: uni1E93 = w + acute@top | 1E93
uni1E93 = w + acute@top | 1E93
Sorry, something went wrong.
ok, so what "Auto Unicodes" means?
if this is ticked on in the UI it will use the RF characterMapping to find unicodes, only when no unicode is provided in the construction
see https://github.com/typemytype/GlyphConstruction/blob/master/GlyphConstruction.roboFontExt/lib/glyphConstructionController.py#L433-L435
No branches or pull requests
from the RoboFont forum:
https://forum.robofont.com/topic/940/glyph-builder-unixxxx-glyph-name-doesn-t-trigger-unicode-value
The text was updated successfully, but these errors were encountered: