This did result in many border issues when we had copied the content of a top header row, into the cells of a secondary header row to make one row (in an effort to pass accessibility, which likes one header row, one header column!). I did this because I realize that when you copy and paste in MS docs, it copies much formatting in the background which the user is not intending to paste. As I had many tables that were similar, I did this once, and then used the upper left corner selection icon, when hovering over that part of the table, to copy the entire thing and then manually make content adjustments.
What I did do to help some of the border inconsistencies go away leaving only the most minute, barely noticeable issues on the onscreen viewed PDF, was to recreate the tables fresh and type the content back in myself.
The two strings I followed for assistance/suggestions:Īs it is really a presentation/screen problem which I'm assuming Adobe cannot control and does not know how to address so they stay quiet hoping people figure out a work-around, or realize it's not an *actual* problem (PDF and Word Doc I have print out just fine), merely visual. Any many of the people were Windows users. I thought it was maybe a Macintosh issue, but when I looked up the problem, I noticed MANY posts about this-one in particular noting that the problem has existed since 2004 (I'm sure before, but maybe he's referencing it being an issue noted on the forum). So I'd be glad to know if this works as well on your side, Yet I can't explain what exact circumstances / settings lead to these borders appearing while none are selected.
So I think there's little to do with Acrobat and the PDF format there, and the border/padding settings are indeed a possibility.īesides, I'd like to add a strange behavior I observed regarding borders, and I hope my experience will be of help to you guys. You can frequently observe such issues with borders appearing with no apparent reason just sticking to MS Word's interface, without ever exporting to PDF.
Without entering a rant against Adobe, I agree this ought to be solved in Word only, therefore acknowledging Luke's approach.