InDesign CC 2019 - font error issues with PDFs
When latest InDesign CC 2019 creates a PDF using certain fonts, an error message appears when opening PDF in Acrobat Pro DC: "Cannot extract the embedded font 'JLUSWO+fontname'. Some characters may not display or print correctly."
Never had this issue with previous InDesign versions. The same PDF opens, views and prints perfectly in Preview. Creating PDFs by other applications with the same font are fine.
HELP!
We have released InDesign CC2019.0.2 with lot of stability fixes. If you are not on 14.0.2.324 then I would recommend you to upgrade to latest version as it is more robust.
If you still face this issue even after updating, please send the following information to santalwa@adobe.com :
• Error snapshot or video recording of the issue?
• Is(Are) the issue related to a specific document(s)/asset(s)? If Yes, Can you please provide the document(s)/asset(s)? Please package the entire document(To package the document, Go to File → Package)
• Does Trashing preference and cache, please create a backup of Preference and cache before trashing them, help to resolve the issue?
Adobe InDesign Team
-
Grace Shum commented
Hi, I'm having the same issue now. I have the most up-to-date Indesign app. Version 18.4 on the CC cloud. I'm having this error code appear in Adobe Acrobat. The font in question is an Adobe Font (Gibson), and not a TrueType font (that I'm aware of). I have tried looking at past forums to answer my question. I have tried running the Preflight check but it does not seem to find any issue. Visually, I can tell there is a problem with the pdf becuause when I upload the file to my website as a hyperlink. The font weights are all slightly distorted. I am not sure what to do. can you advise?
-
Lisa Jackson commented
Hello, I am running into the same issue--using our Corporate font that I have used for years. I reinstalled the fonts after this message, but it did not correct the problem. I am exporting a PDF from InDesign, and when the PDF opens, I receive the attached message. Thank you!
-
Heidi commented
I had the same issue. I opened an older file for some minor updates and then got this error when exporting to PDF. After trying all the work-arounds posted here plus some others suggested on other sites (nothing worked) I noticed that under the font name drop-down for the font that was giving the error message, that even though the font family name was correct, the weight/style drop-down had changed to read "(0)" instead of the usual bold, italic, condensed, etc. When I manually changed all instances back to their proper weights & styles, the PDF exported correctly. I hadn't touched the text which used this particular font when I made my other file updates so I think it may be something in the latest INDD software update interacting with an older font that kicked it out. The file I was updating is about 10 years old and is updated annually. This is the first time it's acted up.
I'm on the latest version of INDD CC, Mac Catalina 10.15.7. The font is a PostScript Type 1 outline font.
-
[Deleted User] commented
IF you are on mac, opening the PDF file first in Preview and doing an additional export to PDF fixes the issue. After that, the files open perfectly in Acrobat.
-
We have released InDesign CC2019.0.2 with lot of stability fixes. If you are not on 14.0.2.324 then I would recommend you to upgrade to latest version as it is more robust.
If you still face this issue even after updating, please send the following information to santalwa@adobe.com :
• Error snapshot or video recording of the issue?
• Is(Are) the issue related to a specific document(s)/asset(s)? If Yes, Can you please provide the document(s)/asset(s)? Please package the entire document(To package the document, Go to File -> Package)
• Does Trashing preference and cache, please create a backup of Preference and cache before trashing them, help to resolve the issue?Adobe InDesign Team
-
Nia Gough commented
This also happens in Illustrator as well as InDesign. It means I have to use an older version of CC
-
Anonymous commented
Same problem here. Any fix yet?