Re: UTF-8 in GNOME2 po files
- From: Martin Norbäck <d95mback dtek chalmers se>
- To: Pablo Saratxaga <pablo mandrakesoft com>
- Cc: GNOME i18n list <gnome-i18n gnome org>
- Subject: Re: UTF-8 in GNOME2 po files
- Date: 28 Jan 2002 14:18:25 +0100
mån 2002-01-28 klockan 13.57 skrev Pablo Saratxaga:
> Note also that xterm has a cut and paste bug (at least the version I have),
> it wrongly converts to utf-8: the bytes composing a utf-8 char are each one
> of them converted to utf-8 as if they were latin1 chars.
Was this when cutting and pasting from an xterm from an xterm?
When cutting and pasting from a gnome-terminal in UTF-8 mode to an xterm
in UTF-8 mode, this is indeed the case, and it's not xterm's fault.
gnome-terminal supposedly puts the text in a STRING atom (which should
only be used for ISO-8859-1 strings), and xterm interprets it correctly
(as iso8859-1).
An UTF-8-aware application should use the UTF8_STRING atom when
exporting UTF-8 text.
> > I guess this needs a recent version of vim, but it works quite well for
> > me. I couldn't use unicode fonts in gnome-terminal, dunno why.
>
> You have to set the terminal to utf-8; for that you must echo some value,
> echo -e '\033@8'
>
> or something like that (don't remember the exact value right now)
The escape string to use is <esc>%G
At the moment, don't use gnome-terminal for UTF-8. It's broken, and can
only be used to display UTF-8. UTF-8 input and cut and paste fails in
strange ways.
Regards,
Martin
--
[ http://www.dtek.chalmers.se/~d95mback/ ] [ PGP: 0x453504F1 ] [ UIN:
4439498 ]
Opinions expressed above are mine, and not those of my future
employees.
SIGBORE: Signature boring error, core dumped
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]