Tiny U's when converting from Word 2007 to Acrobat 9

When converting a MS Word document that has an underlined word in it, the PDF has very small capital U's before and after the underlining. This is when going from Word 2007 on Vista to Acrobat 9 (CS4). Anyone else experience this?

Here's how I can duplicate this.
1 - Open a new document or an existing document
2 - Underline any word using either the Ctrl-U keystroke or by use of the ribbon bar option (Word 2007). By the way, this occurs only in Word, works well in PowerPoint.
3 - Save document either as .docx or .doc
4 - Convert to PDF by selecting the Acrobat ribbon and clicking on Create PDF.
5 - View PDF, zoom to approximately 800% to see the very small capital U's
It should also be noted that if the "Enable Accessibility and Reflow with tagged Adobe PDF" is unchecked, this issue goes away. However, this is absolutely not a viable option because all of my documents must be accessible for persons with disabilities. Furthermore, in theory I should/could be able to create the PDF from Word without the tags and use Acrobat's "Add tags to document" feature, but Acrobat doesn't handle complex documents well, or as well as creating the tags directly from Word.
To see an example see this:
www.humtech.com/upload/test.doc
www.humtech.com/upload/test.pdf

Similar Messages

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.

Figures order gets messed up when converting from Word 2010 to Acrobat PDF

Hi,
Im wondering if someone can help me. I have a 10 page document in Word 2010 with many figures (rectangles and circles overlapping each other). The order of these figures are essential. I have triplechecked the order in Word with the correct figure marked as on top. But when I convert (by printing) to PDF the order of the figures gets messed up making a mess in the document.
I have Acrobat 9.
Could someone please help me with this?
Many thanks!

I solved this by taking the document with me to a computer with Word 2007 installed instead of 2010. I guess the problem lays in the fact as some of you mentioned that Acrobat 9 doesnt support Word 2010. Now I know why! This is a bummer though, upgrading to Acrobat X isnt exactly cheap and I dont want to downgrade Word as I really like some of the new features in it (as the screenclip option).
Thanks for your answers!

Hyperlinks lost when converting from Word 03 using Acrobat PDFMaker 10.0

This hasn't been an issue before (using the same version of both softwares). I checked in Conversion Settings, and both Add Links and Create Bookmarks are checked. Help! Thanks!

Try updating to 10.1.3.

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

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

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.

Acrobat Pro 9.2 crops text when converting from Word 2003

When converting a Word 2003 file to PDF, using either PDF Maker or directly from Pro 9, the converted file crops a few lines of text at the top of some pages. Converting the same file by just printing to PDF is a work around, but this method does not create bookmarks, so is not preferable.
I create an updated version of a particular file monthly, using the old file as a basis. The file will always have tracked changes in Word which are all accepted before converting the file, and the file always has a watermark, which is removed in Word and the file saved before converting to PDF.
Now here's the weird thing, if I remove the watermark in Word, save the file and convert to PDF, the cropping occurs. But if I leave the watermark in the saved file, convert to PDF and remove the watermark in Acrobat, no cropping occurs! This is an OK work around too but I'd rather not have to do the workaround at all.
I've tried all the variations and settings I can think of, but I still end up working around the problem every month.
Any ideas?

They won't show up unless
you have click on each text box
Go Format > Shape
click on lines
chose desired line color for the borders.
once the Borders a colored they will show up in the created PDFs.

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.

Images Sent to Back move to front when converting from Word 2010 to Adobe Acrobat XI

Images that have been set "Send to Back" and wrapping is set to "Behind Text" will move to front, overlapping text when file is converted to Adobe Acrobat XI. I'm on Windows 7. Anyone having this problem?

How you convert the document to PDF format? Export/Create a PDF, Save as PDF, print as PDF, or using Adobe Acrobat?
Please try to save the document as PDF format and then check the result in Adobe Reader.
If you are using Word 2010/2013, the save as PDF is a build-in function and you can find it from File > Save as
If you are using Word 2007, please firstly download and install the Microsoft Office Add-in - Microsoft Save as PDF or XPS .
http://www.microsoft.com/en-in/download/details.aspx?id=7
Thanks.
Tony Chen
TechNet Community Support

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.

Editing PDF When Converted from Word to PDF

I converted a word document to PDF. When I opened the file to edit and use the OCR Text Recognition it said could not edit because of renderable text.
I also have photos and website links in the document.
What can I do so I can edit the text?

Thanks for your quick responses.
Yes I do. I guess I need to re- edit in word. I just thought I could edit it in 9.0 Pro as well. I was getting some large spaces in between some paragraphs. In word the spaces do not look as large.
Also if you know if there is a way to make it so the links are workable. I plan to make the text protected from copy and paste, etc etc.This is going to be an informative Ebook and I want the users to be able to click on the links and continue to various websites.

Text quality bad when converting from word 2010 to pdf

Hi,
When i convert from .docx to -pdf the text quality gets bad, i dont get the problem when printing to pdf though.
Quality in Word:
Quality when converted to pdf:
Can't figure out whats wrong?

What version of Acrobat (and subversion)? Are the fonts embedded in your file?

Why are hyperlinks no longer working in PDF, when converted from Word?

I have Acrobat Professional 11 and have recently upgraded my PC with a new operating system (Windows 8). I can't remember how to find out what version of Word I now have, but it should be a fairly recent version, given its new. Since the upgrade, when converting Word documents to PDF using the "Create Form" function in Adobe Pro 11, only full hyperlinks (with the @ symbol) are working in PDF, not other hyperlinks that we've renamed. Under the old operating system, ALL hyperlinks used to transfer & work when converted ... am I missing a checkbox somewhere?? HELP please, I have loads of word documents to convert and it's very time-consuming to have to do weblinks manually!!

First off, Word should show you the version on a splash screen when you launch it.
Also, what happens to the links if you just open the document in Word and save it as a PDF?

Tiny U's when converting from Word 2007 to Acrobat 9

Similar Messages

Maybe you are looking for