RichTextBox Rtf property wrong converting non ascii chars
See original GitHub issue-
.NET Core Version: 3.1.2
-
Have you experienced this same bug with .NET Framework?: No
Problem description:
After assigning to richTextBox.Rtf some rtf code with nonbreaking space (160 char code), RichTextBox converts it to \'c2\~ insted of \~.

Due to the fact that, number formatting like :N using nonbreaking space for thousand separators (in appropriate cultures) this lead to huge problems 😦(((
Expected behavior:
Nonbreaking space must be properly converted to \~.
Windows 7 x64.
Minimal repro: WinFormsCoreTest2.zip
Issue Analytics
- State:
- Created 3 years ago
- Comments:28 (28 by maintainers)
Top Results From Across the Web
WPF RichTextBox Rtf property wrong converting non ascii ...
1 Answer. The RTF string from code above does not standard-compliant RTF. The non-ASCII characters must be escaped! If replace the {\ltrch entê ......
Read more >A question about rich text file format in visual basic.net
The "save" code you've written completely ignores the actual RTF text, in the Rtf property, and instead only looks at the unformatted Text ......
Read more >RichTextBox Class (System.Windows.Forms)
Represents a Windows rich text box control. ... However, the RichTextBox control does not have the same 64K character capacity limit of the...
Read more >Rich Text Format (RTF) Version 1.5 Specification
An RTF file consists of unformatted text, control words, control symbols, and groups. ... a standard RTF file can consist of only 7-bit...
Read more >Newest 'richtextbox' Questions - Stack Overflow
The RichTextBox control allows to display or edit RTF (Rich Text Format) content, which may include formatted paragraphs, hyperlinks, and inline images.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yes, please.
Sorry, looks like it didn’t make it into 3.1.5. But it definitely made it into 3.1.6