* solenv/bin/createcomponent.xslt simply surrounds it output by <components>.
* solenv/gbuild/CppunitTest.mk got new functions
gb_CppunitTest_add[_old]_component[s] (like their gb_RdbTarget_ predecessors).
* This obsoleted current uses of solenv/gbuild/RdbTarget.mk, which also does not
work currently, as it catenates the input component files instead of passing
them through packcomponents.xslt (which now takes care about the surrounding
<components> in the input). In the future, it will likely be combined with the
recently added solenv/gbuild/ComponentsTarget.mk.
Not a count of code-units, nor a count of code-points, but try and follow
http://unicode.org/reports/tr29/ and present the grapheme count.
Add a few representative tests to try and avoid gotchas.
Both C++ and Java OfficeConnection code now always pass --headless, so no
need for SAL_USE_VCLPLUGIN=svp etc. any more. Only some C++ unit tests that
link against vcl still need an explicit --headless.
compiling an_ES.xml gave:
Warning: Time100SecSeparator is different from DecimalSeparator, this may be correct or not. Intended?
Warning: Don't forget to adapt corresponding FormatCode elements when changing separators.
Warning: QuotationStart may be wrong: U+201C “
Warning: QuotationEnd may be wrong: U+201D ”
Warning: DoubleQuotationStart may be wrong: U+2018 ‘
Warning: DoubleQuotationEnd may be wrong: U+2019 ’
* Exchanged Quotation(Start|End) and DoubleQuotation(Start|End)
Not sure about the use of '.' Time100SecSeparator whereas DecimalSeparator is ','
i.e. change x_rtl_uString_new_WithLength to always create a rtl_uString
with ref count of 1, like rtl_uString_new_WithLength, so requiring:
either the explicit use of rtl_uString_release or
passing ownership to an OUString via OUString(pStr, SAL_NO_ACQUIRE)
which will do the same in its dtor
Tell file name and actual error in error message. Print error message
to stderr. Always exit with failure when not able to open an input or
output file.
