Localised font name troubles fontbakery

I am trying to set a localised family name (Primæ) that includes a non-ascii character. So far so good, only that fontbakery complains that the font full name includes non-ascii, which it shouldn’t. If I then set the full name using my family name (Primae) – without the troublesome character (æ) – fontbakery complains that there is a discrepancy between the family name and the full name.
Does anybody have a suggestion as to what is the bigger issue?
Thanks!

This is the fontbakery error:

Does the font’s CFF table top dict strings fit into the ASCII range?

opentype/cff_ascii_strings

All CFF Table top dict string chars should fit into the ASCII range.

PrimaeText-Bold.otf
    FAIL :

    The following CFF TopDict strings are not in the ASCII range:

     - FullName: Primæ Text Bold
1 Like

Could you send me the font for testing?

1 Like

Certainly, thank you for the kind offer to help!

1 Like

The FullName (nameId 4) seems to be build from the localized family name. And that is fine for the name table (there is no limitation on the encoding for nameId 4). But the same string is used in the CFF font, too. And there, only ASCII is allows. Glyphs writes that wrongly. For now, you need to add a “Full Names” property to each instance.

Thanks Georg, that’s very helpful, I’ll try to implement it like that.