From 08bf088959c677e61cb118bf8d0bf092d3f21466 Mon Sep 17 00:00:00 2001 From: Michael Stahl Date: Tue, 11 Oct 2016 17:22:36 +0200 Subject: improve comment about non-BMP code points in RTF Change-Id: If906fdea692ca4a4df4f7110f42b7360d8b845da --- svtools/source/svrtf/rtfout.cxx | 3 +++ 1 file changed, 3 insertions(+) (limited to 'svtools') diff --git a/svtools/source/svrtf/rtfout.cxx b/svtools/source/svrtf/rtfout.cxx index f64c3c8b8823..cb722db4e243 100644 --- a/svtools/source/svrtf/rtfout.cxx +++ b/svtools/source/svrtf/rtfout.cxx @@ -54,6 +54,9 @@ SvStream& Out_Hex( SvStream& rStream, 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. SvStream& Out_Char(SvStream& rStream, sal_Unicode c, int *pUCMode, rtl_TextEncoding eDestEnc, bool bWriteHelpFile) { -- cgit