office-gobmx/writerfilter
Adam Co 76bd128ff8 Fix 'outset' and 'inset' table border type import in DOCX and RTF
In the past, LO did not support 'outset' and 'inset' border types
for tables, so when encountering them - LO converted them to other
types of border. Now that LO supports it - DOCX and RTF filters
were changed to import these border types correctly.
DOC filter was not changed, because creating a proper DOC sample
file that has these border types (needed for the 'bordertest.hxx'
file) was not possible right now. So at least DOCX and RTF filters
are fixed.

Change-Id: Ida2449d45a0ac138388f3cbfeb41657db1d4cda9
Signed-off-by: Michael Stahl <mstahl@redhat.com>
2014-05-08 22:19:03 +02:00
..
documentation
inc
qa
source Fix 'outset' and 'inset' table border type import in DOCX and RTF 2014-05-08 22:19:03 +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, doc and rtf.

== Module contents ==
 * documentation
 * inc: global headers (can be included by other modules)
 * qa: unittests and subsequenttests
 * 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
 * filter: the UNO filter service implementations, invoked by UNO and calling
   the dmapper + one of the tokenizers
 * ooxml: the docx tokenizer
 * resourcemodel
 * rtftok: the rtf tokenizer