-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wang, Roger wrote (way back in April):
> Hi Michael,
>
> I used the attached patch so the utf8 hardstatus would display
> correctly in my xterm titlebar. Is it ok or how could I improve it?
Hi Roger, sorry this response is so long past your original
Hi Michael,
I used the attached patch so the utf8 hardstatus would display
correctly in my xterm titlebar. Is it ok or how could I improve it?
Thanks in advance.
Roger
On Mon, Apr 23, 2007 at 08:28:17PM +0200, Michael Schroeder wrote:
> On Wed, Mar 28, 2007 at 12:04:09PM +0200, Zvi Har'El wrote
On Wed, Mar 28, 2007 at 12:04:09PM +0200, Zvi Har'El wrote:
> Comparing Unicode, it replaces U+03B1 GREEK SMALL LETTER ALPHA with
> U+00B1 PLUS-MINUS SIGN and so on, i.e, the Unicode values seem to be
> taken modulo U+0100.
Yes, it's because StringChar() in ansi.c discards the upper bits.
To fix
I am trying to investigate this bug, since I am sure it is. One thing I
already noticed that the way the functions void AddStr(char *str)
(display.c:3513) and void AddStrn(char *str, int n) (display.c:3533)
call the funcion void AddUtf8(int c) (encoding.c:638) is errenous. The
latter is called on
I think this question has been asked before, even though I don't
remember whether it was answered. Maybe it was even you who asked
before. If so, I hope this time somebody can help you (I cannot).
Otherwise, maybe an archive search helps.
Regards
--
Alexander Kriegisch
__
Hi,
I am using Screen in a en_US.UTF-8 locale, inside an xterm. I am using
the xterm standard escape sequence to set the window title. I have a
the following problem: There is no problem with the Basic Latin (ASCII)
characters (Unicode < 0+007F), but also with Latin1 Supplement
characters (U+008
Dear Screen gurus,
I am using Screen in a en_US.UTF-8 locale, inside an xterm. I am using
the xterm standard escape sequence to set the window title. I have a
the following problem: There is no problem with the Ascii characters
(Unicode < 0+007F), which are represented by one byte in UTF-8, but
