I have a Word file that uses a client's font. When I convert to .pdf, the text converts as images. I've tried embedding the font, but when I go to the option to embed, the fonts are not listed in the Windows directory to add. When I check my C drive in the Windows folder and Fonts, they are listed there. I have to make this document 508-compliant, so it's not working for that. Any thoughts or ideas?
There are several ways to create a PDF from MS Word. Some produce accessible tagged PDFs, others don't.
What steps are you taking to make yours?
I'm using the "Save As" function. I've also used the PDFMaker and neither work.
Let's go back to the PDF Maker because it's really the best method to create an accessible PDF from MS Office.
Follow the steps here and let us know if that solved the problem.
I've already tried this. When I go to the window to embed the fonts, they do not show up in the Embedding Font Source list. They are in my Windows/Fonts directory on my C drive, but they don't show up here to add to the "Embed Font" column.
Ah, go back and reread the instructions.
You want the two yellow fields blank, as shown. And the items at the top are checked.
Match the screen capture exactly.
Just did this exactly as in the above instructions and when my document converts, it converts everything as an image and when I open, it automatically runs page recognition. I believe that this font just will not work with Adobe.
[EDITED: system lost some of my earlier reply and jumbled the text.]
Well, maybe, but I really don't think so. Even if the font didn't work, PDF Maker would substitute another font and you wouldn't end up with an image of the document in the PDF.
But let's check the font to be sure. What's the font?
Since you're on Windows, find it in C:/Windows/Fonts.
Find the font's icon.
Note, something's wrong with the forum system right now. I can't get it to post the correct screen captures.
Here's the missing sample from the 1st part of the above reply.
I'm not sure why, but my IT Department just ran it again and it worked this time. I guess it just took the IT touch. Thanks for the suggestions though.
Very glad you got it resolved!