-
Notifications
You must be signed in to change notification settings - Fork 19
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
Remove U+FEFF ZERO WIDTH NO-BREAK SPACE #40
Labels
help wanted
Extra attention is needed
Comments
It's a useful character to force equations to not break across lines. |
U+FEFF should be interpreted as the Byte order mark. The use of ZERO WIDTH NON-BREAKING SPACE (ZWNBSP) is deprecated and therefore "the use of U+2060 WORD JOINER is strongly preferred over ZWNBSP for expressing word joining semantics since it cannot be confused with a BOM". |
Finally I decided to remove it. |
stone-zeng
added a commit
that referenced
this issue
Jan 13, 2020
stone-zeng
added a commit
that referenced
this issue
Jan 13, 2020
update README.md [ci skip] glyph: finish arrow block for thin weight script: support woff; fontforge use python3 now script: add main function in build.py [ci skip] glyph: update semi-circle and circle arrowa glyph: arrow block for ultra weight glyph: correct start points and directions for master weights glyph: arrows for all weights glyph: fix uni21E1 glyph: add more arrows - Update squiggle arrows in ultra. - Complete Supplemental Arrows-A. - Add some more arrows in other blocks (from trivial transformation). - Update some scripts to python3. Remove U+FEFF ZERO WIDTH NO-BREAK SPACE Close #40. add hhea and OS/2 tables for ascent, descent and lineGap update changelog [ci skip] Replace soon-to-be deprecated \etex_iffontchar:D by \tex_iffontchar:D update copyright [ci skip]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At present U+FEFF ZERO WIDTH NO-BREAK SPACE is leave as an empty glyph (only in regular weight). Should I keep this, or simply remove it? Do I need to consider such special things when design a font?
The text was updated successfully, but these errors were encountered: