Luca Huelle
-
Posts
7 -
Joined
-
Last visited
-
kenmcd reacted to a post in a topic:
Korean (non-latin) font cannot be extracted from exported PDF if Embed subsets is checked
-
They both worked thank you so much! Could I be a real pain and ask you to convert Medium and Light (attached) as well? I can't seem to find any tools online that actually convert them properly NOTOSANSKR-LIGHT.OTF NOTOSANSKR-MEDIUM.OTF
-
Thank you for your explanation - clearly there's a lot to unpack here and it's all very complicated 😅! But still thank you for your explanations 🥰 If you could provide the TTF fonts that'd be great since that seems to be a suitable workaround for now - assuming it converted the Korean characters suitably as well (which I guess it might not have done given that might have been the whole reason the newer otf type was used in the first place... but it's worth a shot regardless).
-
Luca Huelle reacted to a post in a topic:
Korean (non-latin) font cannot be extracted from exported PDF if Embed subsets is checked
-
Thank you so much for the in-depth investigation, LibreTraining! Hopefully this gets a step closer to the root cause. So am I right in saying that it does seem to be something to do with sub-setting and embedding an OTF font? Does this happen with other OTF fonts or just Noto KR/other international fonts since it has a larger number of glyphs than perhaps expected maybe (because it includes non-latin glyphs)?
-
Hi, thank you for having a look at the issue! None of the issues I looked through in those search results are really related to my bug I think. They were using the wrong fonts, resulted in garbled output, had issues using the Adobe Fonts platform or eventually discovered it was actually a bug with InDesign and not the PDF reader. Could you give some examples of "elsewhere"? I've tried to view the PDF in Microsoft Edge, Firefox, Sejda & PDF Chef (online) - none displayed the font correctly although some had a crack at some of the individual letters at least but never all of them.
-
Further potential note of interest, NotoSans KR are OpenType font (.otf) files whereas NotoSans are TrueType font (.ttf) files when downloaded from Google Fonts (links in original post).
-
I have a document (Font Embed Example.afpub) using Noto Sans Korean [KR] Bold (Google Fonts) and Noto Sans (Google Fonts) but still only using Latin characters. Both fonts are listed as 'Installable' in Windows font settings: However, when exporting the document as a PDF from Publisher with the Subset fonts option checked, the exported PDF (Font Embed Example (subset).pdf) is missing all styles (i.e bold and regular) of only the KR font: The regular Noto Sans font however embeds perfectly well: Unchecking Embed subsets fixes the issue, at the expense of increasing file size from 1MB to almost 8MB (since the Korean font is quite large) (Font Embed Example (non-subset).pdf) which is too large for some file upload limits. I think this may be a bug in the PDF exporter. I haven't conducted any testing with other non-latin fonts but this may yield similar results. I'm running the latest Publisher version on Windows 11. The same issue also occurred on my laptop running Windows 10.
