-
Notifications
You must be signed in to change notification settings - Fork 13
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
Should I rename 0xProto? #27
Comments
I think the name is fine. Also, it comes the first when you browse the font list :p |
I'd rename it, but then, I'm not attached to the name. 😃 If it would let it work in Mail.app, I'd definitely rename it. But this is not a deal-breaker either way. |
@ktekinay See #15 (comment) and #26
|
When generating the font named
I have no recollection where I got that statement from and a quick search turned up empty. Maybe it is an Adobe/Postscript thing (but I searched there also). Anyhow, the font |
Could not find out where George got that from, has been in the code since the initial commit. (I still believe you can ignore it) |
@Finii Thanks for the detailed information! |
After much research and consideration over the past month, I've decided against changing the name 0xProto.
As far as I know now, this is the only drawback caused by the name '0xProto'. So, I decided to prioritize identity over a little inconvenience. |
Per the OpenType specification, there aren't any restrictions on font names, so '0xProto' is perfectly valid. However, in applications like VS Code, where you enter the font name into a text field, it requires the name to be enclosed in quotation marks. This isn't typical for other fonts. Given that the font name '0xProto' starts with a number, it isn't the most user-friendly experience.
As a result, I'm considering renaming the font, if necessary. (I'm really fond of the name '0xProto' and, honestly, I'd be reluctant to change it for sentimental reasons.)
The text was updated successfully, but these errors were encountered: