2009/7/9 Vincent Lefevre <[email protected]>: > On 2009-07-09 22:43:55 +0100, Thomas Adam wrote: >> Oh -- and I ought to mention, the application itself has to understand >> UTF8 since it sets the _NET_WM_NAME XAtom in the first place. You can >> do this for yourself (I assume you're running under a UTF8 locale, >> etc., already): > > No, on my machine, fvwm runs under ISO-8859-1 locales (IIRC because > of a spacing problem under UTF-8). But you don't need UTF-8 locales > to understand UTF-8!
I know that. And running under a Latin-1 locale, FVWM is displaying all the right characters for me -- accents and all (especially so, since the string stored in the WM_NAME XAtom differs from that in _NET_WM_NAME -- quelle surprise.) I think part of the problem is your continued assertion that WM_NAME is used in preference of _NET_WM_NAME, and it's being blind-sighted a little. So please, I'd like you to detail step-by-step here, exactly what it is we would need to do to reproduce your problem -- then I'll take a look and try and verify it. -- Thomas Adam
