This bug was tested LibreOffice v4.1 RC1 running in windows 7 and XP. It appears that LibreOffice loses formatting when importing MS .docx files. I have attached an example. Steps to reproduce the bug: 1. Open attached Demo-2012SummerOlympics.xlsx document in calc 2. Open attached Demo-2012SummerOlympics.xlsx document in Excel2010/Office 365 3. Compare the documents. Note item #1 from the screenshot that the rows should alternate from white to blue.
Created attachment 81707 [details] MS .xlsx file imports incorrectly
Created attachment 81713 [details] Comparison of xlsx in Excel vs Calc 1-3
THis is the missing Format As Table feature that is currently developed as part of the GSoC project.
*** Bug 66378 has been marked as a duplicate of this bug. ***
*** Bug 66379 has been marked as a duplicate of this bug. ***
Marking as NEW as Markus has confirmed that it's being developed now. Markus - you happen to know who is developing it, then we can move to assigned.
(In reply to comment #6) > Marking as NEW as Markus has confirmed that it's being developed now. Markus > - you happen to know who is developing it, then we can move to assigned. If at all it should be kept in New. It is Kohei and my GSoC student so we are aware of the bug. Please don't assign this bug to the student. IMO it is bad to force him to look and care bug reports at this stage as he should focus on the tasks he gets assigned by us.
This issue is still reproducible: - Libreoffice 4.1.5.3 Build ID: 1c1366bba2ba2b554cd2ca4d87c06da81c05d24 - Libreoffice 4.2.2.1 Build ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f - Libreoffice 4.3.0.0.alpha0 Build ID: b6a43bcbbf9e9a5655fd36fd4c8ef72d585f67b0
*** Bug 89107 has been marked as a duplicate of this bug. ***
*** Bug 81711 has been marked as a duplicate of this bug. ***
Created attachment 115487 [details] Comparison of xlsx in Excel 2010 vs Calc 5.0 There are some improvements in LO 5.0.
** 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-20170103
Still not table formatting in Version: 5.4.0.0.alpha0+ (x64) Build ID: bf80bbb7b75febc2769d6b64e6981224982f8fe2
** 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
Same in 6.1 alpha1.
*** Bug 112371 has been marked as a duplicate of this bug. ***
*** Bug 122917 has been marked as a duplicate of this bug. ***
*** Bug 122109 has been marked as a duplicate of this bug. ***
*** Bug 91329 has been marked as a duplicate of this bug. ***
*** Bug 130637 has been marked as a duplicate of this bug. ***
*** Bug 149436 has been marked as a duplicate of this bug. ***