Noel Grandin
828c1999e0
writerfilter wants to convert incoming RTF and OOXML files into writer's document model. But it currently has to do so by manipulating the limited subset that we expose through the UNO API. This is both slower and less accurate than having access to the full document model. So move it inside, and then we can strip out various hacks, and optimise imports. Change-Id: Ie1114d28130ef5f9a786531bc552cb8ee7768015 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165953 Tested-by: Noel Grandin <noel.grandin@collabora.co.uk> Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
945 B
945 B
Import Filters for LibreOffice Writer
The writerfilter module contains import filters for Writer, using its UNO API.
Import filter for DOCX and RTF.
-
Module contents
documentation: RNG schema for the OOXML tokenizer, etc.inc: module-global headers (can be included by any files under source)qa:cppunittestssource: the filters themselvesutil: UNO passive registration config
-
Source contents
dmapper: the domain mapper, hiding UNO from the tokenizers, used by DOCX and RTF import- The incoming traffic of
dmappercan be dumped into an XML file in/tmpindbgutilbuilds, start soffice with theSW_DEBUG_WRITERFILTER=1environment variable if you want that.
- The incoming traffic of
filter: the UNO filter service implementations, invoked by UNO and calling the dmapper + one of the tokenizersooxml: the docx tokenizerrtftok: the rtf tokenizer