Conversion from Word 2007 to PDF/X

Is there a monthly subscription service to Acrobat XI PRO so that I could convert a Word document with
text, graphs, and photos into PDF/X-1a or PDF/X-3? None of the subscription services that I saw expressly
state the type of conversion except to say its to PDF. Why is this so hard for sales and Customer Service
to figure this out?

You can subscribe to Acrobat XI Pro via Creative Cloud, or as a standalone application.
http://www.adobe.com/products/creativecloud.html
http://www.adobe.com/products/acrobatpro/buying-guide.html

Similar Messages

How do you keep embedded documents during conversion from Word 2007 to PDF?

Windows 7, with all available patches.
Word 2007, with all available patches.
Acrobat reader 9.3.2
I have additional documents, spreadsheets etc embedded into a Microsoft Office Word document. When this document is converted to the PDF (using the Word PDF add-in interface) the embedded objects can no longer be opened and only appear as images.
Is there a way to retain the embedded document during the conversion so that they can be opened from within the resulting PDF?
Thanks in advance!

Thanks very much for your repsonse, it's much appreciated
I don't have Acrobat X installed at this time so am not able to create or edit PDFs (other than from Word). I understand that creating a PDF from Word may not be an Acobat issue per se, but thought that someone on this forum may have experienced a similar problem, hence thought I'd try my luck here
I will do as you suggest and try an MS forum
Thanks again

I have had a trial version of Acrobat X1 Pro - I have decided not to buy at this stage - for some time it has been conflicting with opening PDF docs after saving as from word 2007 - I uninstalled Pro X1 and now when I save as from word 2007 to PDF it will

Can anyone help with this - do I have to uninstall Reader and then reinstall?

I have had a trial version of Acrobat X1 Pro - I have decided not to buy at this stage - for some time it has been conflicting with opening PDF docs after "saving as" from word 2007 - I uninstalled Pro X1 and now when I "save as" PDF from word 2007 to PDF it will save the document as a PDF but will not open the document to display after publishing - I have to got to where the file has been saved to view the new PDF document - this is really annoying - do I have to delete adobe reader and reinstall it - adobe needs to look at this conflict with acrobat pro as I have even gone it to properties and tried to have adobe reader as the default PDF program - the main issue is that I cannot view the PDF after publishing it from word 2007

How to make images searchable (OCR) when printing from Word 2007 to PDF with Acrobat 10

Good Day, I have checked several forums and the help file, but I can't seem to get a straight answer on this issue.
Our office creates many documents in Microsoft Word 2007 that contain both typed text AND images. For example, I have a document with a summary section and then a .jpg of an event from Facebook. We usually Print the document using Adobe PDF and the resulting PDF is searchable with the Find tool. The problem is that the images contain text and we want that to be searchable as well. I found posts saying to take the PDF and Print it again as an image and then run the Recognize Text tool. I have tried this and it does indeed work, although the resulting PDF is grainy looking (even at 600 dpi).
What I would like to know is if there is a way to get the images to be searchable during the conversion from Word to PDF. I could educate my co-workers on how to do this and save the trouble of having to touch each document more than once. Also, I do not like the graininess of the image nor the extra steps involved to convert each document. It will require a lot more hands on maintenance than I have time for.
Any assistance or clues you can provide on this topic would be appreciated. Thank you in advance, Paula C.

Thanks so much for your reply.
Paula F. Cutrone
Lead Crime Analyst
Onondaga Crime Analysis Center
511 S. State Street, Room 205
Syracuse, NY 13202
tel (315) 442-5645 x5062
fax (315) 442-5646
***CONFIDENTIALITY NOTICE***
Information contained in this e-mail is confidential and may be privileged and exempt from disclosure. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution, or copying is strictly prohibited. All information contained within should be considered law enforcement sensitive unless otherwise noted. If the reader has received this in error, please immediately destroy all copies and attachments and notify this office by replying to this e-mail or by calling (315) 442-5645.

Converting from Word 2007 to PDF (Acrobat 8.0) footers formatting problems

As the title describes, when I convert to pdf the text in my footers is changed. In Word, the footer simply has a link back to the bookmarks. The text is as so:
Click here go to back to the Table of Contents (with the Table of Contents text the actual link)
When I go ahead and convert to PDF, the font color is changed and only a couple words are underlined. In addition the last four words get placed three lines below the other words.
Any ideas on fixing this? I have not yet patched due to not have admin priv, but am working with our IT guy to update.

Be sure that WORD gets patched too. Often these problems turn out to be OFFICE issues. You might try a sample print to paper to see the issue. Also, AA is at 8.1.6.
There have been several problems folks have had with WORD 2007. The updates help some, but it is almost as though MS put some hooks in WORD 2007 to cross up Acrobat in some cases. I have run PPT documents with earlier versions of WORD and Acrobat with no problem. WORD 2007 would produce a totally different result that was not expected. There are even differences in graphics that you put in a DOC file versus a DOCX file. The latter seems to be doing some strange things to graphics. I would tell you more, but I really try to stay away from WORD unless I need it for compatibility with others.

Adobe does not recognize footers in Microsoft Word 2007 to PDF

I have copied and pasted the details, below, from a previous message I have sent out to an assistive technology listserv.
I am encountering this problem with various builds and versions of Adobe Acrobat:
Acrobat X on a Windows Vista 64-bit build (note that this is the best Acrobat I can install on Windows Vista, Adobe Reader XI is not even supported)
Acrobat X on a Windows XP build, sorry, do not know the bit count (it is my work computer so I can't upgrade anything)
Acrobat 9 on a Windows 7 64-bit build.
I have also encountered and checked into whether or not the PDF reads (and does what I want it to) in JAWS 14, latest update (Feb 2013). We encounter the same problem with JAWS and this morning found out that there is a conversion error between Word and Adobe. (See this post, where the ---- are).
Summary, I have spoken with JAWS, put out a support ticket with NVDA via e-mail, spoken with Microsoft, and tried to communicate with Adobe about this issue for help and Adobe is refusing to help. The other places tried everything they knew but they could not get it to work. I even tried to strip all the page numbers from Word and number using Adobe's page numbering feature, but that was not successful either because I cannot use Roman numerals.
I would appreciate any feedback the Adobe Forums can give me; please note that I cannot post a sample document at this time as the only document I have is a private work document (cannot share those by policy, so I will have to make up a fake document if I get the time and energy).
Thank you very much for your time and expertise. The pertient info is above and below in "Original Message" and "Activities section" - the other information is there if you'd like to look. And to provide feedback to Adobe about things I think they could improve, since they will not let me email them directly.
----Original Message----
My question concerns the reading of Footers / Headers in Microsoft Word 2007 and Adobe Acrobat (headers/footers designed in Microsoft Word 2007 and then converted to PDF with "Bookmark" checked in Adobe Acrobat conversion settings).
The document is a word document containing 50+ pages. There are 12 pages of "front matter" that are marked with Roman numerals. Subsequently, the body text of the document has an Arabic number (1, 2, 3, 4, etc.) in the bottom right corner. Footers are used properly in the document. All Table of Contents links, which do link to both headings in the "front matter" and to headings in the body text, are picked up properly. Literately, the only thing not reading on the document are page numbers (the Word Status bar is reading its page numbers, but the page numbers in the footer are not reading).
I then need to convert the document to Adobe Acrobat PDF. Granted, I have a full copy of Adobe Acrobat X available to me, and my various assistive technologies have always functioned better when opened directly in Acrobat (rather than Adobe Reader). So, I set the accessibility options (from Word) properly, asking it to bookmark Headers and Footers as appropriate, thinking that this will pick up the page numbers and make them read as the bottom right corner of my PDF.
All links work in Adobe to navigate by section/heading. All figures are alt tagged. Everything is perfect - but the one thing that NVDA won't read are the page numbers. Visually, the page numbers are there on the document, but NVDA won't pick them up. Additionally, I also changed the appropriate page numbers in Adobe (Page Thumbnail Pane, on the Navigation Pane I believe it is called) - to reflect the section where it is Roman numerals and Arabic numerals. This did not help, and for what it is worth, I cannot get NVDA to voice when I am in this pane, so I don't seem to have a chance of getting the page number info from there.
NVDA reads the document just fine except for the above-mentioned snare. However, when it reads, it will go to the next page, and say, "Page 2 of 54, (page text), Page 3 of 54 (page text)," etc. when I will need it to say Page ii of 54 (page text), Page iii of 54 (page text)," and so on, changing to "Page 1" when the Arabic numbers are used.
I know that the Page Label issue is part of Adobe's issue, with them not releasing the PageLabel aspect. (I have looked through some NVDA tickets). I do not know how to put a "changeset" into my copy of NVDA though, or even if it would help (I have no computer scripting skill). The easy answer would be to upgrade to Adobe Reader XI and see if that helps, but I don't have the ability to put it on every computer I use, and *I need this file to read consistently across multiple versions of Adobe* (including Adobe Reader/Acrobat 9, X, and XI). (This file is also going out to people who may not have the latest version of Adobe, but are also running some copy of NVDA, either a portable or a full install).
Is there any way to pick up the Footers with page numbers voicing in NVDA, and/or have it read the user-editable page number box that is on Adobe's Toolbar (next to the 1 of 54 parentheses). This user-editable box, to jump to page numbers, reflects the Roman numerals I have loaded into the pages of Adobe. When I press Ctrl+Shift+N in Adobe, I can also go to the appropriate page (if I type in iii, it will take me to iii, if I type in 34, it will take me to the Arabic number 34 -- NOT the 34 of 54, which would land me on a different page. And I want to land on the page that has the Arabic 34, so that's functioning fine.
I just need the page numbers in the footer to voice, "Page iii," or "Page iv," or "Page 29," etc. If I could get NVDA to do that, I could say to viewers of this document, "If you are using NVDA, remember to Ctrl+Shift+N to get the GoTo Box, then type in the page number you want if you cannot follow a link or a bookmark." This document is *very* accessible in my opinion with lots of ways to navigate...the only aspect of navigation that isn't being picked up are those footer page numbers!
I do have my Document Formatting settings on the NVDA menu set to "Report Headers," but that does not seem to help in either Microsoft Word 2007 or Adobe Acrobat. I have even switched the page numbers from the footer to the header to see if that would help and it didn't.
----Activities I have done today----
I spent over an hour on the phone today with Freedom Scientific (makers of JAWS) trying to troubleshoot this. We discovered that Footers will not read very well in JAWS and Microsoft Word 2007 (only solution is to stop reading document text and read Virtual Viewer text briefly, then go back out to document text, then back into Virtual Viewer which is NOT an acceptable or accessible solution whatsoever -- too much work for someone trying to read the document) -- and then we also discovered that:
Upon conversion from Word 2007 to .txt file (.docx to .txt), there are no alt tags for the figures in the document, or page numbers.
Upon conversion from Word 2007 to Adobe Acrobat X then to .txt file, every insert of a page number and footer is replaced with the same alt numberpad numerical code: the one that generates female. ♀No wonder JAWS and NVDA are skipping this, neither understand how to communicate it.
On the advice of JAWS Technical Support I contacted Microsoft Accessibility Technical Support and spent an hour on the phone with them. They say that unless Adobe can find a solution, it appears that it is impossible for Microsoft products to read the footer if JAWS was unsuccessful doing what I wanted it to do. The document/footer in question includes about 12 pages of front matter (numbered in Roman numerals) and 44 pages of body text (numbered in Arabic numerals).
I kindly explained to the Microsoft Support Agent that I found this issue hard to believe, although I understood. Sighted folks have the ability to make their documents look quite professional and that is the caliber and quality of documents anticipated from everyone, especially college students graduating from school, or job applicants. That a coding issue prevents the footer from being read properly, except in Edit view, is disappointing. The representative was with me 100% of the way. She completely understood where I came from. And yes, when I am designing the document myself, I know what I put there (or I pretty much do, anyway). But if I recieve a document, it is much harder to tell what is really there or not, or how the page numbers really lay. And this is confusing as heck, believe me.
I then called Adobe Technical Support, after having a brief online chat with them. Granted, I had to leave the chat in the middle because I got interuptted by something that was high-priority, but the woman chatting from Adobe says that chat is only for installation issues, and I will have to pay to open a support ticket. Excuse me? I have paid a hefty sum of money for Adobe Acrobat 9 and Adobe Acrobat X (work paid for the other Acrobat X copy). I deserve this problem to be troubleshooted for free. There was even a statement on the Adobe Acrobat X website that said Acrobat X users didn't have to pay for support, but Reader users did.
----Slight bit of rant and constructive criticism----
In speaking with Adobe Technical Support, I had to wait on hold for 30 minutes before my call was answered, and then I had to consent to being on hold countless times and had to answer, "Yes, I am converting from Word 2007 to PDF using Adobe Acrobat X" at least 6 times. The representative would put me on hold, then ask me the question, then put me on hold again, repeated 6 times over 45 minutes. At the end of 45 minutes (1 hour and 20 minutes of wasted time by now, that I must justify to my employer) - I told the representative I wanted to speak with his supervisor immediately, I did not care if he was trying to fill out a support ticket (and putting me on hold at least 4 more times in 10 minutes while he claimed he was filling out the support ticket) - and finally he put me on hold again and gave me to a very helpful supervisor. Within 6 minutes of speaking with the supervisor the supervisor had my support ticket filled out and I should recieve a call from Adobe within the next 30 minutes if his estimation was right (he estimated two hours, but it's been an hour and a half).
I have yet to know what can be done about my document. Freedom Scientific Technical Support is closed now for the day and I need to work tomorrow and Friday away from the phone. As I stated to Microsoft Accessibility Support, I truly feel that Adobe should read the page footers, every document says that Adobe should be able to read the page footers, and I feel slighted that as a person who uses assistive technology, there is some glitch that isn't making this happen. I am not blaming a specific place per se, except I am a little frustrated with Adobe especially since they have not gotten back to me, and I am frustrated with their customer service. JAWS customer service and Microsoft customer service were both exemparly, and I cannot say enough good things about them. My wasted time with Adobe however, that was disrespect in my opinion. And I certainly will not pay to open a support ticket, and my workplace has a site license. They've paid enough already.
If you've read this far, thank you. I look forward to replies, or at least understanding. And if anyone has ideas, I'd appreciate it very much (yes, I have tried taking the page numbers off and using Adobe's page number feature, but that would not allow Roman numerals. Only Arabic.).

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

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.

Acrobat Pro 9 - Conversion Error from Word 2007

I do not want to hijack the thread or question raised by another poster a short time ago but I cannot figure out how to correct the below.
Office 2007 fully updated
Vista 32-bit
Acrobat Pro 9.3.4
I have to provide data for someone else to assemble and publish and have been attempting to convert some Word documents nearly full of tables to press quality .pdf. Whenever I try the conversion, Acrobat Pro seems to re-center the tables both horizontally and vertically forcing the misalignment of the rows of data although any repeating headers remain properly placed. I can even see the table shift downward slightly when using the Acrobat conversion macro within Word. It may be adjusting the margins instead of re-centering.
I have tried using the macro within Word 2007, Create PDF within Acrobat Pro and Print to PDF as well as tweaking some of the settings such as lowering resolution and turned off unused settings such as enable fast web view, etc. The glitch also occurs with High Quality Print. Standard used to work but after the update to 9.3.4 that conversion shows the same problem. I even tried saving in Word 97-2003 format with the same results.
The documents in question do have custom page sizes and margins but do not use any abnormal fonts. I have tried changing the margins but the conversion to .pdf still changes the information and/or magins as described above. Row height seems to be correctly maintained.
I realize that a knowledgeable user can export the .pdf back into Word or other program but am trying to make it more difficult for someone to edit information which has always had extremely negative consequences in terms of data organization, layout and even integrity.
There has to be something really silly that I am overlooking.
Thank You

Thanks Bill.
Sorry for the delay, Verizon dumped its DSL +service to Frontier so we had one of the bi-weekly extended outages.
No changes occurred when I changed the default printer to Adobe PDF. All of my printers are new enough so that they can handle the current margins so I do not think that they is a problem there but changing the default as suggested by you and Michael eliminates that as the source.
I had previously been able to convert using the built-in converter in Word but was unsure whether or not the result would be press quality and was unable to find this information in my searches. I retested this and conversion using Word’s built-in converter works without a problem.
The conversion using Combine Miles > Merge Into A Single PDF also works without a problem with the highest quality setting. It took several hours to run but I guess or assume that it was because of the number of tags as this is a quick setting and therefore I could not disable the tagging which is not needed in this case.
I was also able to convert the same file which had been saved from Word 2007 into the 1997-2003 format as described above but the same problem came up when using the Acrobat macro and Create PDF from File. I had even created a modified press quality settings to modify settings like disabling autorotate, Object Level Compression, changed the binding option, lowered resolution, bumping the format up to PDF 1.7, etc., but all produce the same result. I have tried changing the document margins in case the conversion process rounded these but all produce the same artifact/problem except when I use Combine Files or the converter built into Word.

Printing a PDF from Word 2007

Good Day, I have checked several forums and the help file, but I can't seem to get a straight answer on this issue.
Our office creates many documents in Microsoft Word 2007 that contain both typed text AND images. For example, I have a document with a summary section and then a .jpg of an event from Facebook. We usually Print the document using Adobe PDF and the resulting PDF is searchable with the Find tool. The problem is that the images contain text and we want that to be searchable as well. I found posts saying to take the PDF and Print it again as an image and then run the Recognize Text tool. I have tried this and it does indeed work, although the resulting PDF is grainy looking (even at 600 dpi).
What I would like to know is if there is a way to get the images to be searchable during the conversion from Word to PDF. I could educate my co-workers on how to do this and save the trouble of having to touch each document more than once. Also, I do not like the graininess of the image nor the extra steps involved to convert each document. It will require a lot more hands on maintenance than I have time for. We are on Windows 7.
Any assistance or clues you can provide on this topic would be appreciated. Thank you in advance, Paula C.

Any work to make the images searchable should be done BEFORE putting them in Word. It is far too late once the PDF is made because you will destroy the good work that Word did in preparing the PDF in the first place.
Sadly it's far from clear how you'd do that. About the only format you could use to hold OCRd images would be EPS, and I've never heard of "OCR to EPS" software.

Acrobat Pro 9.1 no longer creates PDFs from Word 2007

I upgraded from Acrobat 7 to 9 specifically to gain more control over settings when making PDFs from Word 2007. This worked as I had hoped until the 9.1 vulnerability upgrade was installed. Now it will no longer create PDFs from Word 2007 documents at all.
From within Word 2007, when I click on "Create PDF" (whether in the Office menu or Acrobat toolbar) it asks for a file name, but after I click "Save" does nothing. This is true even for the simplest possible document, using the "Default" settings for PDF "Preferences."
If I right click the file name of the document in Windows Explorer, with Word 2007 closed, and click on "Convert to Adobe PDF" in the menu, it starts and the staus box comes up, but after a few seconds quits and displays "An unexpected error occurred. PDFMaker was unable produce the Adobe PDF."
I can still "Save As" PDF in Word 2007, but this gives me little control over the format.
Is there any way that I can get Acobat 9.1 to do what I bought it for, and what Adobe advertises it will do?

Try printing to the Adobe PDF printer, the more fundamental process (PDF Maker is a preprocessor for the printer). If that does not work, then try with print-to-file selected. Open the file in Distiller and see if the PDF is created. If the latter happens, then check for AcroTray running in the background. It is required to automate the process and is needed by PDF Maker.

The numbering format keeps changing when making PDF's from Word 2007 ? Using Acrobat 9 Pro Extended

The numbering in (Contents) format keeps changing when making PDF's from Word 2007 ? Using Acrobat 9 Pro Extended.

The issue is that I have made up a contract in Word.
The second page has a list of all contents of the contract.
gghhjhhbhbhhbhbjbhj....1
bv v vghvjvjnnnnnnnnn....2
When we convert to PDF some of the numbers change. Example 20 becomes 201.
Your help is appreciated.
Cheers Ocean designs.

Fast Web View breaking links/bookmarks in PDFs from Word 2007

I'm running Acrobat Pro 8.1.2 on WinXP, and I recently noticed an issue with PDFs that I'm creating from Word 2007. If I turn on the setting "Save As optimizes for Fast Web View," any links or bookmarks in the file break when I do a Save As. If I turn the setting back off, Save As doesn't break them.
I had had problems creating the PDFs using the PDFMaker plug-in for Word, so I used the Save As PDF or XPS feature from Microsoft instead.
PDFs created using FrameMaker are not giving me problems.
I don't know whether this is related, but the Settings button on the Save As dialog box is no longer active. I'm sure I was able to click it before, but I can't now. And that goes for PDFs from Word or FrameMaker.
Anyone have any clues?
===========================================
Rick Henkel
http://rickhenkel.googlepages.com/index.htm

This is related to a bug in the direct PDF output from Word 2007. I was told that Microsoft has fixed this bug in the final SP2 release (so when the service pack becomes available, this problem will not be present).
Until then, the workaround is indeed to turn off the "Save As optimizes for Fast Web View" preference in Acrobat (Edit > Preferences > Documents, under Save Settings).
Shlomo Perets
MicroType * http://www.microtype.com
FrameMaker/Acrobat training & consulting * FM-to-Acrobat TimeSavers
"Improve Your FrameMaker Skills" live web-based training sessions

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

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

Cannot convert {PRINT "[/DEST/destination /DEST pdfmark"\*MERGEFORMAT} from Word 2007 to bookmark

Hi,
Please help, We used to have word 2003 and we have below formula for bookmark so that when we convert it, there's bookmark in pdf. However, when we migrated to Word 2007, it stops working. When I am doing merge files into a single pdf, what I get for bookmark is the document title. Is there a compatibility issue? Or what is really the problem? Can you help me? Btw, I'm using Adobe Acrobat 9 Pro. Thank you in advance.
"\*MERGEFORMAT}
{PRINT "[/DEST/destination /DEST pdfmark

A: Cannot convert {PRINT "[/DEST/destination /DEST pdfmark"\*MERGEFORMAT} from Word 2007 to bookmark

Are you using the Adobe PDF printer to produce a .ps or .prn file first and then using Distiller to produce the PDF. I have found that Distiller recognizes and renders the /DEST pdfmark operators it encounters in Word 2010 .docx file. It has also been my experience that when I build a book PDF from multiple PDFs, I must insert the pages from each file. In that way, the named destinations are given the correct page in the book PDF file. I learned that using automatic merge prevented links to named destinations from working. I think the reason is that if you use the automatic merge, the named destinations retain the page of the original PDF file, and therefore, links to them do not work.
Hope that helps

Conversion from Word 2007 to PDF/X

Similar Messages

Maybe you are looking for