My company is looking for a Silverlight RTF-Control able to view/edit RTF documents created by another tool. We need to support different languages.That's why I'm evaluating your C1RichtTextBox control - which by the way does a good job.But I came up with one issue, that would be a show stopper for us: Converting RTF documents containing non latin characters (most times) leads to extra characters being displayed after the original character - or to documents containing "boxes" instead of the character. (Entering the same character in the editfield directly works fine)Quick way to reproduce:Enter an 'œ' (HTML: œ UNICODE: #339) to a Word document - save as RTF - copy RTF source code to your demo applications "Load from RTF" => only empty "box" will be displayedTo get a more impressive effect, use chinese or japanese characters.Am I doing something wrong? Is this a known issue?Thanks for your answerslo
It was a bug, there were some characters from the ansi codepage not correctly handled. I just added them, and also made the code a bit better to support other code pages. Note that currently we only support the ansi 1252 code page, Silverlight only has support for unicode, no code pages. So the 1252 code page is hard coded in the RtfFilter library, other code pages can be added (we ship the source of the RtfFilter as a sample). We also support unicode characters (that is, \uN in rtf), so if the rtf editor you are using saves characters in unicode it should work fine, MSWord seems to save characters in ansi 1252 when it can, and unicode otherwise.
The fixes made to the RtfFilter will be included in the next release.
Thanks for the quick answer. I look forward to test the new version!