Hi Hristo, On Sun, May 07, 2006 at 17:33:56 +0300, Hristo Hristov wrote:
> > Btw, as that encoding probably is not a MIME encoding, I suggest to > > remove the RTL_TEXTENCODING_INFO_MIME flag from > > aImplMIKTextEncodingData. > What means MIME encoding? MIME (Multipurpose Internet Mail Extensions) charsets actually are a combination of CCS (coded character set) and CES (character encoding scheme). MIME charsets though are not only used in mail context, for example also HTML and the like, protocols and databases use them. For OOo, beside some agreed-upons and the ISO-8859-* charsets that are covered by RFCs, and other charsets covered by RFCs such as UTF-8, only IANA registered charsets should have the RTL_TEXTENCODING_INFO_MIME flag, which makes it more likely that information may be stored, transported and retrieved without losses, given that the reader knows how to decode it. For a list of charsets registered with IANA see http://www.iana.org/assignments/charset-reg/ Btw, your "CP437" values in ImplTextEncodingData.mpBestMimeCharset and mpBestUnixCharset most certainly are not correct. Coded sets like your MIK are somewhat a corner case, unregistered, not a standard, but to some extend commonly used in one region. Maybe Stephan Bergmann has an opinion on this? Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
