Files
odfstudio/writerfilter
Stephan Bergmann 8ea9de4f7a Turn BorderHandler::BorderPosition into scoped enum
...to avoid -Werror,-Wshadow from Clang trunk with
<https://reviews.llvm.org/D52400> "Improve -Wshadow warnings with enumerators",
warning about shadowing of BORDER_TOP/LEFT/BOTTOM/RIGHT in enum BorderPosition
in writerfilter/source/dmapper/PropertyMap.hxx.

Also, BorderPosition can apparently be made a private member of BorderHandler,
which gives extra confidence that any other uses of BORDER_TOP/LEFT/BOTTOM/RIGHT
across writerfilter/source/dmapper/ indeed meant to reference the other enum
BorderPosition.

And change BorderHandler::lcl_sprm to return early in default case, to avoid
having to come up with some new BorderPosition sentinel value to represent
"invalid pos".

Change-Id: I31e535326627cec25a17b99485bf7cf56f4c66d3
Reviewed-on: https://gerrit.libreoffice.org/61896
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2018-10-18 13:28:06 +02:00
..
…
2018-06-07 09:27:46 +02:00
…
…

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