Fix conversion of non-BMP chars
...which are apparently encoded as two consecutive \uXXXX\uXXXX escape sequences representing a UTF-16 surrogate pair Change-Id: Ic47a678dee5e28ab4dc43e115ae5c4efefb1db96 Reviewed-on: https://gerrit.libreoffice.org/67245 Tested-by: Jenkins Reviewed-by:Stephan Bergmann <sbergman@redhat.com>
Showing
Please
register
or
sign in
to comment