Created attachment 48006 [details] sample file When saving a file (see attached) in xlsx (Office Open XML Spreadsheet) format includes the following xf records: <xf applyAlignment="false" applyBorder="false" applyFont="true" applyProtection="false" borderId="0" fillId="0" fontId="1" numFmtId="41"></xf> <xf applyAlignment="false" applyBorder="false" applyFont="true" applyProtection="false" borderId="0" fillId="0" fontId="1" numFmtId="44"></xf> <xf applyAlignment="false" applyBorder="false" applyFont="true" applyProtection="false" borderId="0" fillId="0" fontId="1" numFmtId="42"></xf> <xf applyAlignment="false" applyBorder="false" applyFont="true" applyProtection="false" borderId="0" fillId="0" fontId="1" numFmtId="43"></xf> These numFmtIDs 41,42,43 and 44 are not predefinied in ECMA-376-1 so corresponding <numFmt> elements should exist in <numFmts> but in this file we only have: <numFmts count="3"><numFmt formatCode="GENERAL" numFmtId="164"/><numFmt formatCode="YYYY/MM/DD" numFmtId="165"/><numFmt formatCode="DDDD, MMMM\ D", "YYYY" numFmtId="166"/></numFmts>
taking this one ...
Hi Everyone! I confirm this bug in my environment too. I have just verified and reproduced this ancient and long time bug. This is my environment: - OpenSuSE linux 12.1, x86-64 architecture, kernel 3.1.10-31; - LibreOffice, linux, x86-64, 3.5.3.1 (RC1) and 3.5.3.2 (RC2), vanilla rpm builds. To simply reproduce it: - you can create a new spread sheet; - "save as" it as xlsx 2007/2010 format; - open it on Gnumeric; - you will get: -- an "Undefined number format id '42'"; -- a spread sheet without any grid on cells. This is also well described here: http://ubuntuforums.org/archive/index.php/t-1611874.html Have a nice evening, Carlo
Still present in LibreOffice 4.2.3.3 420m0(Build:3)
** 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.3 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-06-08
Tested with LO 5.1 and ubuntu 16.04
I have this problem with files created using both LibreOffice versions: * 6.0.7.3.0+ * 6.1.5.2 Running on Arch Linux, locale: en-US (en_US.UTF-8)
(In reply to JJ from comment #6) > I have this problem with files created using both LibreOffice versions: > * 6.0.7.3.0+ > * 6.1.5.2 > > Running on Arch Linux, locale: en-US (en_US.UTF-8) Dear JJ, This bug has been in RESOLVED WORKSFORME status for more than 6 months. If the issue is still reproducible with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/, please report a new issue in https://bugs.documentfoundation.org/enter_bug.cgi providing, if needed, the steps and documents to reproduce it. Thanks for your understanding and collaboration. Closing as RESOLVED WORKSFORME
Xisco, with which LO version does this work correctly for you? LibreOffice developers appear to just like to close bugs that they didn't bother to fix and interoperability seems to be of no interest to them. So really there is little reason for others to file bugs to help to improve LO.
Experiencing this issue when saving a (modified) .xlsx file with: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: c998691e22ceda15c89d55cf7005201f0392dadb CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-14_11:54:20 Calc: threaded
Created attachment 176565 [details] xlsx file saved by LO 7.3.0.0a exhibiting the issue When you open this file gnumeric, you get an error message about an undefined format id 42.
Dear Andreas J Guelzow, 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