your knowledge on the matter is really helpful!
Seeing your advice I can only imagine how many errors my templates
Just two questions:
- How do you validate your FODT files?
- Do you have a preferred documentation reference for generating FODT
I think that the error UI is not correctly describing what is an XML
error and it should prompt a more specific error message (for example
"Cannot save malformed XML") and maybe a technical detail could be
outputted to in the console.
I submitted the following bug report:
Maybe this issue is impacting even other users.
On 27/04/19 17:49, Piet van Oostrum wrote:
Francesco Ongaro <firstname.lastname@example.org> writes:
By removing the whole 'FooterTable_Row' it successfully saves an FODT.
By removing 'style:family="table-cell"' it successfully saves an FODT.
You should put the table-related styled (style:family="table*") inside the
<office:automatic-styles> rather than the <office:styles>.
<office:styles> is meant to be used for named styles that the user can select through the user
interface, for example the Styles and Formatting side bar, or the Styles menu. The user interface
doesn't have named table column, row or cell styles. On the other hand <office:automatic-styles>
is for styles that are directly set in an object.
With these changes (and the corrections to the XML in my previous message), it works.)
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Impressum (Legal Info)
: 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