Skip to content
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

Drop the "No Glyph" glyph #8

Open
alerque opened this issue May 7, 2020 · 0 comments
Open

Drop the "No Glyph" glyph #8

alerque opened this issue May 7, 2020 · 0 comments

Comments

@alerque
Copy link
Member

alerque commented May 7, 2020

I've been doing tests with mono-space fonts in my terminal that include double width characters. These are actually pretty common as poor-man's-ligatures in programming contexts. One thing I've run across that's really obnoxious is a handful of fonts that have placeholder glyphs rather than no glyphs for unimplemented code points. I'm sure this is a well intentioned attempt to un-confuse people running across the dreaded empty boxes — and in some contexts it is a cute fix, but in others it is obscenely obnoxious — such as when what you are trying to do is make use of font fallbacks such as almost all modern operating systems and typesetting systems support (even vim in my terminal!).

Another thing that is going to wreak havoc with is automated tooling to determine and render specimens for font coverage. You can't easily figure out what is implemented if there are fillers.

I propose entirely nuking the "No Glyph" glyph and leaving unimplemented glyphs as non-existent so that other tools can figure out what to do with them.

image

In my opinion these are to fonts what null is to programming languages: a billion dollar mistake. Not as costly but still an ultimate downgrade in function just because you couldn't resist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant