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

Change font naming convention (or allow custom names during conversion) #42

Closed
eugenesvk opened this issue Nov 8, 2015 · 5 comments
Closed
Milestone

Comments

@eugenesvk
Copy link

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!

@ryanoasis
Copy link
Owner

@eugenesvk

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).

  • Changing the family name to be consistent across variations should be one of the easier fixes you suggest.
  • The variation tacking on the included glyphs is yes very ugly. A partial solution at least is underway where I am going to rename the one with EVERYTHING as: < font name > Nerd Font Complete since this is probably the variation that is going to be most used. Would this be useful? You probably downloaded the font that has all the glyphs anyway?
  • User input: Yeah this could be an option and may help. It sounds like the other points you made are more of a concern but this might be a nice option to have as well.

@eugenesvk
Copy link
Author

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).
And then all other incomplete variations can be indicated though additional file name modifications (I'd suggest abbreviations as indicated above to keep the name short, but it's not critical since I'm only using the complete font type).

@ryanoasis
Copy link
Owner

@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 👍

@ryanoasis ryanoasis modified the milestone: v0.6.0 Nov 14, 2015
ryanoasis added a commit that referenced this issue Nov 14, 2015
…ons to use the same Font Family (partially fixes: #25, #32, #42)
@ryanoasis
Copy link
Owner

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 👍

@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants