Jump to content
You must now use your email address to sign in [click for more info] ×

Export to PDF with a specific font family crashes all three apps


Racey

Recommended Posts

Font Akwe Pro applied to frame text or artistic text causes Affinity Publisher 2 (also Designer 2, Photo 2 and now all three version 1 apps) to crash when exporting to PDF as subset font. To reproduce, place text in any document, apply any Akwe Pro style to it, then export to PDF. The app crashes and on restarting it, Terminal consistently offers up the following [extract]:

'2022-11-13 13:58:13.724 Affinity Publisher 2[2509:47797] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].
2022-11-13 13:58:13.724 Affinity Publisher 2[2509:47797] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug.
2022-11-13 13:58:13.751 Affinity Publisher 2[2509:47797] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].
2022-11-13 13:58:22.974 Affinity Publisher 2[2509:47797] Failed to select item with enum value -3!
2022-11-13 13:58:22.976 Affinity Publisher 2[2509:47797] Failed to select item with enum value -3!
2022-11-13 13:58:22.977 Affinity Publisher 2[2509:47797] Failed to select item with enum value -3!'

The font files have been validated by Font Book. Latest versions of InDesign, Pages, Word all output the font to PDF (as subset not curves). Font was working just fine in v1 until I upgraded to v2 of the Affinity apps.

iMac running Big Sur (11.7.1). Identical error reproduced on a Macbook Pro running Monterey (12.6.1).

Link to comment
Share on other sites

7 hours ago, Racey said:

".SFNS-RegularItalic"

This issue may be related to fonts, but I doubt it is related to Akwe Pro.
The dot before the font name above means it is a Mac system font.
So I am not sure why that is being included in your document.
macOS TTC files do sometimes have a "dot" font and a regular font (for the same font).
Maybe there is an issue with that on Macs now (the TTC files).
Can you attach at least one page of the document which demonstrates this issue?
Then others, including other Mac users, can take a look.

Below is a test of Akwe Pro Regular Exported to PDF (on Windows 10),
and then exported from the PDF to a PNG. Working fine here.

Akwe-Pro-Regular-to-PDF-to-PNG.png.6fc36be9c4af889ebcc62ed420a98157.png

Link to comment
Share on other sites

4 hours ago, Racey said:

Thanks for taking a look. The attached file crashes for me. The SFNS files are separate ttf files in my System/Library/Fonts/ folder. 

Akwe Pro.afpub 645.85 kB · 1 download

Well that is quite bizarre - instant crash for me too on Win10.
Changed the fonts to Akzidenz-Grotesk Next and it exported fine.
Late here, will look closer tomorrow.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.