Publisher 2.2.1: Glyph-Browser shows no glyphs

[Andreas S]

As shown in the screenshot the glyph browser shows no glyphs for my ZapfDingbats font (compared  to the Windows character map).

I have also tried with the AGaramond-Font and it seems to happen with Type1-Fonts.

[Old Bruce]

1 hour ago, Andreas S said:

I have also tried with the AGaramond-Font and it seems to happen with Type1-Fonts.

If you mean PostScript Type 1 fonts then I would strongly suggest replacing them with OTF or TTF fonts. Those old PS fonts are being deprecated throughout the industry.

[Andreas S]

yes, for professional use I agree - I wouldn't want to send a document with Type1-Fonts to a Print studio. Anyway, for home use, why shouldn't I use those fonts from an old Font CD, which work perfectly with Windows and any printer at home? And indeed, also the Publisher works fine, it is only the Glyph Browser which has some trouble with those fonts.

[walt.farrell]

11 minutes ago, Andreas S said:

And indeed, also the Publisher works fine, it is only the Glyph Browser

You will probably find other issues in Publisher, if you use those fonts enough.

[Dan C]

Hi @Andreas S,

Thanks for your report!

As I understand it, Type 1 font support in Affinity is provided by the OS - therefore certain features and functions may not work as expected for these fonts.

Are you able to attach a copy of your Type 1 font here for me so I can log this with our team, to see if this can be improved in the future?

As above, we do recommend using OTF/TTF fonts in favour of Type 1 fonts where possible.

Many thanks in advance

[Andreas S]

Hi Dan,

after the comments from Old Bruce and Walt I checked on the Adobe Website and learned that Type 1 is officially discontinued since 2023. So I believe, the correct handling in the Glyph Browser would be a "nice to have" with a low priority. I'm sending you the Type 1 files anyway.

 

ZD_____.PFB ZD_____.PFM

[kenmcd]

Pretty easy to find alternatives for Zapf Dingbats which will work in Affinity Glyph Browser.

ITC Zapf Dingbats Std - Adobe (2007) (AFF11) - OpenType-PS - (Unicode)
(from Adobe Font Folio 11.1)

Zapf Dingbats BQ - Berthold (2004) - OpenType-TT
(three fonts - Zapf Dingbats 100, 200, and 300)

Zapf Dingbats BT - Bitstream (1993) - TTF - (Unicode PUA)
(in the old BitStream 500 Fonts CD)

 

[Dan C]

Many thanks for providing these for me!

20 hours ago, Andreas S said:

So I believe, the correct handling in the Glyph Browser would be a "nice to have" with a low priority

As I understand it, our developers agree - so I'll be logging this with our team now but I'm unable to offer any guarantees regarding changes in a future version for how Affinity handles Type 1 fonts.

I hope this clears things up