Bug 98520 - ODF Validator reported error: attribute "text:start-value" on element "text:list-level-style-number" has a bad value: "0"
Summary: ODF Validator reported error: attribute "text:start-value" on element "text:l...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL: https://issues.oasis-open.org/browse/...
Keywords: filter:odt
Depends on:
Blocks: ODF-export-invalid
  Show dependency treegraph
Reported: 2016-03-08 14:56 UTC by Franklin Weng
Modified: 2024-02-23 21:22 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

ODT file which reported containing error attribute value (41.48 KB, application/vnd.oasis.opendocument.text)
2016-03-08 14:56 UTC, Franklin Weng

Note You need to log in before you can comment on or make changes to this bug.
Description Franklin Weng 2016-03-08 14:56:00 UTC
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.
Comment 1 Franklin Weng 2016-03-08 14:58:01 UTC
This file is generated by LibreOffice

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/$Windows_x86 LibreOffice_project/55b006a02d247b5f7215fc6ea0fde844b30035b3
Comment 2 Buovjaga 2016-03-13 19:37:29 UTC
Comment 3 QA Administrators 2018-02-18 03:38:22 UTC Comment hidden (obsolete)
Comment 4 Regina Henschel 2019-08-11 11:33:08 UTC
The error still exists in Version: (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.
Comment 5 Michael Stahl (allotropia) 2019-11-11 14:21:35 UTC
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.
Comment 6 QA Administrators 2021-11-11 04:15:08 UTC Comment hidden (obsolete)
Comment 7 Regina Henschel 2021-12-09 18:45:57 UTC
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: (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
Comment 8 QA Administrators 2023-12-10 03:14:51 UTC Comment hidden (obsolete)
Comment 9 Dennis Roczek 2024-02-23 16:02:12 UTC
Still valid using https://odfvalidator.org/

@regina so, i see that #OFFICE-4118 was accepted for ODF1.4. What todo about the older versions?
Comment 10 Regina Henschel 2024-02-23 21:22:15 UTC
(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.