Sergey V. Udaltsov spake unto us the following wisdom:
> Just tested with jabber - russian is perfectly ok. So it seems personal
> Oscar's problem.
It is not Oscar's problem, it is the other side's problem ... let me
guess, the other side is running either an older version of gaim,
another OSS IM program, or Trillian. None of those handle Oscar
i18n correctly.
I have been able to interoperate correctly with iChat and the official
AIM client using Cyrillic text. Oscar uses 16-bit Unicode characters
for *all* non-ASCII, non-ISO-8859-1 text. Many IM clients (including
gaim previous to 0.60cvs) break this completely by sending
locale-specific character sets and *marking* them as ASCII or
ISO-8859-1 ... this *happens* to work of both sides are using
similarly broken clients and the same working locale. (Thus the
hideous hack that is rusconv to ensure that both sides are using the
same character set).
If at all possible, ask the person you are chatting with to get an IM
client that is not broken. I am aware that handling i18n *correctly*
is breaking compatability some, but I am not entirely sure what to do
about it. The problem lies in the fact that the compatability problem
stems from the other person's client not obeying the "rules" of Oscar,
and thus we cannot predict what sort of incorrect IMs they may be
sending.
Ethan
--=20
And if I claim to be a wise man / it surely means that I don't know.
-- Kansas, "Carry on Wayward Son"
|
