I am using MacBook Pro and have Microsoft Word 2016 and Adobe Acrobat 2015 version installed.
Objective: to convert microsoft word file to pdf document with all internal links (table of contents, cross reference links, etc) working.
What I've done:
First try: converted the document to pdf using 'Save As' option straight from Ms. Word, chose 'best for online viewing' to retain all the links. What happened was, the links were all working but all original fonts are gone and replaced with some sort of generic font throughout the document
Second try: tried to create pdf using Adobe Acrobat, it automatically converts the word document into pdf but later found out that all the links were not working at all.
I need to know how to convert a word document into pdf without losing the hyperlinks/internal links and original font. Not sure why Ms. Word just decided to change all of my fonts....
Please click on Acrobat ribbon in Microsoft word application and select preferences.
Then check box for Add links under Security tab.
Now try to convert word file to PDF using Create PDF option under Acrobat ribbon.
Let us know if issue still persists.
Unfortunately, when I click on Acrobat ribbon in Microsoft word application, it only shows Create PDF option and nothing else. Is this an issue with Microsoft Word 2016 for Mac?
Could you please share the screenshot of the options you get when you click on Acrobat Ribbon.
Please also let us know the exact dot version of Adobe Acrobat and OS installed on your system.
Hyperlinks aren't preserved in the Mac version.
I had the same problem on my Mac (using Word for Mac 2016). I was using only Mac-installed fonts, and anything besides Arial was replaced by something else. Since I wanted to keep hyperlinks, we couldn't use the File > Print (or the Save As Adobe Acrobat) option.
It took me a long time and some persistence, but I finally got help on the issue from a very helpful Adobe support person, @Ankur Sharma. He was able to reproduce the problem and lodged it as a bug (ADC-4212190).
While we were looking at other options, I found out that the Save As Adobe Acrobat option uses Distiller, which on the PC version can preserve hyperlinks, bookmarks, etc., but not on the Mac. So we also put in a feature request (ADC-4210906) to add this functionality to the Mac version too. Obviously, the more people they hear from who express an interest, the more likely it is Adobe will act on it, so please, Mac users, let Adobe know we want this.
For the hyperlink issue, if you have Adobe Acrobat Pro DC you can use that app as a work-around for the broken hyperlink export from Word.
I have Acrobat Pro DC, but the problem with using that approach or the Word plugin is that our installed fonts are replaced by substituted ones. That, as it turns out is a bug, which supposedly is getting looked at. But we've had some other issues with that approach, such as Noteref fields being treated like new footnotes (which screws up the footnote symbol sequencing).
The best solution for us would be if Adobe added the ability to keep bookmarks and hyperlinks in the Mac version of Distiller -- just as the PC version does -- but since that's a feature request, we need other Mac users to show an interest.
I tried this on a couple of different word files and got the following error.
Acrobat could not open 'Becca Letter.docx' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).
To create an Adobe PDF document, go to the source application. Then print the document to Adobe PDF.
Follow the instructions.
No, this just uploads the word file into the cloud (why?!) and then the hyperlinks in the online created PDF (data breach!) still don't work
This appears to still be an issue a year later... you have to either pick having fonts download OR hyperlinks - they don't work together. When will this be fixed or are there any workarounds?
Not without significant changes in the architecture of Microsoft Office for Mac…
I'm assuming they still have not made those changes. Has it improved at all in Office 365?
It's already 2018 and still Adobe doesn't have an answer for this? How do we resolve this for mac users? I usually do tv program decks for a tv network and we attach hyperlinks for the tv trailers on our pdfs that we send to our sales clients. Hope we can do something about this. Hope Adobe and Microsoft can look into this problem. It's been years and I still see this problem on mac users. Please... 😃
It is August 6, 2020.
I am working on a project for a client that requires I use a specific font (Mrs. Eaves font deck -- which is listed in Adobe Fonts) <<and>> I have created a linkable TOC. I am working with Word for Mac (V16.39) on a Macbook Pro. I am able to either retain the font <<or>> the linkable TOC <<but>> not both. I've tried utilizing create PDF and print to PDF and export to PDF options, though I get the same results -- font <<or>> TOC links are retained <<but>> not both.
I've tried working with Adobe but they keep directing me to help pages for Word for PC issues. I just found this thread today. Has anyone figured out how to make this work? I know my client is losing faith in me. I really don't need my reputation ruined because of this. Please help! I need a workable solution!
It is 2021 and this is still an issue. It has driven me mad. The solution I have found rom testing every way to create a PDF appears to be something to do with the 'Adobe Create PDF cloud service'. The only way to both create a PDF with embedded fonts *and* retain hyperlinks is to disable the 'use Adobe Create cloud service'.
From the Acrobat tab in Word's ribbon click 'create PDF' and then click 'No' to create a PDF without using this service if prompted. If you are not prompted maybe you already agreed to go into the Acrobat 'preferences' option in the Word ribbon and tun on then export without cloud service and then turn off the preference prompt tickbox so you don't get asked each time (if that makes sense).
Not sure what the 'Create Cloud service' does that is a benefit, but it seems to mess this up and maybe something to do with what fonts are installed locally or installed via Adobe fonts.