office-gobmx/xmloff
Markus Mohrhard 66c6d1ef20 prevent invalid ods files with loext:fill-character
ODF specifies that extension elements in a document are removed before
the validation. With our old implementation of the number format export
this could result in two number:text elements following each other.

According to the spec a number:text element may not follow another
number:text element.

The number:text element before loext:fill is actually not that
interesting so it makes more sense to make this one an extension
element.

Possible documents showing issues:

fdo45268-1.xlsx
fdo49150-1.xlsx
and many more

Change-Id: I3ad92b8a61a246b3dbc0132d9a2c367488a766d0
2014-08-16 07:14:28 +02:00
..
dtd
inc update_pch 2014-08-13 10:10:33 +02:00
qa
source prevent invalid ods files with loext:fill-character 2014-08-16 07:14:28 +02:00
util
CppunitTest_xmloff_uxmloff.mk
JunitTest_xmloff_unoapi.mk
Library_xo.mk
Library_xof.mk
Makefile
Module_xmloff.mk
Package_dtd.mk
README

Contains 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 sw/source/filter/xml.

There is a central list of all element or attribute names in
xmloff/inc/xmloff/token.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 respecive 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.

http://www.openoffice.org/xml/general.html
http://www.openoffice.org/xml/xml_specification.pdf

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.