7 Jun 18:07
Re: Encoding
* Casey Allen Shobe <lists@...> [2006-03-27 13:04]: > On Sunday 26 March 2006 15:06, Iulian Ciorascu wrote: > > Ladislav Laska wrote: > > > > Yeah, that was, but as far as i know, when gentoo package 'ncurses' is > > > > compiled with 'unicode' use flag, ncursesw will be compiled instead. > > > > No, it's not "instead", it's "also". > > I have ncurses and ncursesw libraries just as you show. Am using Gentoo, > ncurses with the unicode use flag. I'm not sure what ncursesw is, but if I > read your mail right, it could be fixed with a slight modification to the > ebuild, possibly adding a unicode flag to centericq? I just patched my local centericq ebuild to link to ncursesw instead of ncurses. Now I can see the umlauts in the input window as I type them, but the cursor advances by *2* characters when pressing an umlaut key, so it looks like there's a space between the umlaut (last character) and the cursor. So, if you press an umlaut 3 times, there are 3 spaces between the 3 umlauts and the cursor. I also tried to send the umlauts. It works from cicq (utf8) to cicq (utf8) via jabber. Tried it with a friend who's using ICQ 5.1 on Windows, he sent me 3 umlauts. I saw nothing, so I examined the history file. less shows them as <E4><F6><FC> whereas vim decodes them to äöü. Looks like ISO-8859-1 and CenterICQ does not recode it to UTF8. So, what I can tell now is that with my version of CenterICQ linked against ncursesw, CenterICQ is able to *display* UTF8 encoded(Continue reading)
RSS Feed