MS Word 2007 table lines have interesction tick marks

Hello,
MS Word 2007 SP2
Adobe Acrobat 9.0.0 Plus
A table created in Word, where row lines are shown but not column lines, shows on some lines tick-marks where row and colums would intersect. In AA version 7 this was not an issue, however, when converting from within Word this too was an issue.
The image below didn't turn out as clear here than the original, but you still can see the Word bit left and AA on the right with the tick-marks.
How can it be avoided?
Thank you
Stefan

I'm experiencing this myself. I found instructions to navigate to Edit > Preferences > Page Display. Then, uncheck 'Enhance Thin Lines'. This lightens the lines considerably; reducing the very dark, chunky lines. However, table lines are still not the same width/thickness regardless of the zoom level in Acrobat (50% - 800%). And there is no pattern to where thicker lines appear; header rows, odd rows, etc. A random mess. I'm 100% positive the lines are set properly in Word 2007. And interestingly, all tables lines display equal widths consistently in printed copy- when printing from the PDF. The issue seems to be Adobe's electronic page display and that the 'solution' I found does not work. I have the latest version of Acrobat Pro and a colleague has the latest version of the Reader without a writer license-- no conflict of versions or software suite.
I deliver documentation to customers electronically. My documents have many tables. My deliverables to look unprofessional and unpolished. My deadlines haven't been met due to research and this unresolved issue. Difficult to accept.
So frustrated! Please help!
Jennifer

Similar Messages

Problems with saving Word 2007 table as PDF

I have a table in MS Word 2007 with some merged cells. If I use the Save as ... PDF or XPS option in Word 2007 to save this document as a PDF, the resulting PDF has a table with a discontinuous table grid. The table lines around the cells are broken.
Is this a problem with the Word table or does the Save as PDF command not work well with tables.
Thanks,
Karl Smith

What versions of both programs and how did you create the PDF? Can you post an example of the PDF?

Importing Large Sized MS Office Word 2007 Tables

Hello,
Once again I am stuck; hopefully some experienced and helpful FM people can give me some pointers.
I am using FM 9 in WinXP and MS Office Word 2007. You know, the one that saves documents as .docx.
I get these documents from Engineers in a Word doc format that in some cases have very large tables that I need to import into FM. I have tried to import these tables as a file, as a CSV, but nothing seems to work well. I keep having problems with each method I try such that the tweaks required to make the import work are not worth it and I may as well start copying and pasting each cell.
I have also searched the forums to see if there was a post concering this type of thing, but maybe I am not searching on the right thing because I could not find a post that was similar to what I am going through.
What is the best method to import a 200 row, 6 column table from MS Office Word 2007 into FM9? The end result will need to have a header row and be editable as an FM 9 table.
Thanks for the help!
Erin

Erin, as you've found, importing Word tables can be quite a challenge because there are so many ways that the two applications have different capabilities that the import filter just can't handle them. Plus, it often leaves hidden Word "junk codes" in the table in FM which can severely mangle one's sanity later on. And, the .docx file spec is newer than the FM9 filters, so ...
The very best way to get clean import of Word tables is to use Rick Quatro's TableCleaner import:
http://www.frameexpert.com/plugins/index.htm
It's absolutely worth its weight in gold.

I want to get windows vista on the macbook pro with retina display but my first question is this that how do i install it without using a DVD OR CD disk drive, and my second question while installing windows vista do i have to tick mark the install win 7

hello i have a few problems and i hope somebody has a solution my first problem is that how can i install windows vista without using a disk drive and my second problem is that should i tick mark the option which says Install windows 7 while using boot camp please reply, Thanks,

When running Windows in a virtual environment Windows and OSx share your computer's resources such as RAM. Therefore your games can not use all your computer's resources when running.
If you install Windows natively then Windows and your games can and do use all your computer's resource such as RAM.
But as already said, older operating systems are not supported and will not run natively using Boot Camp Assistant. You must use Windows 7 if installing natively in Lion or Moubtain Lion.

Obtaining grid lines for every tick mark in a chart

I would like to create a chart that contains gridlines for each tick mark. Furthermore, I'd like to keep the notion of major tick marks being longer and being the only labeled tick marks. It seems that the XYChart is only placing gridlines for major tick marks. Pouring over the API doc, I cannot find a way to make it draw gridlines for the minor tick marks.
Is this possible out of the box?
If not, what is the correct solution? A subclass of ValueAxis?
Thanks,
Karl

Paru told me that it is not possible and to file a bug.
http://javafx-jira.kenai.com/browse/RT-17285
Karl

Word 2007 = PDF

Hi,
I'm french, sorry for my English.
I have Adobe acrobat pro extensed 9.
When i generate a PDF file with a WORD, i have a problems.
In word 2007 :
In PDF :
Thank you for your help

Converting Word (table) to pdf - lines screwed up - googled as far back as 2004.
BUG STILL exists. HELP/FIX PLEASE?
http://www.pcreview.co.uk/forums/missing-table-lines-conversion-pdf-t878406.html
http://forums.adobe.com/thread/305508
Trying to convert any word doc with tables (& shading) to PDF
- basic table, black borders throughout
- shaded headings, black outline border
- shaded subheadings, black outline border
However when convert to PDF:
- 'displays' NO top cell border for some/all shaded rows
- shows diff thickness lines
- each conversion, diff lines missing/incorrectly sized
- however converted pdf prints perfectly fine
Adobe know about the bug, per PRMW's (Paul's) post on 2009-07-15 15:44:34, however only offered a painful time consuming workaround using non-freeware Adobe Pro:
http://acrobatusers.com/forum/pdf-creation/word-pdf-table-lines-missing-or-faded#comment-7 8139
- "It is not feasable to edit 200+ tables in the PDF every time the PDF is generated, as we maintain the original in word.
- "This complete issue seems to have been passed off by Adobe as no problem and that there is a work around. I consider this an unsatisfactory response from a major product supplier.
Microsoft TechNet & NitroPdf said it's an Adobe issue & to contact Adobe to fix the bug.
Tried, but proble exists:
* Word 2010 > File > Save & Send > Create PDF/XPS Document
* Word 2010 > Save As > Pdf
* Word 2010 > Print > PrimoPdf (even tried properties > advanced > dpi 300/600/2400) > Custom
* Word 2010 > Print > doPDF v7 (even tried 'high quality images)
* Word 2010 > Print > PDFCreator
* Word 2010 > Print > CutePdf Writer (even worse)
* Nitro Pdf Reader > Convert From File > (even worse)
* www.pdfonline.com > Word to Pdf (even worse)
* www.wordtopdf.com > email: Sorry, an unexpected conversion failure occurred when converting your file.
Software:
* Word 2010 - tried with .docx & .doc (97 to 2003)
* Adobe Reader 8.2.6 (freeware), then upgraded to Adobe Reader X 10.0.1 (freeware)
* GhostScript 9.01 w32 (freeware)
* CutePdf Writer (freeware)
* PrimoPdf (freeware)
* Nitro Pdf Reader 1.4.0.11 (freeware)
* doPDF 7.2.361 (freeware)
* PDFCreator 1.2.0 (opensource - www.pdfforge.org)
Seems to display better at 300%, but lines still not right (even at 2400%), but who views pdf's at this zoom?
Message was edited by: shell_l_d

No header in output when template saved with Word 2007

Hi,
I came across a problem when saving template in Word 2007.
We have template created in Word 2003 that has a header with table with image and some text in it.
And it was working fine.
Now we had to make some modifications in this template (in the body, not in the header) and in the meantime we switched from Word 2003 to Word 2007.
When we save and uploaded the template on the server it was working fine but there was no header in the output.
I took it back to Word 2003 and made some changes to it, saved and uploaded and header was here.
Looking at the xsl-fo of the templates (from Word 2003 and Word 2007) I noticed that xsl-fo from Word 2003 in the table definition has keep-together.within-page="always" attribute which is missing in Word 2007 xsl-fo.
Word 2003 xsl-fo header table definition:
<fo:table start-indent="0.0pt" xdofo:table-summary="Template Table 1" xdofo:row-header-count="0" keep-together.within-page="always">
Word 2007 xsl-fo header table definition:
<fo:table start-indent="12.5pt" xdofo:table-summary="Template Table 1" xdofo:row-header-count="0">
Anyone had same problem?
Thanks,
Tomislav

Hi Vetsrini,
Do you have a link to a workaround for this? I having a problem with a table splitting across pages.
I'm working with tempalte creation oin word 2007 and can't keep the rows/lines together in a table.
Regards,
Hakan
Edited by: HakanB on 2011-maj-04 00:04

Using 'save as' in word 2007 corrupts a field in rtf template

I am working on a cheque template using Word plug-in (Word 2007).
I have created a number of fields to display the micr line. Examples of 3 of these fields are below. I am using micr mt font 12pt to display the micr line.
<?if@inlines:PaymentAmount/Currency/Code='CAD'?>
<?xdofx:'C' || lpad(PaymentNumber/CheckNumber,8,'0') || 'C'?>
<?end if?>
In most cases, if I make a change to the template and preview as pdf (which automatically triggers a save), the output of the micr line is fine.
If I make a word only change (i.e add a carriage return) or if I use 'save as' (i.e. when I am making a back-up of the template with a different name) and preview using pdf, the Micr line does not display properly. Instead of the micr line, I see the text from the field itself (i.e. <?end if?>) displayed in micr mt font which means a bunch of boxes and other strange characters.
It isn't just the preview output that is broken. If I generate and compare the actual xsl-fo stylesheet, there is a section missing in the broken version, and it is replaced by the strange characters.
If I go in and re-enter the code into the fields, everything is fine again until I save using 'save as' or preview after a minor 'word only' type change such as a carriage return.
Has anyone else experienced this?
Thanks,
Tam

This does not sound right.
I highly recommend you to report this to Oracle Support (open a SR).
Include:
- The product version (5 digit number)
- Include steps how to reproduce the issue (if possible with screenshots)
- Include example (either RTF and XML file and steps to reproduce).
Give no excuses to Oracle Support to come back with a vague answer
it seems you have found a bug.
cheers
Jorge

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

N100 with windows 7 - can´t highligt and copy paste in office word 2007

Hello!
Really hope some of you guys or girls can help me. After I have upgraded to windows 7 and installed the office word 2007 a very annoing problem occur, right after when i shift line in typing in word 2007. I have no problem in wordpad. all the drivers should be installed and otherwise I have not had any other problem with the upfgrade to windows 7. Hope I have managed to explain my problem, so it can make any sense to your guys.
I am using my laptop primarily for writing, so it is killing me, that I can't solve this problem. Any suggestion is welcome!
René

re-install office.

"Convert to PDF" shortcut is missing in Microsoft Word 2007

Hi
I have just updated from Microsoft Word 2003 to Word 2007. I have always had a shortcut in Word 2003 in the toolbar with "Convert to PDF". After I have upgraded to Word 2007 I cannot get the shortcut to appear in the Word toolbar.
Does anyone know how I can get the shortcut back?
/James

Version 8.1 or later are the only versions that will work with MS Office 2007. You will also have to install or repair Acrobat after installing MS Office and enable the Acrobat macros through the "About Word" panel.

Acrobat Pro 6 & Word 2007

Have a pdf document that I can open and edit in Pro 6. However, when I save out as a word.doc document and open it in Word 2007, all I have is an image of the document that I cannot edit.
Any suggestions as to what I'm failing to do?
Many thanks for any suggestions.

Original document was scanned in and then saved as a pdf - using software that came with a Kodak printer. It is editable within Acrobat Pro 6. If I turn off save images in the settings box in acrobat it fails to save at all. So I guess acrobat is just saving it out as an image.
It wasn't OCR'd.
But is there a solution?

Acrobat X 10.02 crashes when converting Word 2007 document wiht linked Visio file.

Acrobat X 10.02 crashes when converting Word 2007 document with linked Visio file and causes a C++ runtime error in Word and crashes Word.
To see the behavior create a short Word 2007 document with a linked Visio file (e.g., create a Visio file with one box and text and insert it as a link into a Word docx).
No problem in Acrobat 9

There may be some of an issue with AA X on this, but part of the blame probably goes to MS also. I would suggest you simply clip the graphic from VISIO as a vector graphic (EMF will be used by default) and not do the link and do not embed the VISIO object. The linking and use of embedded objects in WORD 2007 seems to have been a major problem and is mostly a MS issue.

Word 2007 to PDF = no bookmarks

Hi,
We recently got upgraded to Office 2007. And we use Adobe Acrobat 6.0 Standard. The OS is Windows XP.
Now, when we try to convert Word documents to PDF, the PDF converts without any bookmarks. I checked the settings in Acrobat and I have option to include bookmarks checked.
I cant seem to find the option in MS Word 2007 to cross check the same. The regular 'Convert to PDF' buttons don't appear in Word 2007.
I have tried re-installing Adobe after the MS Office upgrade was completed.
What am I missing? Or is there a known compatibility issue between Office 2007 and Acrobat 6? Any pointers will be appreciated.
Thanks,
Prasanna

Upgrade Adobe Acrobat. Version 6 doesn't support Office 2007.

Robohook.wll and Word 2007

Is RoboHook.wll necessary for Word 2007? Is RoboHook.wll necessary for RoboHelp 8 HTML or is it a leftover from earlier versions of RoboHelp?
I am using RoboHelp 8 HTML to generate WebHelp.
My Word 2007 documents (totally unrelated to my RoboHelp projects) have a global template called RoboHook.wll. My Word documents change the style formatting of my co-worker's documents when I open them. My employees do not have and do not need RoboHelp.
If I were to remove RoboHook.wll, will it cause issues with RoboHelp 8 HTML?
Thanks in advance for your assistance.
Mark

Peter,
Thank you for your reply.
We are updating everyone to Word 2007. We have narrowed it down to my environment.
I still wonder if RoboHook.wll is necessary for RoboHelp8 HTML. Any ideas?
Thanks again.
I'll check back on Monday!
Mark

MS Word 2007 table lines have interesction tick marks

Similar Messages

Maybe you are looking for