#include <hallo.h>
* Wladimir Mutel [Wed, Jul 20 2005, 03:28:00PM]:
> Package: icewm
> Version: 1.2.22-2
> Severity: important
> 
> 
> How to reproduce :
> 
> 0. Generate locales en_US.UTF-8 and uk_UA.UTF-8
> 1. Start icewm with locale en_US.UTF-8
> 2. Start Mozilla from icewm.
> 3. In Mozilla, navigate to page with Russian title, like
>       http://linux.org.ru
> 4. See big space between "-" and "Linux" in window title bar. (as well
>       as in taskbar and tooltip for this window)
> 
> How it should work :
> 
> ...
> 1. Start icewm with locale uk_UA.UTF-8
> ...
> 4. See "LINUX.ORG.RU - Русская информация об ОС Linux" in window title
>       bar. So many letters between "-" and "Linux" ! :>
> As seen on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318923 ,
> this behaviour could be caused by Xft/FontConfig deficiency. In

Indeed, that is broken. However, not exactly in the way you expect it.
Let me rephrase you statement, commenting details.

There are two ways of doing it wrong:

 - not support Unicode at all, which has the consequences:
   - users need to work in traditional-charset-locale
   - users need to setup the fonts for their exact locale correctly
     (which means lots of work with IceWM themes that hardcode the
     charset). They also need to make sure all their chars are covered
     by the selected fonts
 
 - support Unicode in a limited way, which means: rely on fontconfig
   doing everything for us. That is how it has been done in IceWM,
   having its limitations:
   
   - because many fonts do not provide glyphs for all charsets,
     something must do font replacement for it. There are
     implementations like the pango lib which is clever but slow (which
     not that bad for few strings in icewm) or the one from rxvt-unicode
     which is less mature and still needs manual tunning (providing font
     (family) lists manually).

The current icewm version 1.2.22 has apparently a bug - UTF-8 works (as
long as the choosen fonts has the glyphs) in all menüs and in the
taskbar command line, but is broken everywhere else (looks like not
processing multibyte at all).

EOF,
Эдуард.

Reply via email to