You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry forgot to mention in #317 but U+200B (zero-width space) is useful for strings like "Yes/No/Maybe" if you want each word to separate into new lines.
The fact that the glyph in question does not exist in the font does not by definition mean that it will not be rendered. There are environments that use fallback fonts in this case. Applications such as Adobe InDesign are able to synthesize these kinds of spaces by itself.
Activity
BoldMonday commentedon Jun 9, 2020
The fact that the glyph in question does not exist in the font does not by definition mean that it will not be rendered. There are environments that use fallback fonts in this case. Applications such as Adobe InDesign are able to synthesize these kinds of spaces by itself.
johnnyshields commentedon Jun 10, 2020
Without use of fallback, how does it appear in plex? As tofu?
BoldMonday commentedon Jun 10, 2020
Probably. Without fallback any glyph that is non-existent should be displayed with the .notdef character (AKA “tofu”).
johnnyshields commentedon Jun 10, 2020
Would be worthwhile to properly handle all the ZWJ / ZWNJ characters maybe as part of the Math Symbols project?
BoldMonday commentedon Jun 10, 2020
That could be a consideration.
FWIW – ZWJ and ZWNJ are currently included in Plex Sans Thai (Looped) and Plex Sans Devanagari.
AlsoScratch commentedon Jun 10, 2020
Well, this could be an actual problem.
BoldMonday commentedon Jun 10, 2020
Perhaps. But when I use a zero width space with Plex in a macOS application such as TextEdit then I see no problem.
AlsoScratch commentedon Jun 11, 2020
I can't trust every application to use a fallback font... but those that do shouldn't matter, probably.
mjabbink commentedon Sep 29, 2020
Could be consideration for Plex Math but tabled for now.
tay1orjones commentedon Aug 16, 2022
Hey there! v6.1.0 was just released that references this issue.
Comment here or join the release discussion to provide feedback or voice concerns. Thanks!
tay1orjones commentedon May 8, 2023
Hey there! v6.3.0 was just released that references this issue.
Comment here or join the release discussion to provide feedback or voice concerns. Thanks!