Converting on Word doc to PDF makes all docs PDFs

I tried to convert a document from Word to a PDF. Now all documents on my computer are PDF's.

Can you tell us, step by step, how you tried to convert, and what software you have?

Similar Messages

When i convert a word file with a hyperlinks to a PDF file it doesn't work ?? thanks in advance for helping me

when i convert a word file with a hyperlinks to a PDF file it doesn't work ?? thanks in advance for helping me

using microsoft word.
the hyperlink doesn't work in the pdf file (adobe reader).
adobe reader xi.
my operating system windows 8.1.
the attached screen is appeared.

How do I convert a word file larger than 100 mb to pdf?

I use the adobe online pdf service to convert word files. I have a file that is 101mb and the converter won't upload and convert the file. How do I convert this word file to pdf now?

Hi adrentcdc,
There is a 100 MB file-size limit for uploading to the Adobe PDF Pack online service. Since no such limitation exists for Acrobat, you could use that to convert the file to PDF. You're welcome to download a free 30-day trial, and give it a spin. For more information, see www.adobe.com/products/acrobat.html.
Best,
Sara

Blank Page appears after converting MS Word (2010 on Win 7) document to PDF using Adobe Acrobat XI

Hi,
Even after updating to the latest version of Adobe Acrobat Pro XI (11.0.2). While converting a MS Word 2010 .docx format document to .pdf, the cover page with text, image and background color, appears blank with only the background color.
Apperciate if someone can give me a resolution for this issue.
Best Regards

The coverpage gets converted in Acrobat.com cloud service. Is Abobe going to fix this bug in the Acrobat XI version too?

Word for Mac 2011 Opening all Docs/Crashing

Hello,
Today, after a restart of my MacBook Pro (Late 2013, Running Yosemite 10.10.1), Microsoft Word opens ALL recent documents to the point where it causes the program itself to error out and crash (though it does send a report to Microsoft).
I have tried several things (all found on Google, including moving com.microsoft.office.plist to the desktop). However, the issue still occurs.
Any help/suggestions/fixes for this?
I am at a complete loss, and I have much work to do.
Thanks,
Heather

Deleting com.microsoft.office.plist won't do it.
Follow these steps
http://support.microsoft.com/kb/2398768
Before you do that two things:
(1) be sure you have a good backup
(2) be sure you have your hands on your original Office 2011 install case and DVD.
Then Reinstall from DVD
Enter your product #
Then upgrade. It will take a few times before you get to final upgrade to current Office version. 14.4.7

Error message: Missing PDF maker files in Word 2007

OK, I am beyond frustrated. I have had nothing but trouble with Windows Vista and Adobe Acrobat. Please help!!!
What happens: first, the pdf addin for Word 2007 suddenly becomes disabled, for no apparent reason. Forget about trying to re-enable it through the Add-Ins menu, because Word tells me that the "connected state of Office Add-Ins registered in the HKEY_LOCAL_MACHINE cannot be changed". This is a problem for me, because I use a special font (Vietnamese) that sometimes gets corrupted when running pdf maker. The only consistent way I have found to avoid this problem is to run the pdf maker as "Quick PDF" and as far as I can see that option is only available through the pdf addin in Word, I have never been able to find it when I open the Acrobat program and create a pdf from there.
Second problem: shortly after the pdf addin becomes disabled, my Acrobat program loses the ability to create pdfs altogether. I get the error message "Missing PDF maker files". Yes, I have tried repairing the installation and re-starting my computer per the instructions given. It doesn't fix the problem. I also tried looking in the Knowledge Database on this website, but it appears that the instructions they have to fix the problem there are for earlier versions of Word, not 2007, because my version of word does not look like the version of Word in their little videos.
This is the second time this has happened. The first time I resolved the problem by a) re-installing Acrobat, which is a pain because it involves calling Adobe and wading through their customer service to get a new installation number, and b) paying a computer repair service to dig deep into the guts of my computer and convince it to change the Office Add-ins to allow the pdf addin again. It worked for about 6 months, and now I have the same problem again. For some reason Vista is spontaneously disabling Acrobat.
I simply cannot deal with this every few months. We all know that Vista is a crappy program, but I run a business and I need a program that works with whatever crappy program Microsoft puts out. Please, can anyone give me suggestions about how to re-enable these functions when Vista disables them?
Thanks in advance!
Alycia

for Office 2007, see if this Microsoft product will work for you
http://www.microsoft.com/downloads/details.aspx?FamilyId=4D951911-3E7E-4AE6-B059-A2E79ED87 041&displaylang=en

How do I access Adobe from Word to convert a word document to pdf?

How to I access an Adobe command in Word to convert a Word document to pdf?

Certain versions of Word will have an Adobe PDF menu in the ribbon, which allows you to convert the Word file you're viewing to a PDF directly, maintaining all the links, bookmarks, destinations, etc. in it.
The other option is to use the PDF Printer and print the Word document to a PDF. This will result in a "flat" copy of the file, without any of the meta-elements described above. Basically the same as printing it out, only you use a virtual printer that generates a PDF file.

Why do colours change when converting from Word to PDF

I am converting word files to pdf, however the header and footer background colours change once converted. How can I stop this happening?

Depends on how you are creating the PDF. If you are using PDF Maker (the create PDF button), then check the preferences in that menu. There is an entry for the settings file selected. If you are printing to the Adobe PDF printer, the settings file is listed under the settings tab of the properties menu.

Converting from Word to PDF and printer settings

I have a program that writes letters automatically in Word and if we have a PDF file as an enclosure when the letter prints, it actually converts the word document as a whole to a PDF. This part works great, however, when the letter begins with Word we have the Page setup for the printer to print the first page on letterhead (tray 1) and all pages after to plain paper (tray 2). When the word document converts to pdf, it is printing everything from tray 1 which is letterhead.
Is there any way to convert a document to pdf and keep the page settings as well?
Thanks for any input!

Don't have an answer. However, you might consider creating the WORD document so that the letterhead is built in and you do not need the paper.

Headers not converting from Word to PDF

I just installed Acrobat Pro XI and when I convert a Word Document to PDF my Headers do not show on the PDF. Footers do show OK>

I just solved the problem by converting the word doucment "Compatibility Mode". All works well now.

Convert from Word to PDF

I have been trying to convert both word documents and excel documents to Adobe PDF's. I have the latest version of Adobe Acrobat Professional but I get an error message saying that " PDF Maker encountered an error while printing the PDF. Please Retry. " Of course I retry but it still says the same thing.
Any help would be greatly appreciated.
Thanks

If you have Office 2008 the PDFMaker is written using VBA. VBA is not in Office2008.
To make PDF's from Word2008, go to "Save As..." and select PDF. MS got tired of waiting 20 years for adobe to figure out how to interpret insert page and Insert Section breaks so Office2008 they make PDF directly.

Black Pages - Convert from Word to PDF

When I convert a Word document to a PDF, the pages on the PDF document are black. This only happens on select Word document that use a specific cover graphic. I've sent the same document to a co-worker and they were able to convert the document to PDF with no issues. I have verified my preferences with my co-worker and these are the same. I have the latest version of Adobe Reader (10). I was previously able to convert a Word document with the same graphic to PDF without any issues. Any ideas on how to fix this?

Adobe Reader can't convert from Word to PDF.

Bug? Accessibility Tags Converting from Word 2007

This seems like a minor issue, but it's one that could create a lot of frustration for a disabled person using a screenreader to read tabular data in a PDF.
As you know, Acrobat plays nicely with Office apps allowing users to create tagged (structured), accessible PDF documents from MS Office files. I just created a simple docx file with a table (attached), and when I converted it to PDF, I noticed a difference in the tags it creates compared to conversion from Word XP. As you see in the Word file, the table is very basic, except that one of its column headers is split into two cells. This is actually a very common technique for presenting table data. In order to automatically tag the header rows as table header cells <TH> in the PDF, I set the first two rows to "Repeat Header Rows."
Converting from Word 2007 with the "Save as Adobe PDF," or any other method that uses the Acrobat plugin, creates a tag tree that is missing a <TH> tag. I found the problem when I was testing a file with JAWS screenreading software. Using the JAWS "current cell" command (Ctrl-Alt-Numpad 5) to announce the column headers. It reads the wrong header for the current cell due to the missing <TH>. So, in my example file, it announces $2 and $5 as 2010 amounts rather than 2009. That could be pretty confusing to a screen reading user, to say the least.
I then compared the result to the new Word 2007 "Save as PDF or XPS" feature. That feature tagged the file properly and the header columns match up.
Compare the attached "save-as-adobe-pdf.gif" to"save-as-pdf-xps.gif". Note the empty (but necessary) <TH> tag in the latter image.
Just as a sanity check I had a coworker with Word XP convert the file. Those tags were correct too. So, this must be a problem between Acrobat and Word 2007.
Anyone have other observations on this? I'm going to be leading some accessibility training and right now, it looks like using the Word 2007 conversion feature is the way to go.
I'm using Acrobat 9 Pro.
Thanks,
Joe

Hi Joe,
I sense your frustration. For any organization that has to or wants to engage in providing accessible online information
a serious logistics support issue raises its head. To do PDF, HTML, whatever the proper way (and it can be done)
requires more resources (training, knowledge, hardware, software, changes to work flows, perhaps some more staff).
The is no "work smarter with less & pump out more" in this venue.
Yes, it is helpful (and necessary) to "be one" with the S508 "paragraphs" - WCAG 1.0 - WCAG 20.
However, once anyone begins to provide PDFs that must be "accessible" the first, single most important reference is ISO 32000.
The Adobe PDF References that preceded PDF becoming an ISO Standard are useful; but, ISO 32000 is the standard.
In this documentation there is full discussion of what *must* be done to provide an accessible PDF.
Without a firm understanding of this content, other information tends to bring about a defused opacity of focus which can
contribute to major conceptual errors vis-a-vis accessible PDF.
Leonard Rosenthol's AUC blog entry provides a link to the ISO permitted Adobe version (free) of ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Additional, useful information is found in these two documents:
(1) - PDF Accessibility API Reference (from the Acrobat SDK)
https://acrobat.com/#d=J7bWW4LvNoznh8fHCsfZDg
(2) - Reading PDF Files Through MSAA
https://acrobat.com/#d=uIOvkVTP74kag3bXFJLIeg
About JAWS - Yes, much used. However, not the exlusively used AT application.
If I use Windows Eyes, NVDA, a braille reader, or something else then what?
JAWS *does not* define "it is accessible"...
re: (1)
"Game away and if it ...."
   Consider "Stop before right on red".
   "Compliance" is Stop on Red - Turn Right
   "Intent" (aka usability) is Stop on Red - Look Good for on coming traffic that has the right of way - Yield - when clear, turn right.
But, at least we are not talking about "left on red" 8^)
re: (2)
Just an observation. A defective product that claims to be "whole" can get entities (individuals/businesses) into a sticky wicket.
Putting a high volume of defective products on one's selves only increases the probability that one gets 'busted'.
Quantity replacing Quality just is not a success precursor.
Case in point - Target and the national class action legal action that was taken against it with regards to "accessibility" of online information/services.
Resolved now - see NFB's web site.
re: (3)
Ah, but what would Judge Judy or Judge Marily say?
Efficiency does not preclude providing a "whole" product.
I doubt that there will ever be a seamless "one-click" between products of any of the dominant software houses.
They are intense competitors. That this is the case does not abrogate others from providing a "whole" product, no?
So, if the organization wants the "we do accessible PDF" label then it pays the freight - Adobe Pro, training, appropriate work flows, etc
that permit delivery of PDFs that meet the standards for what a well formed tagged output PDF is (accessible is a sub-set of this).
For PDF there is no other way.
If this cannot be done then there is always HTML as an acceptable method (to some it is the preferred and only "true" way).
However, HTML, done "right" for accessiblilty is just as demanding in its own way.
With each AT version / dot version release, JAWS - Windows Eyes - NVDA & others hone in closer on utilizing PDF ISO Standard 32000.
That means if you deploy "accessible" PDF you need to provide PDF that live to the ISO standard.
Keep in mind that S508's paragraphs began when, effectively, HTML was "it". In software terms that was geologic eons ago.
For contemporary AT to effectively parse PDF, the PDF must be a well formed Tagged PDF having a format/layout that reflects a logical hierarchy.
Creation of all this must start in the authoring environment with the content author.
The post-process PDF output then assures that the PDF elements (tags) are the correct type, have the requisite attributes, etc.
Without this, AT will not be able to provide the end-user effect utilization of the PDF.
So, for AT to properly 'work' the PDF, <TH> elements *must* have the Scope attribute's value defined, Row and Column Span values defined, etc.
Scope, Row Span, Column Span, Table IDs and Headings must be added as part of the post-processing of a PDF using Acrobat Professional.
An alternative is the Netcentric CommonLook plug-in for Acrobat Professional. What it does, Acrobat Pro can do; however, the CommonLook
provides a robust user interface. Downside: at some $1k per seat it is not 'cheap' and it has a *steep* learning curve (Sitka Pass?).
Two table related resources are at this AUC thread (in post 3 and 4). They may be of some usefulness.
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=23178
When the "smelly stuff" gets feed into the maw of the fan it's prudent to not be directly down stream, eh.
Consider Target and the situation they put themselves in.
Consider submittal of accessible PDF to fedgov or stategov agencies.
They won't be in front of the fan if usability of the PDFs becomes an issue.
Rather, it will be those submitting. After all the agency did say "accessible".
Better to slow down and do it right or ramp up resource loading to support "schedule" than to stake oneself out as someones "feed" tomorrow, no?
In the final analysis, for PDF, HTML, or any 'format', Accessibility is the Usability + Compliance.
Does it take improvements in professional development/training, adequate hardware/software, *time*?
Yes. But, it all comes down to "where the rubber hits the road" - what tires are you on?
It can be done. I do it one small step at a time every day. Often, that's what it takes.
Deliverables are provided; but, with no mis-labeling and the incremental progress is identified, celebrated and the whole thing continues until
the "road" is completed properly.
Don't want wash outs, bridge collapse or what not tomorrow <g>.
(But then I'm a fan of "Holmes on Homes" which may go a long way towards understanding my point of view when it comes to accessible PDF.)
re: function(){Return ....
Good question.
My guess - either from the cut & paste I initially performed from the application I'd been using to assemble write up and screenshots or something associated with the Adobe Forum application.
It can't be that I'm 'special'; if that was the case one of my occassional lotto quick picks would have been a big $ winner long ago <G>.
fwiw -
You'll find a number of "Accessible PDF" related resources in the threads at the AUC Accessibility Forum.
http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=18
Two Accessible PDF related on demand eSeminars are also available.
Look for Duff Johnson's and Charlie Pike's (on page 2) eSeminars.
http://www.acrobatusers.com/learning_center/eseminars_on_demand
Be well...

PDF Maker cannot append

I hope that someone can help solve a current problem.
I have a user computer running Acrobat X pro and Outlook 2010 on the local machine. The user can convert email messages without error. However when the user attempts to append to an existing PDF thread the following error is received.
" Adobe PDF maker cannot create PDF file. Make sure the file is not already open in Adobe Reader. Click Retry to try again or click Save As to choose another name for this file"
I want to note that the PDF is not open when message is received, and sometimes the "Try Again" function works. The user can print, scan, move and edit PDF's just fine. This issue is isolated to the PDF appending function in Outlook.
Please Help!!!!

Thanks for the reply, I have completed all of the updates. Acrobat X pro does have the ability to both convert and append emails from Outlook. Whats more frustrating is that only this particular user is having the problem. No one else in the office.

PDF maker, Acrobat 9.0, Excel 2007 - wrong page sizes

When I use PDF maker, or "Create PDF", with my entire excel workbook, the sheet sizes come out randomly, though they are set as 8.5X11.
I notice there have been many reported problems. Are there any current solutions?
Thanks.

Thanks for that, I have checked thwe Word Document and the 'lines' are actually Cells so it would appear that the creator has copied
in these from a spreadsheet, into a Word document and then created the PDF.
The resolution is set to 300DPI in the PDF and the lines appear when unticking the Line Weights, however, this change isn't saved, if you can advise me on how to save the document with the line weights option unticked then that would be brilliant!
Thanks for your time helping me with this!
P

Converting on Word doc to PDF makes all docs PDFs

Similar Messages

Maybe you are looking for