It has been quite a while since this thread started or even had any activity. I thought it would be appropriate to provide an update from Adobe.
The problem of fonts being unexpectedly embedded in a PDF file even if the joboptions explicitly requested that they not be embedded turns out to be due to the dramatic growth of some of the Windows systems fonts such as Arial and Times New Roman. For Windows 10, some of these fonts have over 4000 distinct glyph definitions supporting not only Western Latin characters sets, but also Cyrillic, Greek, Arabic, and Hebrew plus extensive symbols. In the early days of Acrobat, they had less than 256 such distinct definitions. It turns out that Acrobat Distiller has a hard-coded limit of 4000 glyph definitions in a font; anything over 4000 glyph definitions forces embedding for that font (typically subsetted) in the resultant PDF file. The assumption was that such a large font was likely a font supporting an Asian language (CJK – Chinese, Japanese, or Korean) and that we needed to have that font embedded. Ironically, most such CJK fonts typically have well over 16000 distinct glyph definitions.
A fix will be put into place that will likely be available with Acrobat DC (and possibly Acrobat 2017) no later than November 2019 in which that glyph limit will be raised four-fold to 16000. That should suffice for virtually all non-CJK system fonts. (It will not be retrofitted to Acrobat 11 or earlier!)
That having been said, best professional practice is to always subset-embed fonts referenced within a PDF file to avoid problems of either a font not being installed on a recipient's system or that the font installed on the recipient's system has a different glyph complement or encoding resulting in errors in file display and/or printing. In recognition of this, Adobe changed the Standard joboptions in a recent release of Acrobat DC such that all fonts are always subset-embedded. The increase in PDF file size is a very small penalty to pay for reliable text rendering on any target system.
I will be closing this thread, but if anyone has further questions or concerns with regards to this issue, please feel free to contact me via private message on these forums.
- Dov