Julien Nabet
e808025d6f
As Eike indicated in https://bugs.documentfoundation.org/show_bug.cgi?id=146404#c4 COLOR format codes are preserved in ods/fods format. The pb was the missing map back. Indeed, we had the mapping for [COLOR<something>] => Color value (eg: "ffaa16") but not the reverse mapping Color value => [COLOR<something>] Eike had provided the right code pointer in xmlnumfi.cxx. First, I thought using PaletteManager but this one is in svx and svx shouldn't be used in xmloff (dependency pb). Then I used ChatGpt (GPT-5.6 Luna) and it pointed the right process. It just consisted to use a similar callback system (DECL_LINK, IMPL_LINK, LINK) of GetUserDefinedColor. In addition, by testing all this, I noticed that maList in XColorList::GetIndexOfColor was empty. So I added the Load call in case mbListDirty is true. Change-Id: I0ef6b5901f2e4c757e88994412dbf79a13100ffd Reviewed-on: https://gerrit.libreoffice.org/c/core/+/210518 Reviewed-by: Julien Nabet <serval2412@yahoo.fr> Tested-by: Jenkins
ODF Import and Export Filter Logic
The main library "xo" contains the basic ODF import/export filter
implementation for most applications. The document is accessed
via its UNO API, which has the advantage that the same import/export
code can be used for text in all applications (from/to Writer/EditEngine).
The filter consumes/produces via SAX UNO API interface (implemented in
"sax"). Various bits of the ODF filters are also implemented in
applications, for example [git:sw/source/filter/xml].
There is a central list of all element or attribute names in
[git:include/xmloff/xmltoken.hxx]. The main class of the import filter
is SvXMLImport, and of the export filter SvXMLExport.
The Import filter maintains a stack of contexts for each element being read. There are many classes specific to particular elements, derived from SvXMLImportContext.
Note that for export several different versions of ODF are supported, with the default being the latest ODF version with "extensions", which means it may contain elements and attributes that are only in drafts of the specification or are not yet submitted for specification. Documents produced in the other (non-extended) ODF modes are supposed to be strictly conforming to the respective specification, i.e., only markup defined by the ODF specification is allowed.
There is another library "xof" built from the source/transform directory, which is the filter for the OpenOffice.org XML format. This legacy format is a predecessor of ODF and was the default in OpenOffice.org 1.x versions, which did not support ODF. This filter works as a SAX transformation from/to ODF, i.e., when importing a document the transform library reads the SAX events from the file and generates SAX events that are then consumed by the ODF import filter.
OpenOffice.org XML File Format
There is some stuff in the "dtd" directory which is most likely related to the OpenOffice.org XML format but is possibly outdated and obsolete.
Add New XML Tokens
When adding a new XML token, you need to add its entry in the following three files:
[git:include/xmloff/xmltoken.hxx][git:xmloff/source/core/xmltoken.cxx][git:xmloff/source/token/tokens.txt]