Created attachment 114549 [details] Sample doc file At work we use MS Office to process certain document templates prepared from other government bodies. MS Office used is 2002 (or 2003). There appear to be serious problems when displaying the same files on LibO 4.3.5 (as well as 4.3.6): although some table cells look good, others make text "disappear". We have attached one of these .doc files and also include screenshots on how the files look on both MS WOrd as well as on LibO. Table formatting seems to be a rather serious issue on LibO. Unfortunately, examining the other bugs listed here I can not really tell if this one is a duplicate or not.
Created attachment 114550 [details] File on MS Word 1/2
Created attachment 114551 [details] File on MS Word 2/2
Created attachment 114552 [details] File on LibO 1/2
Created attachment 114553 [details] File on LibO 2/2
Reproducible with LO 4.4.1.2, Win 8.1. -> The grey frames are not visible.
This looks much the same all the way back to LO 3.3.0 - presumably there is an issue here with font metric compatibility / line spacing -> Version: Inherited from OOo
(In reply to A (Andy) from comment #5) > Reproducible with LO 4.4.1.2, Win 8.1. > > -> The grey frames are not visible. The main issue for us is not the visibility of the grey frames, but rather that the cell contents are not entirely visible when opening with LibO. That is, the user has to manually adjust cell height in order for the cell content to become visible.
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Created attachment 124429 [details] LibO 3.3 (on the left) rendering better than 5.0.5 (on the right)
Created attachment 124430 [details] LibO 3.3 (on the left) eating the same line as 5.0.5 (on the right)
(In reply to tommy27 from comment #8) > Test to see if the bug is still present on a currently supported version of > LibreOffice (5.0.5 or 5.1.2 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 The bug is still present on 5.0.5. Operating system is Windows 10 64-bit, Libreoffice is 5.0.5.2 (32-bit). > If you want to do more to help you can test to see if your issue is a > REGRESSION. To do so: > [...] > 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 I installed 3.3 on a Windows 7 VM. Comparing 3.3 and 5.0.5.2, one can see that formatting is better on the older version. See attachment "LibO 3.3 rendering better than 5.0.5.png". However, on some cells the cell contents are truncated on both versions, see "LibO 3.3 eating the same line as 5.0.5.png" Hence, I will set version to "inherited from OOo". I have uploaded a couple of screenshots
** 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
Created attachment 159786 [details] tdf90408_fontsizeChanged.doc: minimal example where fontsize goes from 10 to 12 The big problem here is that after these gray macrobutton widgets, the fontsize changes from 10 to 12. When I export this to DOCX, I can see that the text is littered with fontsize 10, so there shouldn't be a good excuse for changing the fontsize...
Seems to be related to this commit: commit a79a0101f114e0fcac40503220c5d34750124367 Author: Oliver Bolte on Date: Wed Jul 18 13:46:57 2007 +0000 INTEGRATION: CWS swqbf100 (1.102.50); FILE MERGED 2007/07/09 13:31:57 hbrinkm 1.102.50.1: #i79169# save attributes of macrobutton text and apply them to the macrobutton field
Dear Michail Pappas, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e4042da6e63ed2ac6e1687f696580d9a502bad83 sw: fix crashtesting assert on tdf90408-1.doc It will be available in 7.6.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.
using comment 13's example, I repro 7.6+. I noticed the "boxes" are using PUA U+f06f, so the actual character shown is irrelevant since this is a "personal use area" for that specific font (Times New Roman). In general, I think OP's document looks pretty good now. When MS Word 2010 round-trips it to DOCX, then LO opens the DOCX fine - everything is in 10pt font.
Created attachment 187412 [details] macrobutton.doc: the original that comment 14's patch was trying to solve. It looks like a simple revert is in order. The bug document that triggered this patch now works fine without it.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/02c56a8d3ea86f28ffbdd645f83d1d4de2b56bea tdf#90408 Revert #i79169# save/apply attributes of macrobutton text It will be available in 7.6.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.