Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


Hi Michael,

the extended schema is in https://opengrok.libreoffice.org/xref/core/schema/libreoffice/

The standard itself is working in progress. You can follow it in https://www.oasis-open.org/committees/documents.php?num_per_wg=100&wg_abbrev=office&sort_field=d1.submission_date&sort_type=DESC

Kind regards
Regina

Michael H schrieb am 15-Jul-19 um 16:59:
I've got custom built files that are failing ODT validation. One of these
failures is for loext:contextual-spacing

Is there documentation similar to the ODF specification for Libre Office
extensions?  All I'm finding are discussions about the issue, and actual
code that is apparently what's IN libreoffice.  I'm looking for the spec
that shows what tags this field is allowed under, and what the allowed
values are. I see mentions this field is confirmed to be part of the ODF
1.3 spec (which I'm assuming means it (will) require renaming to something
like text:contextual-spacing) , but I don't see any list or syntax for ODF
1.3.

Thanks!

Michael Hart



--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.