Created attachment 117492 [details] This is my colleague me sent Microsoft Office 2007 created original XLSX table Dear Developers, My colleague sent me a Microsoft Office 2007 or 2010 created .xlsx file. After I edited the calc table, I saved the table in Libreoffice Calc with Microsoft Excel 2007/2010/2013 XML format (.xlsx the file extension). With Libreoffice correct opening the calc table, but my colleague Microsoft Office application is not. The original.xlsx file in my Ubuntu system the file command says following: teszt.xlsx: Microsoft Excel 2007+ The another name saved Libreoffice Calc created .xlsx file the file command says following: teszt2.xlsx: Zip archive data, at least v2.0 to extract I tryed the Office open XML sheet format too the saveas dialog, but the file command producing the second file related result. I attaching the original and the second Libreoffice saved files, possible this is help. I tested this issue in my Ubuntu 14.04 system with original packaged Libreoffice 4.2.8 version, the Libreoffice 4.4.4 latest version and Libreoffice 5.0 RC3 version. Testcase: 1. Open the attached teszt.xlsx file. 2. Save the file with an another name, the office 2007 related calc formats. Expected result: Microsoft Office if this is possible need opening the another name Libreoffice Calc saved .xlsx file. Actual result: My tested Libreoffice versions correct opening both two files, but my colleague Microsoft Office version unfortunately only the first file opening right. Attila
Created attachment 117493 [details] This is a saved .xlsx table with I simple save as in Libreoffice Calc after I opened the first attached file
Hello Attila, I can open file teszt2.xlxs in excel 2010 without problem. Seems to be a problem in your colleague's office. What's the version of his office?
Hi Raal, I will ask he when come back from holiday. Me unfortunately not have Microsoft Office product to test this issue, I not use my machines with Windows and Microsoft office. This is a good news with you opened right the teszt2.xlsx file with Office 2010. Attila
tested both attachements under http://www.docspal.com/viewer the original one from MSO is correctly loaded the file save in LibO fails to be loaded so some issue probably exists and is probably limited to old MSO versions (2007 right?) which is probably used by DocsPal too. anyway I set status to NEW since LibO alters compatibility and interoperability of that file
Same problem with LO Calc 5.0.2. MS Excel viewer cannot open an unedited Excel file saved in LO Calc file which LO Calc can open after saving. MS Excel 2007 opens the LO Calc saved file after repairing what it sees as a corrupted file. The repair log states: <?xml version="1.0" encoding="UTF-8" standalone="true"?> <recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>error058520_01.xml</logFileName><summary>Errors were detected in file 'D:\Public\Public Downloads\174270_1-TAX FORM 2015_R saved in LO.xlsx'</summary><repairedParts summary="Following is a list of repairs:"><repairedPart>Repaired Part: /xl/worksheets/sheet1.xml part with XML error. Load error. Line 2, column 249.</repairedPart></repairedParts><repairedRecords summary="Following is a list of repairs:"><repairedRecord>Repaired Records: String properties from /xl/sharedStrings.xml part (Strings)</repairedRecord></repairedRecords></recoveryLog> I can upload the files if required.
Created attachment 119790 [details] Linux console output (repeated lines reduced) I'm not sure this is a valid bug, nor that it should be fixed. RT files cannot be open with Excel 2007 and Excel Viewer but they open fine with Excel 2010.
** 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
Dear Attila Hammer, 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
I retested this with LO master 7.1+. Resaved XLS/X open both in MSO 2007 and 2016. So I close as WFM. Note: now saved XLSX is similar size to original, unlike before when it was larger, probably wrong.