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

Missing character (U+202F) 'NARROW NO-BREAK SPACE' #282

Closed
ksesong opened this issue Nov 4, 2019 · 6 comments · Fixed by #555 or #562
Closed

Missing character (U+202F) 'NARROW NO-BREAK SPACE' #282

ksesong opened this issue Nov 4, 2019 · 6 comments · Fixed by #555 or #562

Comments

@ksesong
Copy link

ksesong commented Nov 4, 2019

This character is expected in some languages, particularly in French, as described on this page.

@BoldMonday
Copy link
Collaborator

Please provide a real-life example where Plex is misbehaving in this regard and that can be reproduced.

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, or synthesize these kinds of spaces by themselves.

@ksesong
Copy link
Author

ksesong commented Nov 5, 2019

I came across this issue when I tried to create a subset of the font for heavy optimization in webpages, using subfont for example. A webpage used the NARROW NO-BREAK SPACE character, but it was missing from the initial font glyphs, so the subsetting did not succeed, and the fallback font will always be used because of it.

I accept that this is quite a niche use case, and that this might even be more an issue of the subsetting software than of the font itself. Feel free to close the issue if you think this is the case.

@vpicone
Copy link
Member

vpicone commented Jan 31, 2020

Hey, we're going back and closing stale issues. Please feel free to reach out if you think this was closed in error!

@vpicone vpicone closed this as completed Jan 31, 2020
@techdragon
Copy link

@vpicone Unless the symbol was added, (it does not appear to be) then this was closed in error and still needs to be added.

@BoldMonday
Copy link
Collaborator

@techdragon the issue is noted on our side. Priority is pretty low though for the reasons stated above.

@tay1orjones
Copy link
Member

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!

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

Successfully merging a pull request may close this issue.

6 participants