-
Notifications
You must be signed in to change notification settings - Fork 169
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
Explain the fields in "Font Info & Metadata" section #202
Comments
If people would like, we could add explanations for the fields based on probonopd/font-leutkirch#11 (comment). |
I agree with @probonopd. I plan to rewrite this page entirely. While most of this book is really good, I've always thought, this page is very rough. There is far too much focus on basic things people are likely to know, and which are in any event discretionary/to-taste (e.g., the semantics around version numbering†), yet very important questions are glossed over or ignored entirely:
(To be clear, I'm not asking that someone else answer these questions before I rewrite it. I know the answers.) † It's not even correct about these semantics. "Sadly, the third PATCH version number isn’t available in OpenType font version metadata fields." This is wrong. You can do "Version 1.0;patch 1;FontForge 20200314", and this is relatively common to see. Hack's Version string is, as of writing, |
Thanks for taking up this challenge @ctrlcctrlv. As I had to learn in probonopd/font-leutkirch#11, there seems to be much more to this than meets the eye. I hope that thread has some useful material that can be worked into the chapter. |
http://designwithfontforge.com/en-US/Font_Info_&_Metadata.html contains a section on Font Info & Metadata.
Unfortunately this does not explain what to put where.
It would be worthwhile to have a concise, pragmatic explanation what to put into which field, from today's "industry best practice" perspective. See here for some questions that may come to mind when being confronted with this dialog for the first time.
The text was updated successfully, but these errors were encountered: