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

Explain the fields in "Font Info & Metadata" section #202

Open
probonopd opened this issue May 3, 2020 · 3 comments
Open

Explain the fields in "Font Info & Metadata" section #202

probonopd opened this issue May 3, 2020 · 3 comments

Comments

@probonopd
Copy link
Contributor

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.

@probonopd
Copy link
Contributor Author

If people would like, we could add explanations for the fields based on probonopd/font-leutkirch#11 (comment).

@ctrlcctrlv
Copy link
Member

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:

  • What is the difference between sfnt Revision and Version?
    • Why does an sfnt Revision of 2.001 turn into 2.00101?
  • What are the differences between PS Names and TTF Names?
    • Why do PS Names seem to influence TTF Names?
    • Are "TTF Names" even applicable to me if I'm going to be producing a CFF-flavor .otf file (that is to say, using cubic Béziers in my «Fore» layer) or can I ignore them?
    • The page references “Preferred Family Name” and “Preferred Style Name”—yet these strings are nowhere to be found. Where are these set?
  • OS/2??
    • Is OS/2 only for IBM OS/2 and its derivatives?
    • Why are weight classes in multiples of 100? Can I put e.g. 150, and when should I?
    • What is a PFM family? What is an IBM family?
    • How much can I rely on OS/2 DRM?
  • What are the WWS Family and Subfamily?
  • "Windows does not support font families with more than the 4 basic styles"?? What about InDesign, GIMP, Inkscape, LibreOffice, Krita, and many more?
  • If PS UID/XUID are no longer necessary, what is unique then?
  • What if I need Unicode?
    • What if my font has different names in different languages, as is common with CJK fonts like MS 明朝? If my "Name for Humans" can't include Unicode, how do these fonts work?
  • How does all this affect CSS?
  • What should I put for Weight if this will be a variable font?

(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, 3.003;[3114f1256]-release; ttfautohint (v1.7) -l 6 -r 50 -G 200 -x 10 -H 181 -D latn -f latn -m "Hack-Regular-TA.txt" -w G -W -t -X ""

@probonopd
Copy link
Contributor Author

probonopd commented May 10, 2020

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.

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

No branches or pull requests

2 participants