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.
Thanks,
Dom
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
Received on Fri Feb 25 19:03:00 2005
This archive was generated by hypermail 2.1.8 : Fri Feb 25 2005 - 19:03:01 CET