Converting from Word to Adobe

I want to convert a Microsoft Office Word 2007 document to a pdf (Adobe 8 Reader). I don't see the option. ????

[email protected] wrote:
> get the primopdf printer here
or the
> pdfill printer from here
. primopdf printer
> works very nicely. i haven't tried the printer of pdfill but their
> crop feature works nicely so i'm assuming the printer works too.
No need at all for such substitutes as long as it's Office 2007 apps.
All one needs is the PDF/XPS add-in.
BTW: There are tons of freeware/shareware and low-budget instruments for
PDF creation and none can match Acrobat.
Major problem with almost all of them (and necessarily so if the work as
printer drivers):
*Links* in the source document are not converted. In this is a major
drawback if it comes to usability: URLs in a document are not active,
nor are bookmarks available (a most serious drawback for documents with
TOC, f.e.)
Rainald

Similar Messages

Hypertext links are not always preserved from Word to PDF, using Aperçu or Adobe, depending on OS 10 or Lion. Why? This generally works perfectly in Windows. Why are Apple and Adobe unable to correctly handle links when converting from Word to PDF?

Hypertext links are not always preserved from Word to PDF, using Aperçu or Adobe, depending on OS 10 or Lion. Why? This generally works perfectly in Windows. Why are Apple and Adobe unable to correctly handle links when converting from Word to PDF?
Depending on the system version, and Office Word version:
- a pure URL link starting with http or even www sometimes works in PDF, either produced by Aperçu or Adobe, sometimes does not work;
- other kind of links where the text under display is not a URL, never work!
I like everything with Apple computers and software, except PDF generation. Output files are usually bigger in size, and no better quality, than under Windows. Furthermore, it is weird that something as common as hyperlinks does not work correctly!
I related this question with Mac OS X Snow Leopard, but the problem is still there with Mac OS Lion.
This problem seems to have been around for years, without any proper solution from Apple and/or Adobe! To me, this is very embarrassing!

Greetings NoNameGiven,
If I understand the problem correctly (I’m not sure I do) you would prefer ‘iii’ to be read as “eye eye eye” rather than “three”? The alt text property is the only way that I know of to make this happen. Hope this helps.
a ‘C’ student

How to use .joboptions file while converting from Word to PDF

Hi,
I'm pretty new to Acrobat. I'm using Acrobat XI. I need to convert a word document to a PDF file which conforms to certain requirements described by a given .joboptions file. The .joboptions file can be opened by distiller, but as far as I know distiller is not invovled in the conversion (Word to PDF) process. So how can I make sure the converted PDF file meets the requirement described by the .joboptions file?

Distiller is used when converting from Word to PDF, if you do it via the Acrobat panel, not the Adobe PDF printer or Word's internal Export to PDF command. If you've loaded your joboptions file in Distiller (via Settings - Add Adobe PDF Settings), then you will see it in the drop-down of Conversion Settings when you click the Preferences button in the Acrobat panel in Word.
After you've selected your job options profile click the Create PDF button, and the file will be converted using the selected options.

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...

Convert from Word 2007 to Acrobat Pro 9; bookmark issue

When converting from Word 2007 to PDF using Acrobat Pro 9, enabling "Convert Word Headings to Bookmarks", not only are Headings converted to bookmarks, but bulleted text (styles), as well. I attached the subsequent PDF, but this forum does not permit the document attachment. I really only want to show the Headings. (It may be noteworthy to mention that when using this same set of styles in Word 2003 and Acrobat Pro7 the conversion was seamless.)
Does anyone know how to correct this? I have reviewed my Word styles and the issue does not appear to be on the document level. Am I missing some obscure setting?
I'd appreciate any help.
Thanks.
-PS

I had a similar situation occur when converting Word 2007 docs to Acrobat Pro 9 Extended via the PDFMaker (Acrobat add-on tab in Word 2007), and I want to share a workaround. In summary, I had extraneous bookmarks appear in the PDF (heading 3s, body text, XE Index tags, etc.) that I did not select to be in the PDF. I contacted Adobe's support and ended up talking for approx. 2.5 hrs to 2 different reps with no solution. They reproduced the issue on their end, but couldn't figure out how to fix this. I recently upgraded to Tech Comm Suite 2.5 from 1.0. The Word 2007 conversion to PDF via Acrobat Pro 8.x worked fine.
Scenario: I have 400-page user guides that I am required to publish as 'Press Quality' with navigable bookmarks to certain headings in the PDF. I have to generate the PDF via the Acrobat Add-On tab in Word, since I do not want to manually insert bookmarks in the PDF for 400 page documents (as you would when using the Adobe Print driver or 'Save As PDF' operation).
In the Adobe PDF Maker dialog, I have the following Application Settings selected in the General tab:
Create Bookmarks
Add Links
In the Bookmarks tab, I originally had only two Elements selected for bookmarks:
Heading 1 (a Word Heading already present) as the Level 1 Bookmark.
Table of Contents Bookmark (a Word Style I created) as the Level 2 Bookmark.
As a result, the Convert Word Headings to Bookmarks and Convert Styles to Bookmarks were both enabled in the Bookmarks tab.
The resulting PDF contained extraneous bookmarks that I did NOT select, such as Heading 2s, 3s, even body text - too much to clean up for 400-page documents! Additionally, and this was annoying too - I noticed that all bookmarks appeared as Level 1 Bookmarks, making the PDF Bookmarks really messy. I converted multiple Word 2007 documents with the same results.
How I resolved the issue:
In the Word 2007 document, open the Styles window, select all instances of the specific Word Heading (in my case, Heading 1). All instances of the selected Word Heading will be selected in the doc.
Click the New Style icon in the lower left part of the Styles window.
In the Create New Style from Formatting dialog, create a new style name (e.g., I created H1).
Just to be sure to NOT create the new style from an existing Word Heading, I selected (no style) in the Style Based On field.
Configure the remaining formatting items as necessary, and then click OK. All of the selected instances from the old Word Heading style are now changed to the new style created (in my case, H1).
Click the Preferences tab in the Acrobat add-on tab in Word 2007, and open the Bookmarks tab.
Remove the old Word Heading (in my case, it was Heading 1) so it no longer will be included as a Bookmark in the PDF.
Select the new Word Style that you created (in my case, H1) to be generated as the Level 2 bookmark. Note: My original Level 1 bookmark, "TOC Bookmark," is still selected. Now, only the Convert Word Styles to Bookmarks is enabled in the Bookmarks tab.
Generate the PDF once again via the PDFMaker, and no extraneous bookmarks appear in the PDF.
Note: I also noticed that when Index tags (XE tags) were present in an element selected to be a bookmark in the PDF (such as my new style, H1), they also appeared in the PDF Bookmarks pane. I just moved the XE tags down to the body text so they would no longer appear in the PDF.
Question for discussion: Maybe there is a bug in the PDFMaker when both Convert Word Headings to Bookmarks and Convert Styles to Bookmarks are selected? The extraneous bookmarks do not appear in my PDF when only Convert Word Styles is selected.

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.

How do I get PRO to not include codes when converting from Word?

When converting from word, I get all of the codes printed too.How do I get it to not show in Adobe? I'm on a deadline and right now not happy that I upgraded. Need my old adobe back!
Board of Directors Meeting{ PRINT \p para "[
/EMC pdfmark [ /StPop pdfmark" }
{ PRINT \p para "[ /Subtype /P /Title () /StPNE pdfmark" }{
PRINT \p para "[ /StBMC pdfmark" }{ PRINT \p para "[ /EMC pdfmark [ /StPop pdfmark" }
{ PRINT \p para "[ /Subtype /P /StPNE

Thanks Bill for your reply.
I am using Acrobat XI, just downloaded it and Word 2003. There are no punctuations on my form, I just hit return to go to the next lines.
I put in a little square check box and that is also causing issues. I checked to make sure the field codes are off on the original word doc.
I did try from the printer to save and adobe and I get the same codes. Other people that I work with are able to get my document to save correctly in acrobat with the same versions of word and XI.
It has to be some small setting on my computer.

Since 11-4-14 every convert from Word to PDF has failed online or desktop - when will this be sorted

Since 11-4-14 EVERY convert from Word to PDF either online or desktop has failed, when will this be fixed?

No replies on here so went online and tried various options including "repair reader installation" plus uninstall and reinstall etc, some posts suggested a repair from the Printers file (Vista) so installed AdobeCreatePDF desktop printer plus Xerox Phaser PS printer as advised. All without any obvious sucess ie still no word docs converted after hours of trying. Then unexpectedly a further test convert attempt succeeded; tested again on desktop plus online and now all works fine as it did before. Who knows why - possibly only Adobe know. Will leave this thread here just in case the fail reappears over next few days!

Editing files that have been converted from Word documents

Will I be able to save and edit the PDF files I convert from Word documents?

Hi,
Yes it is possible to edit the PDF files and save the changes. You need to use Adobe Acrobat for this.
Please download and test the 30 days Trial for Adobe Acrobat : http://www.adobe.com/cfusion/tdrc/index.cfm?product=acrobat_pro&loc=us
~Pranav

How did my pdf files get converted from 'open with Adobe Reader' to open with Adobe Acobat'? And if I have a ''free'' Acrobat account why does it not open? When I do click on the account it ask me to pay $89.99. I never wanted Acrobat. How can I get -

How did my stored files get converted from 'open with Adobe READER' to 'open with Adobe ACROBAT'? How can I get them re-set to open with 'Adobe Reader'?
Please reply to my e-mail: [email protected]

It sounds as if you downloaded Adobe Acrobat Pro. If you did, uninstall it. Then repair Adobe Reader.
The free Acrobat account has no connection to any of this.

Converting from WORD to pdf always fails the first time

OS is XP. Acrobat Pro 8.1.5. When I first convert from WORD, EXCEL, whatever the program appears to be working but no file is created. This happens always on the first time I convert to pdf for the day. Once I do it again, it works and continues to work throughout the day. I turn off my computer at night and again the next day when I come in it doesn't convert the first time but will work again. Is there something in Windows or Acrobat that I can fix to get this to work properly?

If you are using Word 2007 (you don't say) you might try the Microsoft plugin... this is instead of Acrobat
http://www.microsoft.com/downloads/details.aspx?FamilyId=4D951911-3E7E-4AE6-B059-A2E79ED87 041&displaylang=en
If you are using an earlier version of Word (or Word '07) make sure you have installed all Microsoft Office updates, so you'll know this is not a Microsoft bug

Abobe v8: Problems with converting from word 2003 to PDF

I use one of those free conversion tools, since i am a student. My problem is that i have a word document with a unique page margin. When i convert from word 2003 to pdf everything gets converted except the page margin which is much bigger then it's supposed to be. Do anyone know how i can fix that?, any help are appriciated.
Kindly Erik

You cannot fix anything in Reader. If you have a problem with the tool
used to create your pdf, please ask in their forum.
Mike

How can I keep the formatting when converting from Word to pages?

How can I keep the formatting when converting from Word to pages?

Use only formatting that is supported (in the same manner) in both applications. You'll need to find which that is through trial and error. Beyond those formatting options, you'll need to do some corrections, as Fruhulda suggests.
Regards,
Barry

Hi, I have adobe acrobat pro 9 (yes older version) with error to convert from word

on win7 64bit. but when I try to convert a word file to pdf. I get error PDF MAKER. When I print a test page from word to pdf printer it does correct. Word is 2007
When I go to my acrobat. And I press combine from word I get the error.
When I combine from other pdf it all works.
So it is the conversion from word to acrobat creating the error.
The exact error messag I get is next:

I don't believe that Acrobat 9 is compatible with the 64bit version of Windows 7, which might cause integration errors, like the one you're describing.
The solution is to upgrade to the latest version.

Techniques needed for Automated (OLE) PDF Creation from Word using Adobe 9

My client currently uses Adobe 5, PDF Writer, Word and OLE automation to generate PDF files. This is done on a server. A queue of Word documents are read. A watermark is added via a VB Macro. Then, also via a macro (below) a pdf file version of the Word doc is generated. The pdf file is generated as temp.pdf, which the program uniquely renames later.
Unfortunately, Adobe 5 and PDF Writer cannot handle Chinese characters and now needs to. Seems like the process above cannot be the same with Adobe 9. How should I approach this server driven, pdf file generation from Word docs with Adobe 9? This is a 24 x 7 ongoing, 100s of documents a day process. It isn’t clear to me that PDF Writer is still an option. With Adobe 9 installed on a client, it is possible to save a Chinese character Word document using the Adobe ‘Convert to PDF’ toolbar button
Sub WritePdfFile()
    Windows(1).Activate
    ActivePrinter = "Acrobat PDFWriter"
    Application.PrintOut FileName:="", Range:=wdPrintAllDocument, Item:= _
        wdPrintDocumentContent, Copies:=1, Pages:="", PageType:=wdPrintAllPages, _
        Collate:=True, Background:=True, PrintToFile:=False
End Sub

I think that type of question would go in
Scripting http://forums.adobe.com/community/acrobat/acrobat_scripting
or
SDK http://forums.adobe.com/community/acrobat/acrobat_sdk
Or, for Microsoft parts of the process, search at
http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US

Converting from Word to Adobe

Similar Messages

Maybe you are looking for