AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Stamp text corrupted adobe preflight12/25/2023 ![]() You will need to find out the actual end-to-end workflow and find what “extra steps” are being applied that effectively ruin the file. And we know that the modifications were not made by Adobe software by virtue of the fact that the font was not embedded and proper mapping tables were missing. Depending on the profile, the preflight inspection can also correct certain errors. Preflight inspects the file against a set of user-defined values, called preflight profiles. The created and modified dates being different that this is not the original file exported from InDesign. The Preflight tool analyzes the contents of a PDF to determine its validity for print production and a variety of other conditions that you can specify. The most plausible explanation of the problem is that the PDF file was improperly modified by some defective, non-Adobe software after it was exported from InDesign. Note that InDesign always embeds fonts and when using CID Identity-H encoding (as was done here), provides the CIDtoGIDMap table. Acrobat has no way to map the text in the PDF to glyphs in a font. And if you check the fonts being used they are all basic fonts: Arial. Its not with every PDF, just certain ones. This accounts for the gibberish you see on page 2 of the document. I too am experiencing the same issue with the latest version of Adobe. In conjunction with that, there was no Unicode mapping due to a missing CIDtoGIDMap mapping table for that font. This yielded a number of issues including the Monserrat-Regular font not being embedded for some of the text using same on page 2 of the document. I then ran the List potential font problems profile in Preflight in Acrobat Pro DC: ![]() However, it appears that the file has been modified by something between the time it was exported from InDesign and now the created and modified dates are different. Based upon what is seen in the document properties (see screenshot below), it appears to have been directly exported from InDesign 14 (2019) under MacOS. I downloaded and examined the file in question. ![]()
0 Comments
Read More
Leave a Reply. |