Fini Jastrow 4394824977 name-parser: Change naming behavior ... [why] We created two fonts, one 'normal' and one 'Windows Compatible'. The later one used shorter names because there are some Microsoft applications that can not work with long (family-) names. But it would be better to have universally usable fonts, like all our sourcefonts. It would reduce confusion and also reduce the size of installation packages. [how] ID 1 (Family) family() Unchanged Take the short form font name. Appends depending on mode short or long weight. ID 2 (SubFamily) subfamily() Unchanged Transmogifies Oblique to Italic. Returns long form styles (i.e. RIBBI) ID 4 (Fullname) CFF.Fullname fullname() Take the short form font name (instead of long). Depending on mode take short or long styles. This is now in line with ID 4 = ID 1 + ID 2 ID 6 (PS Fullname) CFF.FontName psname() We limited the length to 31 characters, which is sometimes too short to have different names for fonts of one same family. Now we take the short forms of name suffix and styles, for example VictorMonoNFM-BdIt ID 16 (Typogr. Family) preferred_family() The name itself is unchanged (short form name plus verbose suffix), but the suppression check has been fixed to really compare the resulting name with the ID 1 name. ID 17 (Typogr. Subfamily) preferred_styles() This is unchanged (long form styles) but the suppression check has been fixed to really compare the resulting string with ID 2. CFF.Familyname ps_familyname() Uses ID 16 now and ID 1 as fallback. Was always ID 1 before, which is wrong. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>		2023-04-15 20:57:08 +02:00
..
scripts	name-parser: Change naming behavior	2023-04-15 20:57:08 +02:00