Dond10 Posted March 17, 2019 Share Posted March 17, 2019 I have found that when I have exported to PDF for web that any word beginning with a lower case (f) followed by an (i) will lose the (i) character. Exporting to PDF for print is OK attached example exporttopdf.afpub exporttopdf4.pdf Dond Windows 10 Pro, 8th gen i5-8250U, 8gb ram, 256gb PCIE SSD Link to comment Share on other sites More sharing options...
Alfred Posted March 17, 2019 Share Posted March 17, 2019 I’m not on my Windows machine so I can’t check right now, Don, but this sounds like a problem with ligatures: f followed by i is usually replaced by a fi ligature so that the dot on the i doesn’t clash with the terminal at the top of the f. Try turning off the ‘standard ligatures’ OpenType feature for the font. Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.4.1 (iPad 7th gen) Link to comment Share on other sites More sharing options...
kenmcd Posted March 18, 2019 Share Posted March 18, 2019 The "fi" ligature is one of those old legacy ligatures which are included in most (all) Unicode fonts. Applications like APub, LibreOffice, Word, etc. usually automatically replace these using an auto-correct feature. So disabling OpenType standard ligatures will not turn them off. You can disable auto-correct, or just remove those from the auto-correct dictionary. Another workaround is to insert a zero width non-breaking space between the characters to prevent the ligature from being applied. Link to comment Share on other sites More sharing options...
Dond10 Posted March 18, 2019 Author Share Posted March 18, 2019 I've been using PagePlus for a few years with the document that I've just noticed this problem with in afpub and experienced none of this. I had used the optimise for fast web view with PP too. How do you disable auto-correct and looking through the auto-correct list the "fi" is not there. This sounds a bit of a faff for normal users. Dond Windows 10 Pro, 8th gen i5-8250U, 8gb ram, 256gb PCIE SSD Link to comment Share on other sites More sharing options...
Dond10 Posted March 18, 2019 Author Share Posted March 18, 2019 I have found a way round this issue. In the Character Studio - Typograph - you will see the button for "fi" (standard ligatures), as you have mentioned, this is selected by default. Click this button to deselect and when exported it exports correctly. exporttopdf16.pdf Alfred 1 Dond Windows 10 Pro, 8th gen i5-8250U, 8gb ram, 256gb PCIE SSD Link to comment Share on other sites More sharing options...
kenmcd Posted March 18, 2019 Share Posted March 18, 2019 I guess I made an assumption which is not correct. Was messing with the fractions a few days ago and they do work that way. So I assumed that like other apps APub is doing the same for other legacy ligatures. But they are not there in the auto-correct settings. Tried to test your doc above and replicate the results. Getting some different results (and some odd results). I suspect it is because you used ArialMT which is a font flavor I do not have. I have the standard Arial that came with Win7, (and other versions from Win10, 8.1, XP, etc). I also have the full Arial MT Pro family. These different sources have very different ligatures features. I would like to test the exact ArialMT version that you used. Would it be possible for you to PM it to me for testing? Link to comment Share on other sites More sharing options...
Staff Gabe Posted March 28, 2019 Staff Share Posted March 28, 2019 Hi all, Sorry for the delayed reply. I could not reproduce this in the latest build. Can you please check it again and confirm if it's still an issue? Thanks, Gabe. Link to comment Share on other sites More sharing options...
Recommended Posts