OpenType font naming in FM
For those who are interested in how OpenType font naming can be handled in FM, I just published a PDF on this subject. Also some details are revealed on how the automatic generation of OpenType Layout features is handled. At the coming FM Track in St. Petersburg more info will be given, also on OT Master.
9.Sep.2008 2.26pm
Thanks, Frank!
ChrisL
9.Sep.2008 11.33pm
Frank,
check out page 14
TTName 2 3 1 0x409 “Regular”; #Macintosh
“#Macintosh” is wrong here, this might lead to confusion ...
10.Sep.2008 1.15am
‘[...] check out page 14
TTName 2 3 1 0x409 “Regular”; #Macintosh [...]’
Yes, I noticed the wrong comment, but most readers will probably understand what should have been written there. Nevertheless I will change the page shortly.
Perhaps I should add here to the info in the PDF that at DTL we normally edit the name IDs directly in the UFM files using a text editor. Not only ‘basic’ name IDs, like copyright notice, manufacturer name, URLs and license description can be simply copied into the UFM files, also the complete UFM files can be copied and internally renamed (in batch) for weight/style related fonts of the same family that support for instance other scripts (every font has its own UFM and kern file, which are connected by file name to the corresponding glyph database).
For the OpenType production normally a centralized ‘standard’ OT layout features file is used (features that don’t match the character set are removed during font generation), but when the features file is specifically customized it could make sense to put the font names in the file itself (if only to mark the file).