Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 39618

Summary: gaim 0.7x cant display special german chars with TOC protocol
Product: Gentoo Linux Reporter: Nils Ohlmeier <develop>
Component: Current packagesAssignee: Gaim Bugs Crew <gaim-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Nils Ohlmeier 2004-01-27 15:46:00 UTC
Since version 0.70 gaim shows a line with only one space in it if the message from the buddy contained a special german character (Umlaut: 
Comment 1 Nils Ohlmeier 2004-01-27 15:46:00 UTC
Since version 0.70 gaim shows a line with only one space in it if the message from the buddy contained a special german character (Umlaut: äöüß). This happens only if the TOC protocol is used for the conversation. With the AIM/ICQ protocol everything works fine.

Reproducible: Always
Steps to Reproduce:
1. use gaim version > 0.70
2. let you send a message with a german Umlaut or view chat conversation log which contains such a char
3.
Actual Results:  
You will see only a line (starting with the usual buddy name and date and 
time) which contains a space as message 

Expected Results:  
I should see the complete message with the correct display german Umlaut. 

German Umlauts were displayed correct up to version 0.69. 
The error occurs with several clients (i tested with gaim on Windows, Appels 
ichat, AIM on Windows on the other side). 
The error is still present up to version 0.75-r7. 
I can provide conversation logs which contain these charaters and demonstrate 
the problem if this helps. 
 
emerge info: 
Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 
2.4.20-gentoo-r6) 
================================================================= 
System uname: 2.4.20-gentoo-r6 i686 AMD Athlon(TM) XP 1900+ 
Gentoo Base System version 1.4.3.10p1 
distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) 
[enabled] 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer" 
DISTDIR="/alderan/distfiles" 
FEATURES="autoaddcvs ccache distcc fixpackages sandbox" 
GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ 
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo 
http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo/ 
http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/" 
MAKEOPTS="-j4" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://rsync.ohlmeier.home/gentoo-portage" 
USE="3dnow X X509 aalib acpi acpi4linux alsa arts artswrappersuid avi berkdb 
cdr crypt cscope cups dga directfb doc dvb dvd encode ethereal fbcon flash 
foomaticdb gdbm gif gphoto2 gpm gtk gtk2 gtkhtml guile hbci imap imlib innodb 
irda java jpeg kde libg++ libwww lirc mad maildir matrox mbox mikmod mmx motif 
mozilla mpeg mysql ncurses nls odbc ofx oggvorbis opengl oss pam pda pdflib 
perl pic png python qt qtmt quicktime readline samba sasl scanner sdl skey 
slang slp speex spell sse ssl svga tcltk tcpd tetex tiff truetype usb wmf x86 
xml xml2 xmms xv zlib"
Comment 2 Don Seiler (RETIRED) gentoo-dev 2004-01-27 18:01:07 UTC
Why are you even using the TOC protocol?  TOC is the incredibly old predecessor to AIM/ICQ and should be ignored.  I don't know why they still provide it upstream.

Just use AIM/ICQ.
Comment 3 Nils Ohlmeier 2004-01-28 04:16:45 UTC
Ok, after some try and error i was finnaly able to switch my AIM account to the AIM/ICQ protocol.
But nevertheless the messages which i received over TOC are not diplayed when i try to look at them with 'View Log', allthough the messages are correctly loged to the logfile.