[Beta 1.7.0.384] Font in exported PDF

[Evgenii 0]

After updating to the new version, when I export the pdf file, the EB Garamond font renders as a total mess. The font is rendered correctly in the application itself (as well as other applications). Only regular style has this problem, bold, italic, medium render right. The issue is persistent both in the old files and the new ones. Reinstalling the font from the Google Fonts didn't solve it. I have not encountered that problem with other fonts yet. It appeared immediately after updating to the version 384.

bug_test.afpub

bug_test.pdf

[Joachim_L 117]

No problem on my side, see image. Maybe a damaged font installation? Try to uninstall the font and install anew.

Edit: What where your exact export options? Screenshots would be nice, since my file is significantly bigger than yours.

Edited June 14 by Joachim_L
Question added

[Evgenii 0]

As I mentioned, font reinstallation didn't do any good. Moreover, in other programs, like word, text renders as intended.

I believe the export settings are default

[Alfred 3,954]

I have EB Garamond installed, so the original file opens correctly in the iPad version of Affinity Designer. When I export using either ‘PDF (for export)’ or ‘PDF (for print)’, the text is converted to curves.

[Joachim_L 117]

Very strange. Used the same export setting. No problem again, text as text, but my file has 1.778.714 bytes compared to Evgenii's 406.116 bytes. Opening Evgenii's PDF in Illustrator or ADesigner shows the strange characters.

[Evgenii 0]

Interestingly, if I don't embed the font, the resulting PDF renders it right.

 

Edited June 14 by Evgenii

[LibreTraining 50]

Where did your original EB Garamond fonts come from?
The originals from GitHub (octaviopardo) and the ones from GoogleFonts are different.
If you installed the ones from GoogleFonts over the old ones the font cache(s) could be a mess.
Actually in the ones from GoogleFonts the way the fonts are named is really odd.
It is not one Typographic Family, it is four.
I have never seen anything from GoogleFonts named like this.
Keep in mind that GoogleFonts is not geared towards desktop use.

Also the ones from GitHub are available in both OTF and TTF.
The ones from GoogleFonts are only TTF.
So if you installed those over the OTF versions ... font cache(s) could be a mess.

I have been meaning to fix these fonts (from GitHub) to work properly in LibreOffice.
They then should also work properly in APub.
That would probably fix your issues here.
If you're interested.

 

[LibreTraining 50]

Try these.
Renamed family to: EB Garamond X  
"X" for cross-platform compatibility.
Both OTF and TTF files are included.
The family name is different you can have this installed along with the previous version.

EB.Garamond.X.both.OTF.and.TTF.zip

I did not test yet but I expect your PDF output will be fine.

[Evgenii 0]

I use FontBase for managing my fonts, and I had Garamond from Google Fonts. Installing the same very font directly into the system solved the problem, even though I'm not fan of this solution.