From: Jamie Lokier <jamie@shareable.org>
To: jw schultz <jw@pegasys.ws>, linux-kernel@vger.kernel.org
Subject: Re: JFS default behavior
Date: Tue, 17 Feb 2004 21:37:14 +0000 [thread overview]
Message-ID: <20040217213714.GI24311@mail.shareable.org> (raw)
In-Reply-To: <20040217064755.GC9466@pegasys.ws>
jw schultz wrote:
> Your concrete example is a good one. Where did that
> filename come from? It would seem to have come from the
> keyboard via a tty (or simulator) which also had to display
> it. I'd say this is an argument for the terminal to display
> UTF-8 and convert intput into UTF-8. That is something that
> seems to be not consistantly done as yet. Ultimately it
> seems to be a responsiblity of the user interface, whether
> tty or GUI. Until that happens the shells might be able to
> fill the gap, however poorly.
Many terminals will not ever display UTF-8. Think: all the serial terminals.
This is why I think "stty utf8" or something along those lines would
be useful. The terminal itself doesn't have to talk UTF-8; however,
the applications talking with /dev/tty would always see UTF-8.
That seems to solve most of the practical user interface problems of
the command line, in one single clean place.
-- Jamie
next prev parent reply other threads:[~2004-02-17 21:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 23:03 JFS default behavior Nicolas Mailhot
2004-02-16 3:45 ` Jan Knutar
2004-02-16 8:30 ` Nicolas Mailhot
2004-02-16 8:54 ` Valdis.Kletnieks
2004-02-16 6:21 ` jw schultz
2004-02-16 15:55 ` Jamie Lokier
2004-02-17 6:47 ` jw schultz
2004-02-17 21:37 ` Jamie Lokier [this message]
2004-02-17 22:12 ` Linus Torvalds
2004-02-18 9:59 ` Jamie Lokier
2004-02-18 15:54 ` Linus Torvalds
2004-02-18 23:58 ` Jamie Lokier
2004-02-19 10:59 ` JFS default behavior / UTF-8 filenames kernel
2004-02-19 14:05 ` Dave Kleikamp
2004-02-19 23:47 ` kernel
2004-02-20 15:00 ` Dave Kleikamp
2004-02-22 19:22 ` kernel
2004-02-24 14:44 ` Dave Kleikamp
[not found] <1pvUz-6j-1@gated-at.bofh.it>
[not found] ` <1pRVj-2am-29@gated-at.bofh.it>
2004-02-16 15:32 ` JFS default behavior Pascal Schmidt
2004-02-16 19:05 ` Eduard Bloch
-- strict thread matches above, loose matches on Subject: below --
2004-02-15 14:48 Pascal Schmidt
2004-02-16 14:24 ` Eduard Bloch
[not found] <04Feb13.163954est.41760@gpu.utcc.utoronto.ca>
2004-02-14 14:27 ` Nicolas Mailhot
2004-02-14 15:40 ` viro
2004-02-14 17:47 ` Nicolas Mailhot
2004-02-14 17:59 ` Nicolas Mailhot
2004-02-14 23:06 ` Robin Rosenberg
2004-02-14 23:29 ` viro
2004-02-15 0:07 ` Robin Rosenberg
2004-02-15 2:41 ` Linus Torvalds
2004-02-15 3:33 ` Matthias Urlichs
2004-02-15 4:04 ` viro
2004-02-15 9:48 ` Robin Rosenberg
2004-02-15 18:26 ` yodaiken
2004-02-12 16:50 JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.) Nicolas Mailhot
2004-02-13 3:03 ` Jamie Lokier
2004-02-13 18:06 ` Nicolas Mailhot
2004-02-13 18:15 ` viro
2004-02-13 18:31 ` Richard B. Johnson
2004-02-13 18:50 ` JFS default behavior Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040217213714.GI24311@mail.shareable.org \
--to=jamie@shareable.org \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.