68bc6a5dd6
Bit count for the image is a numeric value (sal_uInt16) but only a handful of values make sense - namely 1,4,8,24 and 32. This replaces the numeric value with an enum, which only accepts those values and checks the correct values are used at compile time. Change-Id: I0fc137c62bce3b0d021f05019a1648da628521bc Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112408 Tested-by: Jenkins Reviewed-by: Tomaž Vajngerl <quikee@gmail.com> |
||
---|---|---|
.. | ||
inc | ||
qa/cppunit | ||
source/filter | ||
util | ||
CppunitTest_lotuswordpro_import_test.mk | ||
CppunitTest_lotuswordpro_test_lotuswordpro.mk | ||
IwyuFilter_lotuswordpro.yaml | ||
Library_lwpft.mk | ||
Makefile | ||
Module_lotuswordpro.mk | ||
README |
Import filter for file format of Lotus Word Pro. == Description == The import is not direct, but via an intermediate format: StarOffice XML, the predecessor of ODF (yes, the code is old). The entry point to the filter is class LotusWordProImportFilter (refer to Source code section), but that just hooks up the necessary machinery for processing StarOffice XML produced by the filter. The real fun starts in function ReadWordproFile() (source/filter/lwpfilter.cxx); this function initializes the parser (class Lwp9Reader) and the SAX XML handler that produces the output (class XFSaxStream). The Lwp9Reader class then does the actual parsing. If the module is built with debug level greater than 0, it is possible to examine the intermediate XML: set environment variable DBG_LWPIMPORT_DIR= to an existing directory and, on opening an lwp document, a file named lwpimport.xml will be created in that directory. == Source code == === Module contents === * inc: module-global headers (can be included by any file in source) * qa: cppunit tests * source: the filter itself * util: UNO passive registration config === Source contents === * filter: lwp document format parser * filter/LotusWordProImportFilter.cxx: the entry point to the filter * filter/xfilter: export to StarOffice XML