Text displaying as gibberish on PDF Export

[Yaco]

Hi, in Affinity Publisher, when I export the document to PDF, text is displaying as gibberish (see attached screenshot).

The font is a standard Google font (Lato) , so there should be no licensing issues. What might be causing this, is there a way around it?

 

Thanks!

[ashf]

No, Lato does not become gibberish on my side.
What software are you seeing the pdf on?
I checked the pdf on Adobe Reader.

[Joachim_L]

Works fine for me too. I have Version 1.104 installed. Could post the .afpub file and / or the PDF you exported? Maybe deleting and re-installing the font(s) might help?

[Cyan Cooper]

I'm getting this issue as well. The REALLY messed up thing is that only one of the pages in the Publisher document has this behavior.

Attached are screenshots. The font is Montserrat, and it displays fine inside of Publisher but not in PDF format. Again, this is only for one page of the Publisher document, the OTHER page of the Publisher document displays Montserrat in PDF format just fine.

This behavior has been going on for a while, any help is much appreciated!

Thank you!

 

[carl123]

Can you upload a copy of the Publisher document?

[DLW4000]

I am also having this issue, particularly with the font Raleway (also a standard Google font family). Text displays as gibberish in any pdf reader (Adobe, Chrome, Edge, etc.) - have tried exporting with various settings, and from both Publisher and Designer. It happens whether the text is copied and pasted from another source, or with a new text box and typed in with the default font - if the file is exported with other fonts it exports correctly, but if the font is changed to Raleway, it exports as as mess. Raleway exported fine in a previous document using these Affinity programs... What happened?

Edited December 29, 2020 by DLW4000
addition of information

[RedBambie]

Print to pdf gets around the issue

[walt.farrell]

12 hours ago, RedBambie said:

Print to pdf gets around the issue

Welcome to the Serif Affinity forums. 
Yes, that would probably work. There are probably other solutions, too, if anyone reporting the problem in this thread had answered the questions we asked, or provided sample files.