Hi Hristo, On Thu, May 11, 2006 at 07:39:46 +0300, Hristo Hristov wrote:
> > Btw, your "CP437" values in ImplTextEncodingData.mpBestMimeCharset and > > mpBestUnixCharset most certainly are not correct. > What I know is that MIK encoding is based on CP437. But it can't be represented in cp437, I guess, otherwise you would use cp437 instead. The mpBestMimeCharset string could be used for example when writing HTML files, the charset="cp437" attribute would be written and the data converted to cp437, in case of HTML with the missing characters converted to #nnnn representation, so no actual harm with modern browsers, but in other context maybe with losses. The mpBestMimeCharset should be identical or a superset of the actual encoding, or have only little differences. A mpBestUnixCharset by definition can't be cp437, as it isn't a native Unix encoding. Probably iso8859-5 containing Cyrillic would be best, if all characters are representable in it. > > Coded sets like your MIK are somewhat a corner case, unregistered, not > > a standard, but to some extend commonly used in one region. > Yes it is, and this encoding is very often used in DOS Cyrillic files. I wonder whether there is some common cpNNN alias that maps to it and maybe is even already present in our source. Did you check for that? > > Maybe Stephan Bergmann has an opinion on this? > Where Can I find him? > Is he reading this list? Most times he does. May take a few days though. 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]
