Hello,
On 2/8/06, Daniel Henninger <[EMAIL PROTECTED]> wrote:
> I get notifications when people post comments on blathersource, so no
> need to point me at them. ;D But what do you mean "if client
> places incorrect encoding name into registration form"?
I'm sorry. It was an feature of old snv version (august 2005) and now
it's removed.
I got an IQ from transport <username/> <password/> <encoding/>
Now it ask me only <username/> and <password/>.
> All I ask
> for in the registration form is username and password, so I'm
> confused about where you would be entering a wrong encoding name. As
> for the status bug, I need to look into that a tad closer. I think
> there might be something broken at a lower level. Can you ...
> actually email ought to work ... email me a russian phrase that I can
> test with as a status message?
??????????, ???????? ?????????. <- russian
> And is this Russian typed via unicode
> or via codepage 1251?
Afaik old native ICQ clients (2003 and earlier) use cp1251 for sending
messages (by often not for status).
It seems like icq5 use unicode. JIT uses cp1251 (default russian installation).
--
Regards,
Oleg
From [EMAIL PROTECTED] Wed Feb 8 14:17:31 2006
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Wed Feb 8 14:18:02 2006
Subject: [py-transports] PyICQ: FYI
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
> On 2/8/06, Daniel Henninger <[EMAIL PROTECTED]> wrote:
>> I get notifications when people post comments on blathersource, so no
>> need to point me at them. ;D But what do you mean "if client
>> places incorrect encoding name into registration form"?
>
> I'm sorry. It was an feature of old snv version (august 2005) and now
> it's removed.
>
> I got an IQ from transport <username/> <password/>
> <encoding/>
>
> Now it ask me only <username/> and <password/>.
Yeah, I found that many clients didn't pay attention to the extra
field... so I decided that wasn't the right way to do this. Of
course, I've since seen the supposedly proper way of offering
additional fields it to use xforms, so ... I may look into that.
>> All I ask
>> for in the registration form is username and password, so I'm
>> confused about where you would be entering a wrong encoding name. As
>> for the status bug, I need to look into that a tad closer. I think
>> there might be something broken at a lower level. Can you ...
>> actually email ought to work ... email me a russian phrase that I can
>> test with as a status message?
>
> ??????????, ???????? ?????????. <- russian
Awesome, thanks, I'll give that a shot!
>> And is this Russian typed via unicode
>> or via codepage 1251?
>
> Afaik old native ICQ clients (2003 and earlier) use cp1251 for sending
> messages (by often not for status).
> It seems like icq5 use unicode. JIT uses cp1251 (default russian
> installation).
Ok. So here's a question. I am, probably obviously, from the U.S.
I am using a Mac as my primary desktop platform. I can easily type
unicode characters with no problem. I can not, however, figure out
how I would go about changing code pages and typing russian
characters via code page 1251. Anyone have any suggestions on how I
might do this? It may be simple and I just haven't seen it.
Basically, I'm more or less stuck with either iso-8859-1 or unicode
as far as I am capable of setting.
Daniel
>
> --
> Regards,
> Oleg
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
