The
likely reason is that you both have a version of TrueType Arial with some
of the standard encodings AND a derivate of the same font with some CID
encoding in *the same* document.
When
merging such documents you actually may end up with bogus documents, even with
Acrobat 6.01. Actually, you might see in the Acrobat font list, that the CID
font is *gone* after the merge, and the characters represented by it now is
drawn with the TrueType version. Therefore the jumbled text
!!!
This
has nothing to do with the error message, however, and I wouldn't expect an
error message to be displayed, since the PDF in a technical sense still
is perfectly legal.
This
situation may occur when you with MS Word is using TrueType (or
OpenType) Arial and you e.g. both use plain language text AND Greek
characters or math symbols from the same Arial. In this case you'll both get
Arial as an embedded TrueType subset and an Arial with CID encoding
put into the PDF, which also is perfectly legal. Unfortunately, a merge
operation with Acrobat or PDF Library (which basically is the Acrobat
kernel) may not handle that situation correctly, not even with Acrobat
6.X.
There
are two solutions:
1)
Edit the original document and isolate non-roman characters into a different
font such as Symbol, and then re-create the PDF's and re-merge,
or
2)
Edit the Distiller PPD to add Helvetica as a device font (all four faces), and
then let the printerdriver substitute TrueType (or openType) Arial with the
device font (Helvetica) on the fly. This will force the roman Arial to be
downloaded as Helvetica and leave only the Greek/Math characters as a CID based
Arial.
Solution (2) is the easier, but will require that you have Adobe Type 1
Helvetica on your system to get it embedded, but you'll be able to merge your
documents because Arial no longer show up with different clothing in the same
source files.
All
the best
Jacob Sch�ffer
Grafikhuset
-----Oprindelig meddelelse-----
Fra: Dave Young [mailto:[EMAIL PROTECTED]
Sendt: 7. maj 2004 02:43
Til: [EMAIL PROTECTED]
Emne: Re: [PDF] "Unable to extract" and "SOS"
Fra: Dave Young [mailto:[EMAIL PROTECTED]
Sendt: 7. maj 2004 02:43
Til: [EMAIL PROTECTED]
Emne: Re: [PDF] "Unable to extract" and "SOS"
The original "SOS" post was an exclamation of dismay that a customer's pdf was causing jumbled text - both on screen and in print. I had the same problem-and several people on this forum and elsewhere offered solutions. The Adobe FAQ's said the problem was caused by combining files prepared in different versions of, say, Arial and Acrobat was unable to cope with that in the same document. The 6.0.1 patch was supposed to solve that problem.I dutifully applied the patch - the customer's files acted the same mysterious way. I took his original Word files and distilled them myself - Standard job options, 100% subset (thats supposed to make any variant of Arial have its own internal font number- as I understand it). But I had the same woeful results.I gave up - printed individual pages/chapters and copied the document rather than printing them (it was all text anyway - so I could get away with it). But what about next time? It seems to happen with only one customer - different people in a large organization - that may be using some font set over there that is squirrely.Any more thoughts out there?Dave YoungMcLean, VA----- Original Message -----From: "Jacob Sch�ffer"> Dov Isaacs wrote:
>> ... such as being hacked together via combination of multiple PDF files
>> with differing versions of Helvetica from different sources ... >
>
> If the document was merged from multiple PDF files with Acrobat 4.X this
> 'Unable to extract the embedded font XXX' problem is quite often seen,
> though the merged document actually might behave/print as expected on some
> systems/platforms after all.
>
> This problem is not isolated to Helvetica, however.
>
> With Acrobat 6 this risk has been even further reduced, perhaps eliminated.
> At least, I haven't seen it with documents created with Acrobat 6 yet :-)
