Re: [Gaim-devel] AIM custom charset

[Alexey M. <gai...@ly...>]

Mark Doliner wrote:

>On Sat, 28 Aug 2004 10:58:51 -0700, Alexey Marinichev wrote
>  
>
>>That's great too, we should change gaim_plugin_oscar_parse_im_part 
>>to this:
>>
>>        else if (charset == AIM_CHARSET_ASCII)
>>                charsetstr = "ASCII";
>>
>>Having "UTF-8" there is arbitrary; this:
>>        charsetstr = gaim_account_get_string(account, "encoding",
>>OSCAR_DEFAULT_CUSTOM_ENCODING);
>>is just as arbitrary but better for interoperability.
>>    
>>
>
>Changing it from UTF-8 to ASCII is not going to happen.  It doesn't help
>anything, and it makes things worse.  Changing it to ISO-8859-1 is a possibility.
>  
>

Agreed 100%.  The only thing changing it to ASCII would achieve is 
agreeing with the standard and not tolerating clients that do not follow 
the standard.  Assuming, of course, AIM_CHARSET_ASCII really means ASCII.

>Changing it to gaim_account_get_string(...) is horrible, because then real
>ASCII messages might not be decoded correctly if the character set specified
>in the account editor is not a superset of ASCII.
>  
>

We already do it for AIM_CHARSET_CUSTOM.  Custom does not imply ASCII, 
though.  I do not know much about charsets I do not use, are there many 
commonly used charsets that do not agree with ASCII for characters < 128?

>Attempting to convert from UTF-8, and using gaim_account_get_string(...) as a
>fallback is a possibility.
>-Mark
>  
>

That is a possibility I would be most happy with.  Thank you.

       --Lyosha