steps to reproduce 1- open LibreOffice Writer 2- open new document (Ctrl+n) 3- create a 1x1 table 4- save as .odt (or .doc) 5- export to .pdf the upper border of the table is lost in the .pdf exported file. this bug affects 3.4.4 and 3.4.5 as well. was not present in 3.3.4. see attachments. I haven't tested in 3.4.0 -> 3.4.3, so I can't tell exactly when the regression took place in 3.4.x branch I haven't tested it either in 3.5.0 RC1, so I can't tell if this bug is still present in forthcoming new branch. reproduced it with WinXP 32bit and WinVista 64bit.
Created attachment 55956 [details] upper table border test files in the .zip file you will find test .odt files and corrensponding exported .pdf versions obtained with LibO 3.3.4 (no bug) and LibO 3.4.5 (bug)
Hmmm, are you sure? Your pdf file for 3.4.5 is better than for 3.3.4. With LO 3.5.0 rc1+ I get the same thing as your 3.4.5 pdf. I do not know if 0.25pt is big enough for screen resolution. It is perfect with border width of 1 pt. Best regards. JBF
Created attachment 55964 [details] comparative screenshot 3.3.4 vs. 3.4.5 @JBF Here's what I see in my system (Vista 64bit). These is a comparative screenshot between the 3.3.4 .pdf (upper border present) and the 3.4.5 .pdf (upper border missing) taken from Adobe Acrobat 8. I redownloaded the same .pdf files I0ve attached before, so I confirm the bug existing in 3.4.5 and not in 3.3.4. Why do you say that the 3.4.5 .pdf file is better? I doubt it's a matter of screen resolution since the 3.4.5 file has no upper border in any zoom level I tried in Acrobat (even 2400%)
again, arguing against the "screen resolution" theory, if you print the 3.4.5 test .pdf file, you will still see the missing upper border table the 3.3.4 .pdf test file instead prints correctly.
*** This bug has been marked as a duplicate of bug 42089 ***
I remove "regression” from title and keywords since issues about visibility of upper table border seems to affect 3.3.4 as well and not just 3.4.4/5 Read: https://bugs.freedesktop.org/show_bug.cgi?id=40289#c11
*** This bug has been marked as a duplicate of bug 40289 ***