Jean-Marie Schwartz:Do you mean that combining files in Acrobat could result in missing characters? Did I get what you mean? If so, does it apply to Quark Export as PDF too?
Yes, combining some PDFs using some Acrobat's produce PDFs that drop characters through some RIPs or other Acrobats, it was particularly common with German glyphs such as the double ss. I never found definitives but it was generally agreed that avoiding subsets (or avoiding combining or concatining using Acrobat or InDesign) would fix it, we had one customer plagued by it when he mixed CS3 and CS2 generated PDFs in InDesignCS3.
Quark Export uses JAWS so perhaps its more conservative about naming/encoding subsets and produces PDFs that can't suffer from the bug.
Matthais
how did you come across that link, I always enjoy it when someone picks an argument with a really senior figure like Leonard, not realising who they are dealing with
.
Second, as the follow-on to that, is your comment about needing the full embed for “late stage editing” is simply wrong. Adobe Acrobat will NEVER use the embedded font data for TouchUp – it will ONLY use an installed font that matches the embedded one. It must do so for legal reasons. Therefore, subset vs. full doesn’t matter – you still need the font resident on your computer to edit the text.
I think this is avoiding talking about the capabilities of certain versions of Pitstop.
The way I understand it is, that when the same font is embedded and two or more PDFs are joined
Subset A + Subset B = Subset C
Embedded A + Embedded A = Embedded A
... there was the puzzle of why the sun came out during the day, instead of at night when the light would come in useful.
Terry Pratchet