Hi,
A client has tasked me to update some older .pfb font files. While these open in Glyphs and I can save it as Glyphs file, I can’t use the in app type preview function and also when I export a test version of the font it exports but does not contain any glyphs?
In the app everything appears normally e.g. outlines, nodes, etc.
Is this because the format is originally Windows based?
What do you mean by that?
How do you export? How do you test the font?
Oh sorry, I mean the type tool in Glyphs (The T in the toolbar) will not add glyphs when typed. This only occurs with Glyphs files created via first opening the .pfb font files I have (and sadly I cannot share!).
The font exports as either .otf or .ttf with no errors but when used in an Adobe application, Mac OSX, or even with font preview apps, the glyphs are all just whitespace.
Then the unicodes are not properly set. Can you post the name and unicode of some of the glyphs that I can understand what’s going on?
I will later today but I am away from the Mac at the moment.
Thank you very much for taking a look.
Hi Georg,
As requested here is what the outline and unicode looks like in Glyphs:
When exported, comma does not produce a glyph. It appears to be normal:
What version of Glyphs do you have?
And can you select all glyphs in Font view and run Glyph > Update Glyph Info.
I am on Version 2.6.4 (1277)
Ah yes, the unicode values are now loaded beside each glyph. Sorry I had not used that function beyond. I will test an export.
Great, the export is working!
Thank you for pointing this fix and apologises for it being so simple.
Could you send me the .pfb file that I can check why it didn’t add the Unicodes automatically?
