If I remember correctly, font version is a 32-bit number, the top 16-bit is x, the lower 16-bit is y, to make x.y. It is not a string. Use the opentype spec. Or an 16-bit number, top 8-bit as x, lower 8-bit as y, to make x.y .
What is a “single font family” here? An upright design in a single weight, but ca. 16 different point sizes? A single size for a new design? Regular and Italic in ca. 16 sizes? Regular, Italic, and Bold, each in ca. 16 sizes?
If you follow the link https://github.com/IBM/plex you get a download button for everything, including sources. Here is the number of files of each type 16 eot 6 fea 4992 glif 16 otf 36 plist 16 ttf 32 vfb 96 woff 96 woff2
Hey all, I can’t make it to ATypI 2024 in Brisbane (I just can’t justify the cost alas), but I live in Brisbane and would be happy to catch up with people if we wanted to have TypeDrawers meet up. Is anyone from TD going? Details about the event here https://atypi.org/conferences-events/atypi-brisbane-2024/
MacBook Pro 16 M1. Using its own display and trackpad. Sometimes, I also use a 27" external monitor. With FontLab 8.3, which runs natively on Apple Silicon with impressive performance.
Does anyone know why MacOs prefers to use the name id's 16 and 17 for the Windows platform over the id's 16 and 17 for Macintosh the platform? Adobe InDesign on Mac also uses the id's for Windows.
It doesn’t look correct to me. If nameID 1 is “IBM Plex Sans Compact” and nameID 16 is not present, those 4 styles should be grouped under the “IBM Plex Sans Compact” family. Adding the apparently redundant nameID 16 seems to fix this.
About under- and overshoot: 1. for under- and overshoot is it better to have the same values (eg. baseline -16, x-height +16)? 2. for uppercase and lowercase is it better to have the same undershoot values? Because in some fonts I have found for example that the uppercase is 0 / -16 and the lowercase 0 / -12. Could this…
Yes, just so. Those slots correspond to Name ID 16 and 17 (unless they happen to be the same as 1 and 2, in which case 16 and 17 could be omitted). Note: I don't recommend using non-ASCII characters in font names or styles. So Mediaeval is OK, but not Mediäval.
Could it be a matter of the defined charset in your html file? Do other glyphs with their unicode greater than 2^16 work? Is your font in Fontforge encoded for a unicode variant that allows more than 2^16 encoding slots at all (unicode-bmp does not)? Are you sure, that the private area in unicode-bmp is not more suitable…
If you use type design software PLUS Creative Cloud apps like me and @"Adam Ladd", I have the same experience: 16 GB is a good minimum. Although unlike Adam, I do find I occasionally run out of memory, so more would be nice. 16 GB is also the maximum on older MacBook Pro models, so that may simplify your choices.
@peternowell That'll work great. Thanks! @"John Hudson" Here's the link:https://calendly.com/peternowell/font-proofer-webinar?month=2023-02&date=2023-02-16