89e44da1ab
...but only with old MSWord compat flag SplitPgBreakAndParaMark. All of the other cases (COLUMN_BREAK and non-empty runs) split the paragraph, so why not here? This document shows it is needed, but only for SplitPgBreakAndParaMark documents. Note: Word 2003 doesn't display "modern" docx well in this regard. It adds extra paragraphs where it shouldn't. There are already example unit tests that ensure that extra paragraphs aren't written for SplitPgBreakAndParaMark == false. The actual bug's document is not related to the compatibility flag. That will be handled in separate commit. Change-Id: I27399780c909663f9a2b21974a5b385bea67f9ec Reviewed-on: https://gerrit.libreoffice.org/70835 Tested-by: Jenkins Reviewed-by: Justin Luth <justin_luth@sil.org> |
||
|---|---|---|
| .. | ||
| documentation | ||
| inc | ||
| qa | ||
| source | ||
| util | ||
| CppunitTest_writerfilter_misc.mk | ||
| CppunitTest_writerfilter_rtftok.mk | ||
| CustomTarget_source.mk | ||
| IwyuFilter_writerfilter.yaml | ||
| 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
dbgutil 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