f677885fec
Reading OOXML _x005F_ escaped content may not get unescaped, so when writing back to OOXML do not attempt to escape it again, i.e. write _x005F_xHHHH_ as is and not as _x005F_x005F_xHHHH_. This is more a workaround, the proper fix would be to unescape _x005F_ content upon read. But then the entire "invalid XML character" escapement and handling control characters rat tail would come into play. Change-Id: I3d31dc84a362753c23a8c89f7a5d7bfd06e4367b Reviewed-on: https://gerrit.libreoffice.org/73187 Tested-by: Jenkins Reviewed-by: Eike Rathke <erack@redhat.com> |
||
|---|---|---|
| .. | ||
| inc | ||
| qa | ||
| source | ||
| test | ||
| CppunitTest_sax.mk | ||
| CppunitTest_sax_attributes.mk | ||
| CppunitTest_sax_parser.mk | ||
| CppunitTest_sax_xmlimport.mk | ||
| Library_expwrap.mk | ||
| Library_sax.mk | ||
| Makefile | ||
| Module_sax.mk | ||
| README | ||
UNO services for SAX parsing and C++ functions for XMLSchema-2 data types.
* source/expwrap:
string-based SAX parser UNO service wrapping expat
* source/fastparser:
multi-threaded token-based SAX parser UNO service wrapping libxml2
* source/tools:
+ C++ wrapper for fast SAX parser
+ C++ XMLSchema-2 data type conversion helpers
Multi-threading in FastParser can be disabled for debugging purposes with:
SAX_DISABLE_THREADS=1 SAL_LOG="+INFO.sax.fastparser+WARN"