Skip to main content
stever95926846
Participant
August 14, 2019
Question

19.012.20036 introduced Cannot extract the embedded font 'HNQFLR+StoneSansLT-Identity-H' error

  • August 14, 2019
  • 29 replies
  • 19016 views

We have installed the update to 19.012.20036 and our PDFs now give this error.

Cannot extract the embedded font 'HNQFLR+StoneSansLT-Identity-H'. Some characters may not display or print correctly.

These SDS are generated from a software package, and have been working since 2011.

This is a production stopping issue, does anyone have any ideas?

    This topic has been closed for replies.

    29 replies

    Participant
    August 20, 2019

    Hey Guys, if you need your files for now, you can save as your file with PDF/A format in Adobe Acrobat.

    Participant
    August 19, 2019

    Having this issue with Reader and Acrobat....

    patrickrwilson
    Participant
    August 19, 2019

    We are seeing it too.  Not with Acrobat Pro or Foxit, but suddenly with this version of Reader.  I also sent over a small file for Vinod's testing.

    Adobe Employee
    August 18, 2019

    Hi All,

    We are working on the fix for the font issue and require as many PDF files having font issues to test it out. Request anyone having the issue to inbox me the PDF files.

    Thanks,

    Vinod

    Participant
    August 18, 2019

    We are having issue with Font RotisSansSerifStd-Identity-H

    Regards

    Abdusalam

    Adobe Employee
    August 18, 2019

    Pls. inbox me the PDF file

    ritaa4716155
    Participant
    August 18, 2019

    So I now have the problem with a different font on my PC. Hardly anything is displayed apart from a logo. However, this was an attachment to an email which I can read without problem on my Samsung S8 mobile. So what's wrong with the PC version of Adobe Acrobat Reader DC Vs. 2019.012.20036.

    brigudewri
    Participant
    August 18, 2019

    Please support for below error also, its impacting

    Cannot extract the embedded font 'IKYYWH+RotisSansSerifStd-Identity-H'. Some characters may not display or print correctly

    Docguy
    Participating Frequently
    August 16, 2019

    The irony is that if I upload the document to the Adobe Document Cloud, it opens the fonts without a problem.

    Participant
    August 16, 2019

    Hi,

    We are having the same issue with Noto Sans JP.

    This was the Font family assigned to all CPQ Quote Templates in our Salesforce org. Our customers are now unable to open quote PDF's in Adobe Reader.

    Participant
    August 16, 2019

    We have also had this problem, and it significantly impacts not just our own ability to open the PDFs, but our customers' ability to download and open the PDFs successfully.

    I tried replaced the .otf fonts with the .ttf versions of the same fonts, and it did not work when we regenerated a sample PDF.

    Docguy
    Participating Frequently
    August 16, 2019

    The problem is with Reader and with Pro; I have both. Adobe Support says that they don't support any third-party fonts not installed via Typekit. Their solution was for me to purchase Typekit to generate the PDFs.

    That is not a solution for many, many, many reasons. The most important of which is this is not just for newly-generated PDFs, it is for ALL PDFs. So our customers can't read content in our PDFs that we've been generating for the last 5 years with the "offending" fonts. Pro and Reader MUST be fixed. It is impossible to re-generate all the PDFs we've created over the last 5 years and get them in the hands of all the right people.

    If you are experiencing this issue, I have found that opening the PDF in MS Edge or Google Chrome allows you to see the embedded fonts, further giving proof that this is an Adobe issue, not a PDF/generator issue.

    Adobe Employee
    August 17, 2019

    Hi all,

    The engineering teams are aware of the issue and further investigating the root cause. We will share an update on this issue soon.

    Appreciate your patience.

    Regards,

    Vinod

    Participant
    August 18, 2019

    We have the same issue and waiting for your solution since 14th Aug. Kindly follow up with your Engg team and update with a permanent fix asap