Caolán McNamara
d3cf169ea1
A presentation can reference sound files outside its own package, on a slide transition, an animation, or a click action. Linked graphics already come under link management, where the user allows each external reference on its own. Bring presentation sounds under the same link management. Each external sound is registered as a link the user can allow through the link-update infobar or "Edit, Links". For the uno api move these sounds around as XSoundReference so their allowed state can be moved with them. So that changes the property from a string to an XInterface. Setter still accept a string, getter returns the new XInterface, there's an acknowledged possibility of incompatibility despite being technically api-change-passing Signed-off-by: Caolán McNamara <caolan.mcnamara@collabora.com> Change-Id: Ib7deea2f78cf5c5b9958e43adb8e6f46b1b31e80 Reviewed-on: https://gerrit.collaboraoffice.com/c/core/+/6970 Reviewed-by: Miklos Vajna <vmiklos@collabora.com> Tested-by: Jenkins CPCI <releng@collaboraoffice.com> (cherry picked from commit 0aa870b7b5a6bda50bab50c7a0a41d28fdf4f6ab) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/208430 Tested-by: Jenkins Reviewed-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]