Created attachment 71383 [details] test data Platform: All Build: LO 4.0 beta1 Steps ----- 1. Open the attached document Problem ------- It is a mess, whose most obvious issue is characters appears truncated. Meanwhile it seems large part of the contents in page 3,4,5,6 are missing. I'd appreciate if some one could have a list of bugs in this document. Or I'll arrange time to have a thorough review next week.
Created attachment 71384 [details] screenshot of how it should look.
Looks pretty broken on LO Version: 4.3.0.0.alpha0+ Build ID: 5e01904de993caa3d497a8f6c82a846336e70eef TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2013-12-06_02:05:01 OS X 10.9.
** 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 (4.4.1 or later) 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: 2015-04-18
Still broken. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 01a189abcd9a4ca472a74b3b2c000c9338fc2c91 TinderBox: Win-x86@39, Branch:master, Time: 2015-06-14_07:46:28 Locale: fi-FI (fi_FI)
** 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.5 or 5.2.1 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-20160920
Berufsausbildungsvertrag_2007.doc is useless because it is protected against editing, so a developer can't play around with it.
(In reply to Justin L from comment #6) > Berufsausbildungsvertrag_2007.doc is useless because it is protected against > editing, so a developer can't play around with it. Thanks, Justin. Let's close.
Created attachment 136149 [details] P1+2 in Word 2010
Created attachment 136150 [details] P1+2 in LO 5.3.5.2
Sorry guys for disturbance, but this issue is still valid. In fact, it demonstrates so many issues, that this might hurt you, but simply closing this issue doesn't solve them at all. Open the file in Word, and you can see something similar to https://bugs.documentfoundation.org/attachment.cgi?id=136149. In contrary, open it in any version of OO; LO, whatever, and see something similar to https://bugs.documentfoundation.org/attachment.cgi?id=136150. Given, you have the Arial font installed, the fields should flow similar, but obviously the word parser/renderer is completely overstrained. It produces a horrible mess. It is missing complete pages, and even doesn't get the page format right. The result is a disaster, and hopefully, LO will do better one day. So, please keep this open, and somebody might willing and be able to really fix it. For reference, I will add the follow up pages from Word as screenshots.
Created attachment 136151 [details] Page 3+4 in Word 2010
Created attachment 136152 [details] Page 5+6 in Word 2010
For the record, I issued this bug back in 2007 for OO.
Created attachment 136153 [details] The same document, with just the protection disabled @Justin: I just clicked on "Disable protection" (translated) in Word. Can't this be done in LO as well?
Justin: see the previous comment and added file. The bugginess is faithfully preserved. Also: this can be achieved by going to Tools - Options - LibO Writer - Compatibility - untick Protect Form. I know this because I recently had to figure it out.. Unfortunately I did not realize this was the same case. (It's true that this report is a bit invalid as it has many issues, but let's change this one to be about the cell content thing)
** 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
Dear QA Team, yes, hereby I confirm, the behaviour of LO didn't changed up to version 6.1.3.1, Build-ID: 10(Build:1) CPU-Threads: 8; BS: Linux 4.18; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded. Obviously, the attached document produces so many rendering issues/visual distortions, that nobody with the power of fixing such bugs ever touched this issue seriously. As Yifan Jiang noted in #c0, nobody ever attempted to create a detailed listing of the issues, it suffers from. BTW, I filed this issue back in 2008 of OO something, hence it celebrates its 10th birthday this year.
Dear Yifan Jiang, 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
Retested with: Version: 6.3.2.2 Build-ID: 30(Build:2) CPU-Threads: 8; BS: Linux 5.3; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded Outcome: no visual difference to former tests, almost all issues persist in year 11 of its existence.
Bug is still present. Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: threaded
Dear Yifan Jiang, 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
I hereby confirm, that the issues with this document persists with: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 24; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded The origins of this bug date back to 2007 (for OO at that time)
repro 7.6+ with comment 14's attachment 136153 [details]. So, I'm focusing on the top right form column, where the words "Name, Vorname" are in 11pt Arial when they should be in 7pt Arial (according to MS Word 2010). confirmed comment 22 that in bisect-releases this is inherited from OOo.
Created attachment 187459 [details] Berufsausbildungsvertrag_2007_unprotected_MSWord2010_screenshot.png This displays rather badly in MS Word 2010 as well. Differently than LO, but still parts are "missing". (A PDF export from MS Word 2010 looks OK though.)
Using Word 2010, I round-tripped to DOC and DOCX formats. DOCX opened OK. DOC had the same problem - still 11pt cell content.