Ionel Mugurel =?iso-8859-2?Q?Ciob=EEc=E3?= <tgakic_at_sg10.chem.tue.nl> writes:
> Īn data de 13/09/2001, 18:45:48, Dan Espen a scris:
> >
> > I'm not sure if I'd say xterm is doing something wrong.
> > I don't know if it needs to mark that string as a complex
> > string to display right. I suspect that it doesn't.
>
> Where I can read about this "complex string"? I try to add
> a "\" in front of the 8bit letter, also a (Ctrl-V), is not
> working.
>
> man -k "complex string" give no answer and in man xterm I
> can't find complex string either.
I don't think you can backslash the problem away.
When an application creates one of these titles fvwm displays
it correctly when it uses XmbDrawString to display
the string and displays it incorrectly when it uses just plain
XDrawString. Somewhere in the man pages, I got the term
complex string for the difference.
I'm trying to figure out what makes xterm think it needs to
put out that sequence...
Ah, now I see your next mail.
> So, the script running from the fvwm menu is in fact running
> with LANG=C. Well that is strange, because C means ASCII, 7bit
> and shouldn't work. If I change LANG=C in a xterm and I run
> the script I get a xterm where the name has no strange characters,
> and all 8bit characters can be typed. If now I add
> export LANG=C and/or setenv LANG C in my script then it is not
> working.
...
> Still, why LANG=C is OK for 8bit characters, and LANG=ro_RO
> (or any other) it is not?
When in locale C, X works fine with 8 bit characters.
That strange stuff at the beginning of the tltle
comes from xterm deciding it needs to use multibyte.
I don't know why xterm is deciding that it needs multibyte,
it shouldn't need more than 8 bits even for Russian.
> I should manage now to make it work, thank you.
Good, because I'm beginning to suspect I don't know
what I'm writing about.
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Sep 13 2001 - 19:51:41 BST