office-gobmx/writerfilter
Miklos Vajna e1b2476254 RTF filter: use 'using' instead of 'typedef'
Change-Id: Ie7182fa30155a8090421cf9a669525be99f0e0a7
Reviewed-on: https://gerrit.libreoffice.org/38042
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Jenkins <ci@libreoffice.org>
2017-05-26 09:07:27 +02:00
..
documentation
inc RTF filter: use 'using' instead of 'typedef' 2017-05-26 09:07:27 +02:00
qa tdf#105204: ShellCheck nitpicks for watch-generated-code.sh 2017-05-11 16:26:09 +02:00
source RTF filter: use 'using' instead of 'typedef' 2017-05-26 09:07:27 +02:00
util
CppunitTest_writerfilter_misc.mk
CppunitTest_writerfilter_rtftok.mk
CustomTarget_source.mk
Library_writerfilter.mk
Makefile
Module_writerfilter.mk
README

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: cppunit tests
 * source: the filters themselves
 * util: 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 dmapper can be dumped into an XML file in /tmp in
     debug builds, start soffice with the `SW_DEBUG_WRITERFILTER=1`
     environment variable if you want that.
 * filter: the UNO filter service implementations, invoked by UNO and calling
   the dmapper + one of the tokenizers
 * ooxml: the docx tokenizer
 * rtftok: the rtf tokenizer