2003-07-22 15:32:28 UTC
Unfortunately, we have hundreds of these characters in our dB as they are routinely used in our shop.
Substituting \'97 for \emdash does properly display the emdash character in a richtext control. However, the \'97 is immediately converted to \emdash upon loading the control. Consequently it displays properly but if the .TextRTF property of the control is saved, it will overwrite the \'97 tag with the \emdash tag and not display properly if loaded again.
It been tough to find more info about this problem. MSKB 308310 mentions under the heading - Compatibility Problems on Systems Running Windows 2000 and Later, that "Riched20.dll emulates the Rich Edit version 1.0 through Rich Edit version 3.0. This emulation may cause the compatibility problems."
While the use of these character may not be widespread, I don't think \emdash and \endash are trivial issues. They are part of the RTF specification and were supported in earlier rich edit versions.
It is extremely frustrating to have to convert data both prior to and after displaying as a workaround. One of the reasons we used the RichText control rather than a third-party control was the inherent stability we assumed with a MS-supported control. The fact that MS has apparently remained silent about this, is even more frustrating.