Created attachment 55327 [details] documents and screenshots mentionned in the problem description, packed into one file Problem description: the document "Orig.DOC" in Word-Format is generated by a program. It opens ok in Word 2007 - Screenshot Word_2007.jpg. If opened in Libreoffice, it is not useable. Screenshot LO-3.4.4.jpg shows it in LibreOffice 3.4.4 (official release); Screenshot LO-3.5-Beta2.jpg shows it in LibreOffice 3.5.0-Beta2. If the document is opened by Word 2007 and saved without applying changes (to file Saved_by_Word.doc) and this file (Saved_by_Word.doc) is opened with LibreOffice, it show more or less ok (Screenshot LO-3.5-Beta2_Saved_by_Word.jpg). Used System: Intel I5-32xx, Windows7 64-bit Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20100101 Firefox/10.0
Reproduced with LOdev 3.5.0beta2 4ca392c-760cc4d-f39cf3d-1b2857e-60db978 Ubuntu 10.04.3 x86 Linux 2.6.32-37-generic Russian UI
Related to bug 43874 ?
Created attachment 102933 [details] MS Word 2007 SP3 screenshot differs from bugreporter's one Hello. The original table is still destroyed in LibreOffice 4.0.3.2. “Saved_by_word.doc” in LibreOffice is similar to bugreporter screenshot. But both files is destroyed in my MS Word 2007 SP3 (see attached screenshot). Unfortunately I have not newer version of MS Office. If the file is corrupted in newer MS Office, the report is better to close. Can somebody test it?
The documentation for this bug has been produced by MS Office 2007 SP3. The reason for the diffence in the screenshot in Comment #3 is the setting in the options to show formatting characters. In German: Word-Optionen / Anzeige / Alle Formatierungszeichen anzeigen. Regards
tested under Win7x64 I confirm the Orig.doc file is correctly rendered by MS Word Viewer and incorrectly rendered by LibO 4.2.5.2 and 4.4.0.0.alpha0+ (*) I see the same problem with AOO 4.1.0 so the bug is inherited from OOo. I also confirm that the Saved_by_word.doc files is correctly displayed by OOo (*) Build ID: abc28ffc04067eb24840fbf564c311aaee10f84d TinderBox: Win-x86@42, Branch:master, Time: 2014-07-15_07:20:05
Additional data points: the file Orig.doc is correctly rendered in MS Word 2010, where it is identical to the original submitter's Word 2007 screenshot. It may (or may not) amuse to note that Orig.doc does not render correctly in Microsoft's Word Online product, where it is far more garbled than in LibreOffice. (Screenshot attached.)
Created attachment 102959 [details] Garbled rendering in Word Online Just an example from another piece of software that can't render the table correctly which happens to be a Microsoft product.
> The reason for the difference in the screenshot in Comment #3 is the setting > in the options to show formatting characters. Yes. I am sorry for the disturbance. It's the first time I have seen showing formatting characters changing a page representation so much.
** 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-07-18
Created attachment 117317 [details] opened in LO 5.0.0 RC3
The pproblem still exists in Version: 5.0.0.3 (x64) Build-ID: f79b5ba13f5e6cbad23f8038060e556217e66632 Windows 8.1 64-bit see image dated 2015-07-19
** 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
Still present in LO 5.2.1.2 64-bit, Windows 10
LO thinks the table has 7 (seven) columns whereas Word sees only 3 (three). After saving again with Word2007, Lo sees only 3 columns, too.
Still repro with: Version: 5.4.0.0.alpha0+ Build ID: 84f2ff67a7e404febf710b1dc7f66d06745c503f CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-09_23:20:01 Locale: nl-NL (nl_NL); Calc: CL
Shows ok in 5.4.0.2 (RC)
@Helmut thanks 4 feedback!!! RESOLVED WORKSFORME