I got broken encoding in vCards.
http://code.google.com/p/pyicqt/issues/detail?id=145
--
WBR, Anton
I have troubles with offline messages encoding too.
--
WBR, Anton
&RQ and Miranda 0.5 Unicode.
--
WBR, Anton
I'm on pyicqt-0.8.1-git.tar.gz. Problem is on sending from client to
transport but only for offline messages.
--
WBR, Anton
Yes, detectunicode is 1 in config.xml. Broken offline messages look
like the following:
[quote]
[15:59:29] летающий_блюдец/icq: 퇰
[15:59:45] летающий_блюдец/icq: Обычно в рамках фокус-группы стараются
рассматривать не более 10 ?основных вопросов
[15:59:45] летающий_блюдец/icq: 퓮㌠ⴠ⃫⃯⃨㿬
[15:59:45] летающий_блюдец/icq: Бинауральные ритмы — артефакт работы
головного мозга, воображаемые звуки, которые мозг воспринимает
(«слышит»), хотя реальные звуки отсутствуют.
[15:59:45] летающий_блюдец/icq:
[15:59:45] летающий_блюдец/icq: ⃭
[/quote]
Some messages are ok, but another is broken.
If you can not see unicode symbols, screenshot is here:
http://img166.imageshack.us/img166/3477/1111yt4.png
--
WBR, Anton
It's my fault. I used outdated tarball. I cloned git repo and offline
messages are ok now.
Thanks for your work!
--
WBR, Anton
After update FreeBSD ports to 0.8.1.3 I recieve an email from a user
reporting following problems:
--------------------------------------------------------
Hi.
After update i cant discovery transport via ejabberd.
#uname -a
FreeBSD skuns 7.1-RELEASE FreeBSD 7.1-RELEASE #0
#pkg_info|grep jabber
ejabberd-1.1.4_2 Free and Open Source distributed fault-tolerant Jabber serv
jabber-pyicq-transport-0.8.1.3,1 Python ICQ-Transport for Jabber
#sockstat|grep 5347
ejabberd python2.5 43897 3 tcp4 127.0.0.1:63875 127.0.0.1:5347
ejabberd beam 7970 22 tcp4 127.0.0.1:5347 *:*
ejabberd beam 7970 25 tcp4 127.0.0.1:5347 127.0.0.1:63875
#/usr/local/etc/rc.d/jabber-pyicq-transport restart
Stopping jabber_pyicq.
Waiting for PIDS: 43897, 43897.
Starting jabber_pyicq.
Adding Ad-Hoc defaults for user: xstatus_receiving_mode with value 0
Adding Ad-Hoc defaults for user: xstatus_sending_mode with value 0
Adding Ad-Hoc defaults for user: xstatus_saving_enabled with value 1
Adding Ad-Hoc defaults for user: xstatus_option_smooth with value 1
Adding Ad-Hoc defaults for user: xstatus_display_icon_as_PEP with value 1
Adding Ad-Hoc defaults for user: xstatus_display_text_as_PEP with value 1
Adding Ad-Hoc defaults for user: xstatus_icon_for_transport with value 0
Adding Ad-Hoc defaults for user: away_messages_receiving with value 1
Adding Ad-Hoc defaults for user: away_messages_sending with value 1
Adding Ad-Hoc defaults for user: clist_show_phantombuddies with value 0
Adding Ad-Hoc defaults for user: clist_deny_all_auth_requests with value 0
Adding Ad-Hoc defaults for user: utf8_messages_sendmode with value 2
Adding Ad-Hoc defaults for user: offline_messages_sendenc with value 2
Adding Ad-Hoc defaults for user: msgconfirm_sendmode with value 2
Adding Ad-Hoc defaults for user: msgconfirm_recvmode with value 1
Adding Ad-Hoc defaults for user: user_mood_receiving with value 1
Adding Ad-Hoc defaults for user: user_activity_receiving with value 1
Adding Ad-Hoc defaults for user: user_mood_receiving with value 1
#
On jabber-pyicq-transport-0.8.1.1,1 Python ICQ-Transport for Jabber
work fine!
--------------------------------------------------------
Do you have any idea what could be happening?
--
Renato Botelho
OK, but what about the guy say "After update i cant discovery
transport via ejabberd" ?
Do you think this is related with this extra-verbose problem?
Thanks
--
Renato Botelho