Mike Kaganski
9fac5940ce
A graphic-object shape with no embedded graphic data exported as <draw:image><text:p/></draw:image>. Per ODF's draw-image content model draw:image has a choice between common-draw-data-attlist (the xlink:href and friends attributes) and office-binary-data, followed by draw-text (text:p etc.). Without either alternative of the choice the element is incomplete, and the validator rejects it - the diagnostic mentions text:p because the parser stops at the missing choice content before reaching the draw-text part where text:p would be valid. Emit an empty <office:binary-data/> placeholder when there is no xlink:href and no graphic data, satisfying the choice. Groundwork for the clip polygon that follows, which is written on exactly such a shape: a picture placeholder that never got an image. Signed-off-by: Mike Kaganski <mike.kaganski@collabora.com> Change-Id: I5bf792c60affd35b33779c91be0a381eb074f00f Reviewed-on: https://gerrit.collaboraoffice.com/c/online/+/9189 Tested-by: Jenkins CPCI <releng@collaboraoffice.com> Reviewed-by: Caolán McNamara <caolan.mcnamara@collabora.com> (cherry picked from commit 6d1cbfc9fb8e9a705b05f6cdddd4a87a630e973d) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/210035 Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org> Tested-by: Xisco Fauli <xiscofauli@libreoffice.org>
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]