Jump to content

Recommended Posts

When exporting as PDF for web it is default to only embed uncommon fonts.

I have recently exported a file for web using Arial and, when viewing on iOS devices (possibly Android also), the "i" is missing each time it is after an "f" ...a kerning issue.

Before, I only noticed that it effects font styles, but this is annoying. Couldn't it be default to embed all fonts in this situation? Otherwise I need to remember to switch it in the extra settings on export.  

Share this post


Link to post
Share on other sites

It seems more a problem with ligatures, and the "fi" one doesn't appear because your iOS device use a different Arial font that doesn't support them or your app doesn't understand them.
Try to disable them or embed the fonts in your PDF.

2019-05-15_224414.png.c50782985b994de1339fbd54d25b93f7.png

Share this post


Link to post
Share on other sites

Yes, but my point is  is for the developers to consider making all fonts embedded when exporting PDFs for web the default ...and  only uncommon fonts an option. 

Share this post


Link to post
Share on other sites

Making all fonts embedded will bloat the PDF file and therefore increase loading times.


Alfred online2long.gif
Affinity Designer 1.6.5.123 • Affinity Photo 1.6.5.123 • Windows 10 Home (4th gen Core i3 CPU)
Affinity Photo for iPad 1.6.12.86 • Affinity Designer for iPad 1.6.4.45 • iOS 12.2 (iPad Air 2)

Share this post


Link to post
Share on other sites

This is a tricky issue, I think, and I wouldn't know what to suggest. I certainly wouldn't want to bloat the file size for web, but on the other hand, I can easily see myself using "export for web" and blissfully being ignorant that all my ligatures (which I always use when available) are not showing errors on mobile devices.

I take the presets as "recommended" settings for each situation, and in this case, it would have led me astray, and I wouldn't have even known that this were an issue had I not read this thread.

Share this post


Link to post
Share on other sites
On 5/15/2019 at 10:36 PM, AnGwer said:

on iOS devices

And on macOS, too: Look where the URLs in the attached PDF guide you, when you open the PDF in Apple's Preview.app. – It gets stuck at the 'fi' in 'affinity', too.
Whereas it works when opening the PDF in Acrobat for instance.

170330-1 text url w 'fi' mac.pdf

 


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites
58 minutes ago, thomaso said:

And on macOS, too: Look where the URLs in the attached PDF guide you, when you open the PDF in Apple's Preview.app. – It gets stuck at the 'fi' in 'affinity', too.

That at least does work on my Mac in Preview:

1333625320_ScreenShot2019-05-17at9_16_55AM.thumb.png.c9bdffd5815797a88564b9b927b05e62.png

 

I think it is an issue with the installed font, as Wosven suggested.

 

 

Share this post


Link to post
Share on other sites
1 hour ago, garrettm30 said:

That at least does work on my Mac in Preview:

Interesting. Did you click + to get to the browser, or did you just read the popup in your screenshot?

With the 2nd link of the PDF I end up either there:  https://forum.af/   (+ error message in the browser window) or there: 
 https://www.serif.com/de/?topic/85461-kerning-issue-in-export-for-web  (which appears to be a re-directed result but not this forums page)

It appears to depend at what position I click on the text line (which actually has no html in the background).
 

1 hour ago, garrettm30 said:

I think it is an issue with the installed font, as Wosven suggested.

Yes, the ligature "fi" issue. That's why I posted it. I agree, with a default application setting such a result should not occur, as you pointed out already.


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites
1 hour ago, garrettm30 said:

That at least does work on my Mac in Preview:

1333625320_ScreenShot2019-05-17at9_16_55AM.thumb.png.c9bdffd5815797a88564b9b927b05e62.png

I think it is an issue with the installed font, as Wosven suggested.

That would be because it is recognizing that text string (because that's all it is) as a URL.

In Acrobat, this behavior can be turned off.

Capture_000032.png.5b1405366904c9748b71e8bc1be612b0.png

I set that default preference to not having this behavior. One cannot really test URLs in a PDF with it turned on.


My computer is a nothing-special Toshiba laptop with unremarkable specs running Windows 10 64-bit.

Share this post


Link to post
Share on other sites
58 minutes ago, thomaso said:

Interesting. Did you click + to get to the browser

I did try that. It successfully went to the intended link. I just included the popup in my screenshot to show what part was interpreted by Preview as the URL.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×