Re: Question about RTF export

Dom Lachowicz wrote:
> Hi,
>
> We've gotten a few RTF export bugs recently, related
> CJK encodings. Part of the mess is due to the
> broken-ass EncodingManager class and trying to emit
> text in CP1252 and BIG5 encodings as "appropriate".
>
> I'm wondering if there's any good reason why we don't
> *always* export RTF using codepage 65001 (UTF-8) or a
> UCS2/UTF-16 codepage and just be done with it, rather
> than mucking around with "NativeWindows Encodings".
>
> Feedback from Hub, Martin, and TF is appreciated.
>
I don't see any justification beside being compatible for retarded RTF
reader that won't support UTF-8 or UCS-2/UTF-16. And they are quite
numerous.

Note that I did not originate that decision.
The Encoding Manager class should die. I have never seen so ugly code.
Received on Fri Feb 25 21:56:01 2005