kenmcd

> @kenmcd I understand the family name is still messed up (that's issue #393) but I'm not convinced that issue is what is making the font "not a valid font"...

The Affinity publisher interface for Character Variants has been changed/upgraded a lot in the most recent Windows Beta. I don't think this has even made it into the Mac beta...

> (Too bad there's not a "None" placeholder. There's a NULL, but it's supposed to delete a character, and in any case it doesn't appear to be implemented.) I thought...

Hi Peter, I have been watching the whole discussion over there (glad you bumped it and got a response). As I am also subscribed to the Microsoft typography-issues repo, I...

> I think maybe (it's been a while) I decided to duplicate the triple dagger because it's still in the MUFI spec, and people might expect to find it at...

Peter, Perhaps because of the lack of clarity from MUFI it is best for now to continue what you are doing. And then we provide some clarity by documenting what...

> > > I've written to the MUFI group recommending that the PUA code points should be deleted, but I don't know if changes are being made right now. Is...

> >  The lower part of the characters is being cut-off by the typoDecender. Windows apps are using the typo settings for line spacing. If you look at...

The Character Map application (in Windows) only shows characters which have a Unicode code point assigned. Since most alternates are glyphs which are un-mapped (no code point) they do not...

> heads up, I'm working on extending it to [GF Latin Core glyph set](https://github.com/googlefonts/glyphsets/blob/main/GF_glyphsets/Latin/txt/prod-names/GF_Latin_Core.txt) coverage (which includes hungarumlaut accents) as part of a wider font modification project. > > will...