I'm sure it gives you a hardon to bash Linux, but
you're being intellectually dishonest.
For openers, sexual references are inappropriate. This is a
list of professionals, and it ill behoves you to not treat
us that way.
Secondly, I was in *NO WAY* bashing Linux. I am a HUGE fan
of open source
Juliusz Chroboczek [EMAIL PROTECTED] さんは書きました:
And, yes, of course xterm should start up in utf-8 mode if the locale
encoding is UTF-8.
MH Thanks, that was my original conclusion also. I had just
MH wondered why it doesn't. Just an xterm bug I guess.
On Fri, 2003-02-21 at 12:47, Kean Johnston wrote:
There's a libcharset that I think comes with libiconv and
is also used in GLib that you can use to work around this problem.
Which is fine if you use GNU iconv. For those of us that use
the iconv as it was originally invented, libcharset
Thomas Zander [EMAIL PROTECTED] writes:
You can specify en_US.UTF-8 as your locale. Which implies to me that
xterm can recognize, from its environment, the encoding, and act
accordingly.
Hope you aren't using the locale standard 'Variation' variable for
that; in most europe countries
.
And exactly thats why xterm should come up in utf-8 mode in UTF-8
locales.
* If your xterm runs in non-utf8 mode and your locale is de_DE both
xterm and your terminal apps use iso-8859-1 and everything is fine.
* If your xterm runs in utf8 mode and your locale use de_DE.UTF-8
both xterm
On Thu, 20 Feb 2003, Thomas E. Dickey wrote:
Would it be sensible and acceptable to have xterm default to
using the encoding of the user's locale at startup? Seems to be
only if you happen to be running redhat 8.x
I'd like to know what problems are caused by autodetecting the
user's
On Thu, Feb 20, 2003 at 06:32:56PM +0100, Gerd Knorr wrote:
Thomas Zander [EMAIL PROTECTED] writes:
Conclusion;
An xterm should be able to display chinese if man or ls outputs that,
That works just fine if xterm and applications use the same charset.
And exactly thats why xterm should
On Thu, Feb 20, 2003 at 10:30:43PM +0100, Thomas Zander wrote:
Whatever the solution its a bug in ssh, not X.
I have the opinion that forwarding does not solve all problems (since one of
the machines may not know about utf8) so ssh could better convert the data
stream using the different
And, yes, of course xterm should start up in utf-8 mode if the locale
encoding is UTF-8.
MH Thanks, that was my original conclusion also. I had just
MH wondered why it doesn't. Just an xterm bug I guess.
*locale: true
(Credit to Tomohiro Kubota.)
JG Though I disagree that ssh should not transmit the current locale: it
JG _should_, precisely because it could be different coming from Solaris,
JG or Debian, or Windows, and you want to make sure both sides agree on
JG the encoding. Of course, this also assumes that there is some suitable
JG
On Thu, Feb 20, 2003 at 01:50:40PM -0800, Kean Johnston wrote:
You can specify en_US.UTF-8 as your locale. Which implies
to me that xterm can recognize, from its environment, the
encoding, and act accordingly.
Which only encourages the sort of bugs that many an autoconf
script has had,
On Wed, Feb 19, 2003 at 08:53:14PM +0100, Thomas Zander wrote:
I've heard the same discussion on KDE lists. And as on KDE the point
is that the whole system has to be utf-8 to work correctly.
Close -- the way Red Hat 8 is set up, it seems like the whole world
needs to be UTF8 :/
This is an
On Wed, Feb 19, 2003 at 03:48:02PM -0500, Jeff Garzik wrote:
On Wed, Feb 19, 2003 at 08:53:14PM +0100, Thomas Zander wrote:
Its news to me that a locale can specify that its utf-8, since I always
thought that locales don't define encodings.
It's news, then :)
You can specify en_US.UTF-8
13 matches
Mail list logo
