On Tue, 2 Jun 2009 13:31:36 +0200 Dennis Schridde <[email protected]> wrote:
> Am Dienstag, 2. Juni 2009 12:11:42 schrieb Dennis Schridde: > > Am Dienstag, 2. Juni 2009 11:46:16 schrieb Milan Plzik: > > > V Utorok, 2. jún 2009 o 11:16 +0200, Dennis Schridde napísal(a): > > > > Am Donnerstag, 7. Mai 2009 20:03:47 schrieb > > > > [email protected]: > > > > > On Mar 11, 9:35 pm, Dennis Schridde <[email protected]> wrote: > > > > > > It appears to me that when I send offline messages to other > > > > > > ICQ users via PyICQ-t 0.8.1.3, they will receive just an > > > > > > empty message instead of the text I wrote. At least one of > > > > > > the users reporting this is using ICQ 6 (not 6.5). > > > > > > > > > > > > Can someone confirm that? Or please help me debugging it? > > > > > > > > > > I experience the same behavior -- icq contacts often complain > > > > > about empty messages being delivered instead of something > > > > > meaningful. Just for the record, encoding for offline > > > > > messages is set to auto-detect, and I set status send/receive > > > > > mode to ICQ 5.1+6 and some mood/tune/ whatever receipt, but > > > > > that should not matter. I use pyicqt 0.8.1.3-1 (debian > > > > > package), my client is gajim-0.12.1, remote client is e.g. > > > > > Miranda (supposedly even ignore the empty messages) and > > > > > supposedly official ICQ client (receives empty messages). > > > > > > > > Did someone already find a fix or workaround? Or is at least > > > > the cause known? Are there people using 0.8.1.3 who can confirm > > > > that it actually *works* for them? > > > > > > I found out something -- it's connected with encoding used for > > > outgoing offline messages. After I switched the encoding from > > > Unicode to local (iso8859-1), the problem disappeared. > > > > So it seems as if unicode conversion is broken somehow for offline > > messages? > > > > I have set <encoding>utf-8</encoding>, so if that setting is used > > at all, I assume that encoding detection is broken exclusively for > > offline messages, and it just sends nothing instead of converting? > > Or the conversion itself is broken and returns nothing in certain > > cases? > > This field in configuration file required only for default one-byte encoding. It used for online messaging with old ICQ clients (without Unicode support) and for offline messaging sometimes (because not all clients can understand offline messages in Unicode). > > I am trying <offline_messages_sendenc>0</offline_messages_sendenc> > > and 1 now, to figure out whether it is the detection logic, or the > > encoding conversion itself. > Confirmed that <offline_messages_sendenc>1</offline_messages_sendenc> > combined with <encoding>iso8859-1</encoding> works. Unicode and > auto-detect offline messages (offline_messages_sendenc=0/2) does > result in empty messages. Your result indicate that even official ICQ 6 client can't decode unicode-encoded offline messages --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
