f71606c920
look for local variables that can be std::move'd to parameters off by default, since it doesn't do proper data flow analysis Change-Id: I3403a0fcffd165bdea6a772528bc53995c5fdb40 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/135527 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk> |
||
|---|---|---|
| .. | ||
| documentation | ||
| inc | ||
| qa | ||
| source | ||
| util | ||
| CppunitTest_writerfilter_dmapper.mk | ||
| CppunitTest_writerfilter_filters_test.mk | ||
| CppunitTest_writerfilter_misc.mk | ||
| CppunitTest_writerfilter_rtftok.mk | ||
| CustomTarget_source.mk | ||
| IwyuFilter_writerfilter.yaml | ||
| Library_writerfilter.mk | ||
| Makefile | ||
| Module_writerfilter.mk | ||
| README.md | ||
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