When upgrading from QT-3.2.3-r1 to QT-3.3.0 (still the same problem in QT-3.3.0-r1) my swedish characters in Licq is replaced by some ugly characters in the history and in incoming messages. I can type the characters in the input field and there they looks good, but when they go to the history field they are transformed to other characters. Example: "
When upgrading from QT-3.2.3-r1 to QT-3.3.0 (still the same problem in QT-3.3.0-r1) my swedish characters in Licq is replaced by some ugly characters in the history and in incoming messages. I can type the characters in the input field and there they looks good, but when they go to the history field they are transformed to other characters. Example: "åäö" in the input field is tranformed to "åäö" in the history/send messages field. If i change the encoding to Unicode (UTF-8) the old history looks good but all newly typed messages have those characters destroyed. And the people the messages is sent to receives ugly characters to. This is not the case if i have ISO 8859-1 encoding, then it's only a problem for me when reading incoming and outgone messages. If i downgrad to QT-3.2.3-r1 (and recompile licq) the problem disappears. Thanks for reading :) /Lars Reproducible: Always Steps to Reproduce: 1.emerge -u qt # (when having QT-3.2.3-r1) 2.licq 3.# type send "åäö" to someone on the list and look in history Actual Results: I see the characters "åäö" Expected Results: I should see the characters "åäö"
i'm experiencing the same with all my german umlauts which is quite annoying. there is a patch for licq on the licq-devel list for licq 1.2.7 and it is also available on the licq homepage: http://www.licq.org/download.html => http://www.sjaensch.org/licq1.2.7-qt3.3-sprintf.patch this patch has already been applied in licq CVS. the people there also say that this has been fixed in QT cvs (i just downloaded a snapshot and it says this in the changelog: "- QString sprintf() again interprets strings, %s, as UTF-8 strings, not as Latin1 strings." guess gentoo needs either a patch for qt or licq or newer versions of the respected apps. JG
sorry for the 2nd comment, forgot to mention that i just downgraded to qt 3.2.3, restarted kde/licq and everything is working fine again, without recompiling licq. JG
I have the same problem with windows-1251 charset.
Created attachment 26580 [details] updated ebuild for licq-1.2.7 hey guys, for all who don't use licq cvs and/or qt cvs: i made a little ebuild that incorporates the patch would be nice if someone could submit it into the portage tree...
I installed the a patch [1] from a thread in the german-Forum [2] on 2boxes and it worked really well. You just need to add a "epatch ${FILESDIR}/licq1.2.7-qt3.3-sprintf.patch" to the ebuild. Any change to see this patch in portage? It's really ugly to write in languages that need these specific characters... [1] http://www.inf.tu-dresden.de/~s2247401/ebuilds/net-im/licq/files/licq1.2.7-qt3.3-sprintf.patch [2] http://forums.gentoo.org/viewtopic.php?p=935837#935837
I really like to see this in portage
fixed in upcoming 1.3.0 release (and 1.3.0_pre is in portage)
