3 Replies Latest reply: Jul 11, 2013 1:15 PM by Mike Gondek RSS

    Cannot extract the embedded font error

    gwhPoster Community Member

      Hi everyone,

       

      When opening a pdf file, I get the following error:

       

      Cannot extract the embedded font 'QGCXJE+HelveticaNeueLT-Roman'. Some characters may not display or print correctly.

       

      Does anyone know what it means and will it affect the printing when I send it to a printer?

       

      Thanks for any help.

        • 1. Re: Cannot extract the embedded font error
          Bill@VT CommunityMVP

          As long as it displays correctly, there should be no problem with the printing. It is just a warning that apparently something was amiss in an embedded font and the result may not be as expected.

          • 2. Re: Cannot extract the embedded font error
            Mike Gondek Community Member

            I am getting the same error on making pdfs fomr Illustrator. Though everything looks good, this is not acceptable to send a pdf to the client for review, and was not happening before.

             

            My system

            OS 10.8.4

            Acrobat 10.1.7

             

            This does not happen on all files, but repetitively on certain series of files, so must be a font conflict in the files.

            Screen Shot 2013-07-11 at 2.36.51 PM.png

            Screen Shot 2013-07-11 at 2.38.39 PM.png

             

            hmm might be this zapf dingbat, did nto get a warning about missing

            Screen Shot 2013-07-11 at 2.46.09 PM.png

            • 3. Re: Cannot extract the embedded font error
              Mike Gondek Community Member

              Ok figured this out.

               

              Flushed the font cache (using Universal TYpe Client), the <Zapf Dingbats> false positive went away, made 9 new PDFs from troublesome files, and now they are good. The Zapf dingbats was the stars in a USDA symbol, and this all set off a chain of flase positive in Helvetica Neu, so I suspect my font chace had conflcit FOND ID numbers for those two fonts.

               

              Was a while ago, but curious if any of this relates to the original opster.