I just answer myself.. ;-)
> As you said, I downloaded 1.3.4 from sf.net and unpacked it to some
> folder. I copied the patch in the folder licq-1.3.4 and did the
> following:
> I didn't try to compile or really apply the patch then, because auf
> these "FAILED" statements. Should I try or did I miss anything?
I got the source from SVN and could apply the patch without problems.
After installing many Ubuntu dev packages I finally could compile the
source with plugins. Now I removed any overide encoding settings on my
micq for my testaccounts and started messaging:
17:30:49 RealDampy hat sich eingeloggt (verbunden) [ICQ Lite
(??)].
mICQ> s dampy
* 9S. ********* RealDampy (verbunden) [ICQ Lite (??)] 2007-03-22
17:30:48
+ ********* dampy (verbunden) [ICQ Lite (??)] 2007-03-22
17:30:48
IP: ***.**.**.*** / 192.168.2.180:44610
TCP-Version: 9 Benutzer-zu-Benutzer (4) Direktverbindungs-
Kennung: ccebf3a0
SBL ids: 22510, 0: 8781/22510/1, 2: 5994/0/1
Gruppe: Family
Fähigkeiten: CAP_ISICQ, CAP_SRVRELAY, CAP_AVATAOR, CAP_UTF8
As you can see, licq 1.3.4/SSL sends CAP_AVATAOR and CAP_UTF8 now. I
don't really understand what this means, but it looks fine so far.
Perhaps see http://micq.org/ICQ-OSCAR-Protocol-v7-v8-v9/ for details,
but this stuff is too heavy for me. O:-)
mICQ> m dampy ping
17:31:15 RealDampy >>» ping
17:31:26 RealDampy ««« so das geht schonmal
17:31:44 RealDampy ««« nur hat er hier noch iso für den
gegenüber drin
17:32:02 RealDampy ««« so mal umgestellt auf utf-8
mICQ> msg RealDampy juchu äö
17:32:09 RealDampy »»» juchu äö
mICQ> msg RealDampy € pff
17:32:29 RealDampy »»» € pff
Until here, micq has no special override encoding (as I said before).
This usually works without problems with almost all clients like e.g.
Mirabilis ICQ or Miranda. licq was configured (this tiny dropdown
field in message windows upper right corner) to ISO8859-15 (I had to
set this manually in $HOME/alex/.licq/licq.conf since licq doesn't
offer it in this dropdown menu). So far everything works fine.
Now I set licq back to UTF-8 as it's system default.
17:32:36 RealDampy ««« sauber äöü
mICQ> msg RealDampy doch nich
17:32:43 RealDampy »»» doch nich
mICQ> optcontact dampy encoding
Option encoding für Kontakt RealDampy ist nicht gesetzt.
17:33:33 RealDampy ««« äöü
mICQ> msg RealDampy öüß
17:33:43 RealDampy »»» öüß
Something strange happens now. Messages with German umlauts (which are
great for testing this stuff) from micq (still no encoding override)
to licq seem correctly encoded, both sides show them correctly. Now
the way back from licq to micq is crap. licq still shows these
characters with no errors but in micq undecoded utf-8 characters
appear (the ugly two byte chars in message from 17:33.33).
Now I override micq's standard encoding settings for this account:
mICQ> optcontact dampy encoding utf8
Setze Option encoding für Kontakt RealDampy auf UTF8.
mICQ> m dampy foo öäü
17:46:31 RealDampy »»» foo öäü
17:46:43 RealDampy ««« ja ja öäü €
Everything works fine now in all directions, but I still have to
override encoding settings manually as I have to with licq 1.3.2 users
too.
I will post a link of this thread to micq mailing list as well. I hope
Rüdiger Kuhlmann has time to visit it and have a look on the problems
appearing.
HTH and greets
Alex
P.S.: I replaced UIN and IP with *
