"Create PDF" through Adobe Create PDF cloud service from Word 2016 for Mac does not maintain fonts
Steps to reproduce:
- Create Word document in Word 2016 for Mac
- using League Gothic, Monserrat, and Goudy Old Style fonts
- Click "Create PDF" under the Acrobat tab in the Ribbon
- allow it to create with the Adobe Create PDF cloud service
- Check created PDF
Expected to see:
- League Gothic, Monserrat, and Goudy Old Style fonts
- All fonts replaced with Times New Roman
OS: macOS 10.13.2
MS: Word 2016 (version 15.41)
Adobe: CC, Acrobat Pro DC (version 2018.009.20050)
Thanks for reporting the issue.
It is currently under review.
We will keep you posted.
rebecca bowes commented
I have a similar situation but using Word on a PC. When I export or save to PDF, the fonts Sora Semibold and Source Code Pro render as a serif font like Times, but with bad letter spacing. My colleague used the same Word doc and saved to PDF. In her instance the Sora Semibold appeared as Sora Light (or regular) in the PDF.
My workaround is to use the MS Word Print to PDF command which displays the fonts correctly, BUT when those PDFs are put on a web site with a thumbnail of the first page the heading in the thumbnail is garbled and unreadable.
I'm attaching the Word source file, the two PDFs, and a screenshot of the thumbnails.
I'm experiencing the same exact problem as posted on April 13, 2020. This is not a niche issue – creating documents is the main purpose of the software. How is it not fixed yet?
Rebecca Aquino commented
Same here. I used to work for Adobe and I thought the full Acrobat will solve the problem as well, as it used to be. Right now Word Mac to PDF is broken to preserve fonts and links.
Anne Sepulveda commented
Same issue. I thought having a Paid Adobe Acrobat will fix it. Unfortunately, no. It's been 1 year and 6 months and I don't Adobe will ever fix this for Mac users. And their customer service is the worst.
Adam Krpan commented
Agreed, I also have this issue and it's making me jump through some ridiculous hoops (as of yet, I still don't have a solution).
EDIT: I just found out that I can mostly use macOS Pages to open the Word document, and then export from there. Won't work for everyone though as it has issues with some fonts, but it at least got me past my current stopping block.
OS: macOS Catalina Version 10.15.2
MS Word for Mac: Version 16.32
Adobe Acrobat Pro 2017: Version 2017.011.30166
When converting a word document with hyperlinked text, a problem emerges. When using the "print to PDF" option in MS Word, the resulting PDF does not retain the hyperlinks contained in the original document. When using the "Save As PDF" function, there is a dual issue. If the "Best for printing" option is used, the resulting PDF does not retain the hyperlinks from the original document. If the "Best for electronic distribution and accessibility" option is used, the resulting PDF retains the hyperlinks but changes my body font (Helvetica Neue) to what appears to be Garamond or some similar serif font.
This is UNACCEPTABLE.
Given the cost of both MS Office Suite and Adobe Acrobat Pro, this shouldn't be an issue. In fact, this has NEVER been an issue in the past. I am not sure whether this is an update issue with Word, an update issue with Adobe, or an issue with macOS switching to 64 bit. Whatever the issue is, it needs to be fixed. As it stands, conversion to PDF simply does not exist, as to lose either my links or my fonts is to lose the document itself. All aspects of my document represent intentional choices that I made, and unless they are converted identically, then they are not converted at all. Please fix this...PLEASE.
I am experiencing a similar issue with FrameMaker 2017, Adobe Distiller XI and Adobe Acrobat Pro XI. We use a font called IBM Plex Mono for code samples. When printing to paper from PDF, that font prints out in some instances, but not in others (just whitespace).
I'd like to echo Jonathan's concern: this is a core feature. Where's the update?
This post is six months old and there are no updates. It concerns a core feature of Acrobat. So, what's going on?