Created attachment 119587 [details] See cell with content "Revenue implications" In the attached document the table cell with "Revenue implications" is missing its left border.
Created attachment 119588 [details] How Microsoft Office 2013 renders the document
Created attachment 119589 [details] How LibreOffice renders the document
Thanks Matthew for the issue and document. Nice example. (By the way: I guess the table should be at page 1 too?) Ciao - Cor
Thanks Matthew. Confirmed. Ciao - Cor
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
still the same issue in recent daily. (NB bug 103781 for new issue with this file)
** 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
still inVersion: 6.1.0.0.alpha0+ Build ID: a9b202a6b7000e7af34f2a639ca207122a3968bf CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-12-26_23:09:36 Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
still in Version: 6.3.0.0.alpha0+ Build ID: 082144fa0fb2021cfb41494bb6eb5bf417e58ab1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-12-31_03:11:43 Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US Calc: threaded
tblPrEx is the tag that we entirely miss while importing and the key to this bug. It contains table row formatting elements such as borders, shade, spacing, etc. Solving this bug alone would only require the implementation of the borders element of tblPrEx, but that is just 1 of the 9 elements this tag can have. LO does not deal with row properties the same way it deals with table and cell properties, so I don't see an easy way implementing this. Plus, I could not reproduce this from 0 using 2016 MSO, it just outputs everything into a tcPr (table cell props) tag and that is perfectly fine with LO. If someone starts working on this, a possible time saver: Modify model.xml so you can read the elements of tblPrEx. paste under <resource name="CT_TblPrEx" ... > <element name="tblBorders" tokenid="ooxml:CT_TblPrEx_whateveryouwannacallit"/>
László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/8ffc1299ebf83450e67cf2a89304859e2558cd27 tdf#95033 DOCX import: apply tblPrEx table border It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.