office-gobmx/writerfilter
Miklos Vajna 8396bffef7 writerfilter: dmapper ctor can read TextInsertModeRange directly
Change-Id: If17ae09266134b4bc410eab1a1b2f5139ba93a12
2015-10-19 09:23:42 +02:00
..
documentation
inc writerfilter: dmapper ctor can read TextInsertModeRange directly 2015-10-19 09:23:42 +02:00
qa Replace "SAL_OVERRIDE" with "override" in LIBO_INTERNAL_ONLY code 2015-10-12 17:52:29 +02:00
source writerfilter: dmapper ctor can read TextInsertModeRange directly 2015-10-19 09:23:42 +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