Jump to content

Recommended Posts

I created FlowCharts using Artboards with Affinity Designer, very easy and successful.

The text was in English, I saved copies in AF format and as PDF. The PDFs were printed and all the text was, as expected, in perfect English.

I have just reopened the file in Affinity Designer to incorporate suggested amendments, and notice that some letters in some words have been replaced with symbols that I don't recognise. The attachment shows the 'new' version of what I typed - and I checked the previously printed copies which confirmed that this change has only occurred on re-opening the file today.

The text was entered as:

Limited information to branches, e.g. advertising meetings b....

Foreign membership number queries...

I checked the language in preferences and it was set to English (United States), I have just reset that to English (United Kingdom and (not surprisingly) the foreign symbols are still in the text. This means I have to check the spelling in 14 artboards/flowcharts, thankfully the red underlining will help.

Any ideas why this happened, please?

Hilary

416764214_ForeignLanguageAlphabet.JPG.18216cfc626e13c7f3bba193076f0a81.JPG

Share this post


Link to post
Share on other sites

A closer look suggests that most of these 'translations' involve limited combinations of letters such as 'ting' in existing and printing; 'tion' as in option, and 'till' as in still.

Must get the job done, though, deadline looms.

 

Hilary

Share this post


Link to post
Share on other sites

Hi Hilary :)

Sorry to see you're having trouble!

Could you please confirm the following for me:

18 minutes ago, Sunset said:

I have just reopened the file in Affinity Designer to incorporate suggested amendments, and notice that some letters in some words have been replaced with symbols that I don't recognise.

  • When reopening the file, did you open the .afdesign file, or import the PDF as a new document?
  • What font was used in the document?
  • Have you recently changed, added or removed any fonts on your system?

Could you also please provide a copy of the .afdesign document, alongside your exported PDF to the following link for me?

https://www.dropbox.com/request/rGMoL8H8L4sSrZulNWLg

Thanks in advance!

Share this post


Link to post
Share on other sites

Those nonsense replacements are failures to interprret original "ti" and "tt" ligatures. Just type them again and you should be good. 

I am not sure but I think Affinity apps have improved in encoding ligatures properly when exporting to PDFs but earlier they used directly the ligature codebase glyphs for ligatures, and when subsequently opening these pdfs the ligatures were shown with nonsense replacement glyphs like here.

Not all fonts have ti and tt ligatures, but here is e.g. Lato, which does (top row: standard ligatures turned off; bottom row: standard ligatures turned on (default value)):

ti_ligatures.jpg.d5d61a597d42f1f31bd39a170d851918.jpg

And unfortunately Affinity apps have not improved at all, as this is what happens when the PDF produced from Designer (attached below, and showing correctly the ligatures) is opened in Designer:

ti_ligatures_pdf_oepened.jpg.4b144f1ca402e990a2f2a8a04d291a3b.jpg

As can be seen, the "ti" and "tti" ligatures have been replaced with nonsence glyphs. This happens when ligatures are encoded improperly.

Note however that Designer should retain ligatures when saving and opening an .afdesign file so this confusion typically only happens when opening a PDF file produced by an Affinity app. But it may be that it also happens when opening an older .afdesign file format with a newer version (???)

 

 

ti_ligatures.pdf

Share this post


Link to post
Share on other sites
20 minutes ago, Dan C said:

Hi Hilary :)

Sorry to see you're having trouble!

Could you please confirm the following for me:

  • When reopening the file, did you open the .afdesign file, or import the PDF as a new document?
  • What font was used in the document?
  • Have you recently changed, added or removed any fonts on your system?

Could you also please provide a copy of the .afdesign document, alongside your exported PDF to the following link for me?

https://www.dropbox.com/request/rGMoL8H8L4sSrZulNWLg

Thanks in advance!

Thanks,

I confirm that I opened the .afdesign file, the PDF file was only for sending by email to others,

Font - interesting, all the 'changes' were in one text box only, and I can't tell whether that is relevant or not, but the font used was calibri regular 10.

No changes have been made to the fonts on my system in the relevant period.

The document is of a slightly sensitive corporate nature, but I trust the staff at Affinity to recognise that.

I'll send the file as requested.

Note - I had already correct some errors on chart 4, starting with 'newsletter' at the bottom of the page and working upwards).

Share this post


Link to post
Share on other sites

Thanks for the info Hilary :)

I'm almost certain that you may have imported the exported PDF back into Designer without realising it - as I've downloaded your PDF and opened it directly in Designer and it shows exactly the same issue you've reported on this text only.

This is a known issue with Calibri ligatures when importing PDFs, so I'll bump this with our developers now.

I've checked with our QA team and we personally cannot see a 'way' in which Affinity would have changed these ligatures between opening/saving/closing the file, and we heavily suspect this has happened when opening the PDF - likely accidentally.

Share this post


Link to post
Share on other sites
2 minutes ago, Dan C said:

Thanks for the info Hilary :)

I'm almost certain that you may have imported the exported PDF back into Designer without realising it - as I've downloaded your PDF and opened it directly in Designer and it shows exactly the same issue you've reported on this text only.

This is a known issue with Calibri ligatures when importing PDFs, so I'll bump this with our developers now.

I've checked with our QA team and we personally cannot see a 'way' in which Affinity would have changed these ligatures between opening/saving/closing the file, and we heavily suspect this has happened when opening the PDF - likely accidentally.

Anything is possible, I was working to a tight deadline, I hadn't done a flowchart since college in 1973 so I created my own symbols, it is possible I also flitted between my desktop Windows and my Macbook - all of which I love being able to do with Affinity. And, although I'm 'absolutely certain' that I opened the afdesigner file from the 'Open Recent' menu today - perhaps I didn't!

Thanks for checking and forwarding it to the developers. I've fixed what I needed to do, job is done ahead of schedule, I'm happy.

 

Hilary

Share this post


Link to post
Share on other sites

If I remember correctly, then Subsetting the Font has to be unchecked. You'll find this after hitting the More button in the export dialogue.

Share this post


Link to post
Share on other sites
16 minutes ago, Joachim_L said:

If I remember correctly, then Subsetting the Font has to be unchecked. You'll find this after hitting the More button in the export dialogue.

I think Affinity at some point changed the code so that by default sub setting is no longer used. But the actual reason for this error is in incorrect coding of ligatures in exported PDFs. This does not happen when creating PDFs from InDesign. It does not happen even when exporting from Xara, which seems to share some common code with Affinity apps.

This is a pdf created by Xara, and when it is opened in Designer, it shows ti and tti correctly (without ligatures). This is proper behavior.

ti_ligatures_from_xara.pdf

Share this post


Link to post
Share on other sites
11 minutes ago, haakoo said:

I think @Joachim_L is right that one has to export to pdf with the whole font embedded instead of just the subset to make sure the ligatures get exported

The ligatures do get exported (as can be seen from the PDF attached in my post above), but this may also be dependent on the rendering app. E.g., I think that Chrome PDF viewer could not show ligatures encoded in PDF in the way Affinity apps do it, unless the font is included completely (without sub sets). But this is just a workaround for a problem that is basically caused by not doing it right in the first place.

Share this post


Link to post
Share on other sites
7 minutes ago, Lagarto said:

The ligatures do get exported (as can be seen from the PDF attached in my post above), but this may also be dependent on the rendering app. E.g., I think that Chrome PDF viewer could not show ligatures encoded in PDF in the way Affinity apps do it, unless the font is included completely (without sub sets). But this is just a workaround for a problem that is basically caused by not doing it right in the first place.

I think the issue is with Affinity recognizing the ligatures when it reads the PDF if the PDF was exported originally with the fonts subsetted.

Share this post


Link to post
Share on other sites
9 minutes ago, walt.farrell said:

I think the issue is with Affinity recognizing the ligatures when it reads the PDF if the PDF was exported originally with the fonts subsetted.

I am not sure what you mean, but I think there are just multiple errors first in encoding, and then when decoding.

Interestingly, Xara can interpret the hard-coded ligatures when it opens the Designer created PDF attached above. The glyphs are codebase ligatures instead of ones determined by an attribute, but get correctly rendered. When Xara opens the PDF that was exported from Xara itself, it renders ligatures correctly, but as atttibutes. That is, Xara behaves perfectly both when it exports and imports text containing ligatures.

Share this post


Link to post
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.


×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.