Bug 135463 - FILESAVE: ODT: Error: tag name "field:fieldmark-start" is not allowed
Summary: FILESAVE: ODT: Error: tag name "field:fieldmark-start" is not allowed
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-05 13:06 UTC by Xisco Faulí
Modified: 2020-09-14 17:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
sample file (14.55 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-08-05 13:06 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2020-08-05 13:06:42 UTC
Created attachment 163971 [details]
sample file

I found this issue while creating a unnitest for bug 135144 < https://gerrit.libreoffice.org/c/core/+/100157 >

Steps to reproduce:
1. Open attached document
2. Save it as ODT
3. Check styles.xml file or use https://odfvalidator.org/

-> Styles.xml uses field:fieldmark-start and field:fieldmark-end tags and the ODF validator claims is not allowed.

Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: 58937aa4a50ecd681382f03331340da4c843b01e
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

and

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

but not in

Version: 5.0.0.0.alpha1+
Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86
Locale: ca-ES (ca_ES.UTF-8)
Comment 1 Regina Henschel 2020-08-05 16:41:33 UTC
Yes, the element has to be in an extending namespace. Saving to ODF 1.3 is OK. The error happens too, if the reference is not in header but in the body of the document.

The feature request is in https://issues.oasis-open.org/browse/OFFICE-2096. It is "ODF-Later" and the initial discussion shows, that other ideas to fix the interoperability problems exist.
Comment 3 Regina Henschel 2020-09-14 17:43:11 UTC
Validator is happy now both with ODF 1.3 extended and ODF 1.3 strict.