On Mon, Oct 17, 2011 at 4:14 PM, Francesco Poli <[email protected]> wrote: > On Mon, 17 Oct 2011 08:58:08 -0400 Paul Tagliamonte wrote: > >> On Sun, Oct 16, 2011 at 3:06 PM, Francesco Poli > [...] >> > So it must be something that Midori does, when setting the window title: >> > this "something" seems to cause problems with Fluxbox only, for some >> > obscure reason. >> >> >> Well. Fluxbox displays only what WM_NAME contains. > > Hi Paul, > thanks a lot for your quick and kind reply! :-)
Thanks for the report! :) > >> >> Try starting up the application and let's see what `xprop WM_NAME` >> outputs. It might be a result of the font you're using or it just >> plain being wrong, and other WMs hiding that. > > $ xprop WM_NAME > WM_NAME(COMPOUND_TEXT) = "Debian -- The Universal Operating System" > > Maybe you don't see it in the copied and pasted text, but, if I > redirect the output of the xprop command: > > $ xprop WM_NAME > /tmp/xprop.out > > and open the resulting file with vim, I see the following: > > WM_NAME(COMPOUND_TEXT) = "<202a>Debian -- The Universal Operating System" A take a look at the raw bits gets me: e2 80 aa - which is: UCS-4: 0000202A LEFT-TO-RIGHT EMBEDDING UTF-8: E2 80 AA Interesting... > > And > > $ file /tmp/xprop.out > /tmp/xprop.out: UTF-8 Unicode text My results seem to confirm this > > I am attaching the gzipped version of this file, for completeness. Helped a super ton, thank you :) > > By the way, when I do the same with another browser (Galeon), I see the > following: > > WM_NAME(STRING) = "Debian -- The Universal Operating System" > > Please note: no strange symbols (the file command says "ASCII text") > and STRING rather than COMPOUND_TEXT. > And indeed, I don't see any extraneous question mark in the window > title, when I use Galeon... It must be the case that it does not output the LTR UTF-8 char. Interesting. > >> >> That symbol is not something fluxbox will generate, and I do think >> this bug needs to be assigned back to Midori (since they're the only >> one who sets their name) >> >> Let's see what that output looks like, and if it's just because of a >> font that can't handle that exotic char. > > It really seems that there's an exotic character that isn't correctly > displayed, due to a missing gliph in the fonts, perhaps. This might be something we need to take a look at. Humm. Let me think about this for a second or two. > > > -- > http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt > New GnuPG key, see the transition document! > ..................................................... Francesco Poli . > GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE > Thanks for the report! Paul -- All programmers are playwrights, and all computers are lousy actors. #define sizeof(x) rand() :wq -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
