Created attachment 123403 [details] ODT file which reported containing error attribute value Use ODF online validator https://odf-validator.rhcloud.com/ Set to ODF 1.2 (extended conforming), and upload the ODT file (as attachment in this report), the result reported: Error: attribute "text:start-value" has a bad value: "0" does not satisfy the "positiveInteger" type This should be a LibreOffice bug.
This file is generated by LibreOffice 5.0.5.2. The output of this validator is as follows: 03_????.odt/styles.xml[2,38407]: Error: attribute "text:start-value" has a bad value: "0" does not satisfy the "positiveInteger" type 03_????.odt: Info: Generator: LibreOffice/5.0.5.2$Windows_x86 LibreOffice_project/55b006a02d247b5f7215fc6ea0fde844b30035b3
Confirmed.
** 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
The error still exists in Version: 6.4.0.0.alpha0+ (x64) Build ID: ed882d693f37779e3a09641e7cd43b7a925d2312 CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-25_00:58:18 Locale: de-DE (en_US); UI-Language: en-US Calc: CL It is similar to bug 108536. But here the MS Office import filter is involved.
for the record, this is the element: <text:list-level-style-number text:level="1" text:style-name="WW8Num1z0" style:num-prefix="*" style:num-format="1" text:start-value="0"> so presumably it was created by WW8/RTF/DOCX import.
Dear Franklin Weng, 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
I think, that 0 is a needed value and have made a proposal for the ODF TC. I'm not sure how to proceed with strict ODF 1.2 and ODF 1.3. For the extended versions, LibreOffice could write the attribute in loext namespace. Tested in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4ac9032163cf55c160145373e7c41741c9c339ca CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL
Still valid using https://odfvalidator.org/ @regina so, i see that #OFFICE-4118 was accepted for ODF1.4. What todo about the older versions?
(In reply to Dennis Roczek from comment #9) > @regina so, i see that #OFFICE-4118 was accepted for ODF1.4. What todo about > the older versions? For ODF 1.2 or 1.3 extended the loext namespace has to be used. That would be a bug fix. For the strict versions this is a general problem. For some shapes in pptx that use curves with G command we loose the shape geometry when saving to strict ODF 1.2 or 1.3, for example. We can here too not export such list item as list item, which might result in large changes to the document. I would like a more general solution: Collect all problems that occur for the specific document when saving to a 'strict' format and give the user this specific information. But whatever decision is made, you need someone to implement it. So as long as there is no customer who pays to receive a guarantee that the stored document is valid 'strict' format, I see no way to improve the situation for the 'strict' format.