-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Change font naming convention (or allow custom names during conversion) #42
Comments
These are good points and I agree with you pretty much! I have actually been in the process of reorganizing the directory structure a bit to make ad hoc downloading easier (spurred from #32).
|
Yes, having a simple name for an all-inclusive font is a good idea since it is indeed typically the most useful variant. I would suggest though a slightly shorter name (e.g. < font name> Nerd or NerdAll if you insist on indicating everything is packed), since I've already run into trouble in Windows with long font names (I know you have an option to force shorter names, but would like the default to be work). |
@eugenesvk That is a good suggestion to keep it as short as possible. I was going with Nerd Font because it is the project name. I can see where having 'Font' part of a font name is a bit redundant however. All could also work in place of Complete. I am not sure about those but I will definitely consider them 👍 |
Closing for now as this is partially implemented on v0.6.0. If it is not good enough we can discuss and implement on a later version 👍 |
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference. |
Currently both font file names and internal font names are a bit unwieldy.
The file names are too big and font names are unique for each style, which prevents Font Book from displaying them under one family group.
I understand the need to differentiate between many variants, though would prefer a simple
SourceCodePro-Medium-mNOP instead of
Sauce Code Pro Medium Plus Nerd File Types Mono Plus Octicons Plus Pomicons
for file names and something similar for font names (e.g. Source Code Pro mNOP font family while retaining original style names like Regular instead of Book).
Would it be possible to adjust the naming convention during conversion or allow some user input (e.g. sourcing a file with "original font names:new font names" that could be used for naming instead)? I'm most interested in font names since file names are much easier to change.
Thank you!
The text was updated successfully, but these errors were encountered: