djrrb / Bungee

A chromatic signage typeface for vertical and horizontal setting.
https://djr.com/bungee
SIL Open Font License 1.1
336 stars 42 forks source link

Script build for Google Fonts API (NAME table updates) #40

Closed davelab6 closed 3 months ago

davelab6 commented 8 years ago

The NAME table has a few things that I would like to request changing before the next build.

eg in fonts/Bungee_TTF/Bungee-Regular.ttf it is Bungee Regular and should be Bungee

(I noticed that in Bungee-Regular.ttf the family name being Bungee Regular meant the windows full name became Bungee Regular Regular, which is a bit odd - all should just be Bungee :)

The Google Web Fonts API will present these as each a Regular (400 roman) instance for 5 different families, so the filenames should instead be,

davelab6 commented 8 years ago

I just tested the above (by hotfixing TTFs with TTX) and Illustrator is smart enough to silently match BungeeShade-Regular.ttf to Bungee-Shade.ttf so no existing documents should break.

From a UX perspective it means that the styles appear not as styles within a "Bungee" family, but as separate styles in the family list; while this isn't as tidy, I think this might be a better UX because the styles dropdown doesn't have a rendered preview while the family dropdown does. Here's InDesign:

screen shot 2016-05-11 at 10 23 57 screen shot 2016-05-11 at 10 23 41

Here's Illustrator:

screen shot 2016-05-11 at 11 59 25
djrrb commented 8 years ago

Dave and I just spoke about this, and it looks like we are going to leave the names as-is in the sources, and let these fields be changed for the web fonts in production.

I will need to rebuild the desktop fonts, and incorporate the google web fonts along with the other web fonts. I made a separate to-do for this here: https://github.com/djrrb/Bungee/issues/44

If there are no objections, I'll close this issue.

davelab6 commented 8 years ago

Maybe leave it open until there's a script to automate

djrrb commented 8 years ago

Sounds good!

justvanrossum commented 3 months ago

I'm assuming this has been resolved with the v2.000 release.