But the weight returned by availableMembersOfFontFamily is the same as the Light face:įamily: Helvetica Neue, psname: HelveticaNeue-Light, face: Light, apple-weight: 3, css-weight: 2, traits: 01000004įamily: Helvetica Neue, psname: HelveticaNeue-UltraLight, face: UltraLight, apple-weight: 3, css-weight: 2, traits: 01000004 In 10.5, the Helvetica Neue font family shipped with an extra Ultra Light face. The weight NSFontManager reports via availableMembersOfFontFamily is incorrect for Helvetica Neue Ultra Light face.įirefox uses the NSFontManager availableMembersOfFontFamily: method to determine the faces for a given font family along with their weights and traits. One solution would be to read in the OS/2 table ourselves but that's completely beyond the scope of this bug. With two faces that share the same weight, there's no way via CSS attributes to distinguish between the two.

I'm stumped as to how they are calculating these weights, maybe they're just 'analyzing' the style name instead of pulling in the OS/2 weight or the Panose weight? Bizarre. So the information in the fonts is correct, I'm not sure how exactly the Apple API is coming up with an Apple weight of 3 instead of 2 for the Ultra Light face. Using the Apple font tools (ftxdumperfuser) I dumped out the OS/2 tables of both fonts: (For list of Apple weight with CSS equivalents, see below) Psname: HelveticaNeue-UltraLight, face: UltraLight, apple-weight: 3, css-weight: 2, traits: 01000004 Psname: HelveticaNeue-Light, face: Light, apple-weight: 3, css-weight: 2, traits: 01000004

It looks like this api is returning the weight of the Ultra Light face incorrectly: Based on data coming back from NSFontManager, both faces are '200' weight fonts.Īt startup we set up a font list containing the names of all faces within each font family along with the associated weight and traits, using NSFontManager availableMembersOfFontFamily.

Helvetica neue bold font