cannot select text or use search on PDF created by Publisher 2 2.2.0

[Peter Cusworth]

Since updating to Publisher 2 2.2.0, PDF files created in Publisher will not let me select the text on pages or to use the search function properly.

This was not the case on previous versions up to an including 2 2.1.1

Yesterday I uploaded and tried the Beta version 2.3.0.2.2139, but this issue is still the same.

Just wondering if others have had this problem. I have been using the same presets when creating the PDFs.

Regards

Peter

 

[MikeTO]

Hi Peter, I'm unable to duplicate this problem. Could you share a PDF for testing?

Which export preset did you choose? Did you make any changes after selecting the preset? A screenshot of your export settings would be helpful.

Good luck

[Peter Cusworth]

Test page.pdfI've attached a single page PDF and a screenshot of the settings, but it seems to do the same on any of the presets I choose. Maybe there's something I've missed somewhere?

 

Thanks

Peter

[MikeTO]

Your settings look good.

All of the text has been converted to curves in the PDF. Can you confirm that in your afpub the text is still editable text and wasn't accidentally converted to curves?

[Peter Cusworth]

Yes, all of the text is still editable in Publisher.

 

[Peter Cusworth]

Yes, all of the text is still editable in Publisher.

I tried a few of the presets to see if it was any different, but all had the same issue.

[Hangman]

Hi @Peter Cusworth,

I think you would need to upload your Publisher file for us to figure out what is going on...

As @MikeTO mentions above, there is nothing obvious from your export settings, though I noticed in your screenshot that you don't have Include Hyperlinks selected but the hyperlinks are active in your PDF.

The Handwriting Dakota font, used for Glenn's name at the end of the article is selectable in the PDF you uploaded so I don't know if there is an issue with the version of Frutiger you're using, though even that doesn't make a great deal of sense if the file is exporting without issue from v2.1.1. from the same Mac.

I created a quick mockup of your page in v2.3.0.2139 and all exports without issue with the text remaining selectable in the exported PDF using the same settings...

File Attached

Motor Sport Safety Equipment.pdf

[Peter Cusworth]

Hi Hangman,

Thanks to you both for looking at this. I will attach the Publisher file. This is just one page of a magazine, and I have deleted the photos. The resultant PDF did the same thing. I had tried various presets, hence the screenshot not showing the hyperlink, but all presets ended up with the same issue.

Two other monthly magazines I put together use different fonts, and the PDFs have the same issue since using 2.2, so wasn't thinking it would be fonts, but I have just had a go at replacing the font on this page with Arial, and it worked OK with the text selectable in the PDF. However, have also tried several other fonts, and they all have the same original issue. Something wrong with my font collection, except for Arial?

Anyway, see if it is different for you.

Appreciate your help.

Peter

Test page.afpub Test page Arial.afpub

[Peter Cusworth]

Just tried your PDF, and yes, the text is selectable for me, and the search then works too.

[Hangman]

Hi @Peter Cusworth,

Thanks for your files...

For me, your Test page.afpub file opened and recognised the version of Frutiger I'm using and again exports without issue, though oddly for me the Test page Arial.afpub file didn't recognise the font as Arial but instead as ITC Stone Sans (which I've converted to Arial in the attached PDF).

Regardless, both exported without issue with selectable and searchable text...

It may be worth just checking that you don't have more than one version of Frutiger installed, though you mention this issue is happening with other fonts as well...

Which Font Manager are you using... it would be worth running a test with your Font Manager software to see if it flags any font compatibility issues and also perhaps uninstalling Frutiger and reinstalling it just to be sure...

I'm pretty sure this won't be the issue, because I'd expect a different outcome, but I assume you're not using variable fonts?

Test Page PDF Exports

Test Page Frutiger 2.3.0.1239 Export.pdf

Test Page Arial 2.3.0.1239 Export.pdf

[Peter Cusworth]

Thanks for looking at this again.

Both of your PDF exports open on my system with selectable and searchable text.

Yes, sorry – that Arial sample file I sent is the one I'd tried several fonts with and forgot to change back to Arial before I sent it.

I am using the standard Mac Font Book for font management. It doesn't show any issue with Frutiger or the other fonts I tried. I only have one version of Frutiger installed. Maybe I will try uninstalling, or even sourcing a new copy of that font to try. I have had these fonts for many years. Still, it is strange that I didn't have this issue on the older version of Publisher, but otherwise, it looks to be a font issue with my computer.

The Frutiger font is an Adobe postscript Type 1 font. Is there a particular type of font that is best to use with this software these days? I don't think I have any variable fonts, although my Arial is an OpenType, but that worked OK.

I am running Mac OS 12.7.1 which I notice was last updated in October. Maybe that is the change affecting my fonts and not the Publisher update?

Thanks again for your help. I will try some other fonts and see if I can work out a solution.

Peter

[Hangman]

Hi @Peter Cusworth,

Postscript Type 1 fonts are still supported so I don't think that is the issue and likewise macOS 12.7.1 won't be the issue, I'm running 12.6.8... I have to say I'm slightly baffled as to the possible cause especially since it appears to be affecting more than just the version of Frutiger you are using...

Could you possibly create a simple Publisher document in both 2.1.1 and 2.2.0 which just includes some basic text, Lorem Ipsum, Filler Text or just type the characters A to Z in upper and lowercase and the numbers 0 through 9 and the standard punctuation marks and then export to PDF (labelled accordingly) using the settings you have been using so we have a PDF from both versions of Publisher as it may provide some clues as to what is going on.

[Peter Cusworth]

Hi @Hangman

Thanks for your reply. I have been working on my fonts today, and it seems the Postscript Type 1 fonts always cause this issue, at least on my computer. So I have been deleting them from my Font Book. I can reinstall a couple though for this exercise.

My other query though is, how do I create a document in 2.1.1? Do I need to download an old version, or can you save back to an earlier version somehow?

[Hangman]

1 minute ago, Peter Cusworth said:

My other query though is, how do I create a document in 2.1.1? Do I need to download an old version, or can you save back to an earlier version somehow?

I thought you may have still had version 2.1.1 on your Mac but I guess that makes little sense if you've updated it to 2.2.0 so ignore that suggestion, I just wanted to try and understand why this was working for you in an earlier version but not in the current version...

You will most likely be able to find a free version of Frutiger in either a Truetype (.ttf) or Opentype format (.otf) format online so you could download versions of the font weights used in your file, install them and update your file if needed and then see whether your exported PDF still exhibits the same issue or works as expected.

[Peter Cusworth]

I have downloaded a Truetype version of Frutiger now, and that seems to work OK. I will have a bit of updating to do on my regular jobs applying new or different fonts.

I had made up a basic document using 2.2.2.1 and a Postscript type 1 Gill Sans font, and the issue is still there (attached).

Looking at the info page on an to earlier PDF when the text was selectable etc, it was created by version 2.2.1.1. (see attached screenshot, left side). The right side shows the attached basic test file done just now. Something is different in the encoding software, but that might be the October Mac OS update?

Attached is a page from that earlier PDF if that is any help. It was using the original postscript Frutiger and is selectable etc.

Peter

 

extracted_Torque 0923- using 2.2.1.1.pdf Basic test 2.2.2.1.pdf

[Hangman]

Hi @Peter Cusworth,

Just a quick update to your thread...

The 'issue' appears to be due to an update to PDFlib, the PDF library used in v2.2 of the Affinity apps.

PDFlib 10.0.0 has seemingly deprecated support for Type 1 fonts though Section 6.1.5 in the PDFlib manual is (to me) a little ambiguous because, on the one hand, they're saying 'Support for Post Type 1 fonts is deprecated' but they then go on to say PDFlib supports ARM, PFM, PFA and PFB Postscript Type 1 fonts (unless I'm reading this incorrectly)...

I've tried exporting a file from both Publisher 1.10.6 and 2.2.1 using a PostScript Type 1 version of Garamond Pro and the version exported from 1.10.6 is selectable, the version exported from 2.2.1 is not selectable in Acrobat Reader because it gets outlined on export so this would seem to confirm that the PDFlib update in v2.2 is indeed the cause...

[Peter Cusworth]

Thanks @Hangman for the explanation and for looking into this. It's good to know what is causing the problem and that I have a work around now. Changing the fonts is not too difficult, although might be annoying when opening up some of my older jobs to have to change the fonts used, but at least I now what to do now.

 

Thanks again

Peter

[Hangman]

Hi @Peter Cusworth,

No problem, I wouldn't immediately have figured it out so it's certainly helpful to know the cause. I'm sure it's likely to trip a few more people up down the road as well so at least we know why it's happening now...

[Leigh]

Thanks for investigating @Hangman and you're correct - will deffo catch some users out.

[Hangman]

Hi @Leigh,

Maybe a blue 'tip' should be added to the appropriate section of the Help file to point this out, then at least it's acknowledged for those experiencing the same issue...

[Leigh]

3 hours ago, Hangman said:

Hi @Leigh,

Maybe a blue 'tip' should be added to the appropriate section of the Help file to point this out, then at least it's acknowledged for those experiencing the same issue...

I've logged this with the developers to see if there's anything that can be done. I will make an FAQ in the meantime but if we can't improve the workflow then I will see if we can update the help. Thanks again @Hangman 

[walt.farrell]

You might also consider adding a PreFlight warning, @Leigh, if you can't avoid the conversion to curves.

[Leigh]

Here's the FAQ: 

 

[Affinity Info Bot]

The issue "Text using PostScript Type 1 outline fonts are being converted to curves when exporting to PDF" (REF: AF-1387) has been fixed by the developers in internal build "2.4.0.2213".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.