Jump to content

Recommended Posts

Posted


I'm trying to export a Affinity Publisher file to PDF but the program (1.10.4) is substituting the Light version of my font rather than the intended Regular, rendering it very difficult to read. I've tried print and high quality digital settings - both come out Light.


I'm on Mac OS 10.15.17 and do not have this font substitution problem when I use Mac's built-in feature to Save As PDF. (In that case, the fonts am embedded correctly but the interactive links don't hold, so it's not an acceptable workaround.)

Any suggestions?  I've tried various export settings with embedding fonts
 

  • Staff
Posted

Hi Besieged Parent,

Welcome to the forums :)

In order for me to look into exactly why this might be happening I will likely need a copy of the file / font so I can test this at my end. However if you are just looking for a quick solution to this issue and your text no longer needs editing you could convert it to curves and then export to PDF however this will prevent the text from being edited in the future so it is perhaps worth making a back up of the file.

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Posted
18 hours ago, Besieged Parent said:

I'm trying to export a Affinity Publisher file to PDF but the program (1.10.4) is substituting the Light version of my font rather than the intended Regular, rendering it very difficult to read. I've tried print and high quality digital settings - both come out Light.

What font(s) are you using?

Posted (edited)

Raleway, a Google font. I downloaded the full suite and my document uses Regular, Italic, and Bold.  The Affinity export turns everything into the Thin version.  As I mentioned, the built-in Mac pdf-maker exports the fonts correctly.

Raleway.zip

Edited by Besieged Parent
Adding font example
Posted
10 minutes ago, Besieged Parent said:

Raleway, a Google font. I downloaded the full suite and my document uses Regular, Italic, and Bold.  The Affinity export turns everything into the Thin version.  As I mentioned, the built-in Mac pdf-maker exports the fonts correctly.

My guess is you installed the variable fonts, not the static fonts.

When an application does not support variable fonts the default master is what is used. In the Raleway variable fonts the Thin master is the default master - so that is what you get.

The Mac font manager does support variable fonts and fools you by displaying them as if they will work in Affinity apps (which do not support variable fonts yet).

Un-install the variable fonts and install the static fonts - and it should work.

Posted
16 minutes ago, LibreTraining said:

When an application does not support variable fonts the default master is what is used. In the Raleway variable fonts the Thin master is the default master - so that is what you get.

The Mac font manager does support variable fonts and fools you by displaying them as if they will work in Affinity apps (which do not support variable fonts yet).

It sounds the OP was surprised by the exported result only but not in the layout. So, are there also variable fonts which may mislead the user with their look in the font menu only but not in the layout? For instance this "Abelone" occurs colourful in the font menu but in the layout with the currently assigned colour.

1724951956_variablefontmenuvslayout.jpg.49f93f5afe0a94a5642efea546f69926.jpg

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Posted
3 hours ago, thomaso said:

It sounds the OP was surprised by the exported result only but not in the layout. So, are there also variable fonts which may mislead the user with their look in the font menu only but not in the layout? For instance this "Abelone" occurs colourful in the font menu but in the layout with the currently assigned colour.

Yes, I was surprised that "the built-in Mac pdf-maker exports the fonts correctly."
And I assume that it looked OK in the APub interface.
So it appears that on the Mac it can connect the variable font with its PDF engine.
And that PDF engine also supports variable fonts.
I do know that on Macs all applications use their font picker interface.
And since it supports variable fonts it can display them.
I use Windows so I am not real familiar with all that happens on a Mac.

The Abelone font situation is sort of the same - the Mac font list supports Color-SVG fonts.
Abelone is an OpenType Color-SVG font which includes a normal monochrome back-up.
That backup is essentially a normal OpenType-PS (OTF) font.
The SVG drawings are in the SVG table inside the font.
The PS drawings are in the normal CFF table.
If an application knows how to use the back-up font, that is what it will display.
So that is what you see in APub.
Note: that is what the back-up outlines actually look like - with all the filled-in areas.
It appears the back-up glyphs were automatically created by Fontself Maker from the SVG drawings ... so they are bad. The font designer could clean them up if desired. Free font.

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.