Description: One specific type of dotted lines seems to not appear in exported PDF documents. It's gray dotted lines. It is ONLY vertical lines that dissapear, not horisontal ones - even if the line formatting is equal. I'll add some sample files to show what works and what do not works, both odf and pdf versions: table_514 - Sample document made in LibO 5.1.4 (oly one made in older version). Status: FAIL. table_523 - Same document, saved in version 5.2.3. status: FAIL. < Noumerous different documents between - won't comment all those. Status: they all fail > table_523_vertical-only_3 - Same, but another style for vertical lines applied. Status: Success. Steps to Reproduce: 1.Make new document or use an existing one (haven't tried old documents from earlier versions of LibO) 2.Make a table that have both inner and outer borders. The inner vertical borders must be colored gray and dotted. There might be several combinations of line type and colors that also is affected. 3.Export to PDF file - the vertical inner border won't be visible in the PDF file. Actual Results: the vertical inner border in tables won't be visible in the PDF file. Expected Results: All table borders lines should look excactly as in LibO Writer. Reproducible: Always User Profile Reset: No. I did install version 5.2.3.3 over an older version of LibO (5.1.4) - same results. I have also tried the same on another computer with 32 bit version of LibO (an even older version and I cannot remember what version it was). That lead me to beleive the issue is not related to user profile. Additional Info: I saw a similar issue as long as a year ago on another computer. Sadly I didn't realized that it was a bug - I thaught I had forgot something before printing (I saw it at a time when I was far away from the computer using to make the table). That was at least a half year ago, maybe longer. Same issue. I have not installed a printer at home, so I can't tell if same problem will apply if I print directly from Writer. Also print to XPS doesn't provide an actual file for some reason. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Created attachment 128880 [details] sample documents One packed 7z file consisting of 6 pair of odt/pfd files. Total of 12 files. Each odt file have an exported PDF file with matching name. In every file, I've added information on current version of Libre Office used.
Confirmed in Version: 5.3.0.0.alpha1+ Build ID: 9745d29227e471ce40e9992fefd92e10a48696fb CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: ca-ES (ca_ES.UTF-8); Calc: group
No repro with Version: 6.1.0.0.alpha0+ Build ID: cc1db6f2b0ebe05ae807628778835b62df00eca2 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-12-02_23:45:34 Locale: nl-NL (nl_NL); Calc: CL I tested: table_514 table_523
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to Telesto from comment #3) > No repro with > Version: 6.1.0.0.alpha0+ > Build ID: cc1db6f2b0ebe05ae807628778835b62df00eca2 > CPU threads: 4; OS: Windows 6.3; UI render: default; > TinderBox: Win-x86@42, Branch:master, Time: 2017-12-02_23:45:34 > Locale: nl-NL (nl_NL); Calc: CL > > I tested: > table_514 > table_523 No repro in Версия: 6.1.3.1 (x64) ID сборки: a9670562c26181ec3afbe381c9ff499ae88c98b7 Потоков ЦП: 4; ОС:Windows 10.0; Отрисовка ИП: GL; Локаль: ru-RU (ru_RU); Calc: threaded Status->WFM