Created attachment 79056 [details] original and converted files. We are seeing a 3rd pary exported XLSX file that can't be opened by Libreoffice, nor by Google Docs. However it can be converted with Zamzar.com and Office365. I'm attaching to this bug an archive with both the orgiginal file and conversions from these two services. I'm using Libreoffice 3.5.4.2 on Ubuntu 12.04.
It appears to be a ZIP format issue. If you want to report wrong fonts, lack of borders or cell background, that needs to be done in a separate bug.
For now I was just reporting that the file can't even be opened. O don't know if there are other problems with the original file since it can't be opened. I can only open the converted ones. Regarding zip: I tried unzipping by hand with the Linux unzip command and it works.
And if you zip it back, does it open after that?
Yes, this makes it work: unzip 41.xlsx mv 41.xlsx /tmp/ zip -r 41.xlsx * Ark can also read and extract the contents without any problem. The unzip command issues this warning: warning: 41.xlsx appears to use backslashes as path separators unzip -l returns this: Archive: 41.xlsx Length Date Time Name -------- ---- ---- ---- 303 05-09-13 14:33 _rels\.rels 936 05-09-13 14:33 [Content_Types].xml 320 05-09-13 14:33 xl\workbook.xml 1982 05-09-13 14:33 xl\sharedStrings.xml 12099 05-09-13 14:33 xl\styles.xml 5573 05-09-13 14:33 xl\worksheets\sheet0.xml 590 05-09-13 14:33 xl\_rels\workbook.xml.rels -------- ------- 21803 7 files After I unzip and zip again the result of unzip -l is: Archive: 41.xlsx Length Date Time Name -------- ---- ---- ---- 936 05-09-13 14:33 [Content_Types].xml 0 05-11-13 11:49 _rels/ 303 05-09-13 14:33 _rels/.rels 0 05-11-13 11:49 xl/ 12099 05-09-13 14:33 xl/styles.xml 320 05-09-13 14:33 xl/workbook.xml 1982 05-09-13 14:33 xl/sharedStrings.xml 0 05-11-13 11:49 xl/worksheets/ 5573 05-09-13 14:33 xl/worksheets/sheet0.xml 0 05-11-13 11:49 xl/_rels/ 590 05-09-13 14:33 xl/_rels/workbook.xml.rels -------- ------- 21803 11 files We see that the slashes are changed and that there are now individual entries per directory. This is clearly an interoperability problem. Now, the question is who is to blame. Is it LO that doesn't properly handle these files? Or are these files not conforming to the specification? Can someone from the team double check what is written here about slashes? http://www.pkware.com/documents/APPNOTE/APPNOTE_6.2.0.txt
(In reply to comment #4) > Can someone from the team double check what is written here about slashes? > http://www.pkware.com/documents/APPNOTE/APPNOTE_6.2.0.txt It clearly says that all slashes should be forward slashes.
*** Bug 69230 has been marked as a duplicate of this bug. ***