diff options
| author | Michael Stahl <mstahl@redhat.com> | 2016-10-11 17:22:36 +0200 |
|---|---|---|
| committer | Michael Stahl <mstahl@redhat.com> | 2016-10-11 17:23:30 +0200 |
| commit | 08bf088959c677e61cb118bf8d0bf092d3f21466 (patch) | |
| tree | 4ebe38ded1bb3cc493cdb00906aa7ad3ebd519b5 /filter | |
| parent | c8054c1d6885067caf557b5b3179975793cf80f7 (diff) | |
improve comment about non-BMP code points in RTF
Change-Id: If906fdea692ca4a4df4f7110f42b7360d8b845da
Diffstat (limited to 'filter')
| -rw-r--r-- | filter/source/msfilter/rtfutil.cxx | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/filter/source/msfilter/rtfutil.cxx b/filter/source/msfilter/rtfutil.cxx index 32e04fa81877..6b1dd95ed9f6 100644 --- a/filter/source/msfilter/rtfutil.cxx +++ b/filter/source/msfilter/rtfutil.cxx @@ -45,6 +45,9 @@ OString OutHex(sal_uLong nHex, sal_uInt8 nLen) // (it only talks about "Unicode character", but then explains how values of N // greater than 32767 will be expressed as negative signed 16-bit numbers, so // that smells like \uN is limited to BMP). +// However the "Mathematics" section has an example that shows the code point +// U+1D44E being encoded as UTF-16 surrogate pair "\u-10187?\u-9138?", so +// sal_Unicode actually works fine here. OString OutChar(sal_Unicode c, int* pUCMode, rtl_TextEncoding eDestEnc, bool* pSuccess, bool bUnicode) { if (pSuccess) |