Rich Text Format (RTF) Specification, Version 1.9.1, "Unicode RTF" ( original location https://www.microsoft.com/en-us/download/details.aspx?id=10725 ) explains, that the in \uN, N should be signed 16-bit value. However, we output it unsigned. To test: * Create a new text document; * Put there a character from a range U+8000-U+FFFF; e.g., Liberation Sans has U+FB02 LATIN SMALL LIGATURE FL "fl"; * Export to RTF; * Check the resulting RTF in a text editor. Expected: \u-1278 Actual: \u64258 It doesn't create problems in Writer, and also doesn't seem problematic in Word; but better be closer to what Word itself outputs (and it indeed outputs signed 16-bit values).
https://gerrit.libreoffice.org/c/core/+/188257
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/c37b49d621537f623cea71ad8699e83248b169ac tdf#167660: export \uN as signed 16-bit values It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.