From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Jamie Lokier" <jamie@shareable.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: UTF-8 filenames
Date: Mon, 23 Feb 2004 08:35:19 +0900 [thread overview]
Message-ID: <008d01c3f99c$9033e3c0$34ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: <20040222204541.GA26793@mail.shareable.org>
Jamie Lokier replied to me:
> > Consider
> > converting all your ASCII filenames to UTF-16. Let everyone share the
> > short-term pain for the long-term gain. When you get everyone to agree on
> > UTF-16, it will be ugly, but it will be equal for everyone.
>
> UTF-8 is the only sane universal encoding in unix.
That's a bit beside the point. I was replying to the assertion that
everyone agreed to use UTF-8. (And particularly, for large character sets.)
> UTF-16 is not an option;
Of course. Perhaps my use of reductio al absurdum was unclear. I was
trying to show that UTF-8, despite its sanity, is not universally agreeable.
The actual reason is because it came late to the scene (around 20 years ago)
and it is not backwards compatible. But to make the point, I compared it
with UTF-16 which is equally not universally agreeable.
> it's not POSIX compatible,
OK, UTF-8 has one less reason than UTF-16 has, for being not universally
agreeable. But the biggest reason still remains, as mentioned above.
> > By the way, another subthread mentioned that stty puts some stuff in the
> > kernel that could be done in user space. In Unix systems the same is true
> > for IMEs, stty options specify the encoding of the output of an IME (e.g.
> > EUC-JP or SJIS, which then gets forwarded as input to shells, applications,
> > etc.), and whether a single backspace (or whatever character deletion
> > character) deletes an entire input character instead of just deleting a
> > single byte, etc. I keep forgetting to see if Linux has the same stty
> > options. I haven't needed to set them with stty because if I need to use a
> > different locale then I just open a new terminal emulator window using that
> > locale.
>
> Do you have a list or description of the specific stty options that
> are used?
Well, I thought I described them as I saw them used in Unix. I no longer
have access to machines running commercial Unix systems, but some of the
stty options were the way I did describe. I have a feeling that System V
might have implemented them slightly differently from BSD-based systems, but
regardless, the same functionality was pretty much "universally" needed and
implemented.
If you're asking whether I noticed similar stty options in Linux, I didn't
notice because of the reason mentioned (I just opened another terminal
emulator window using the locale that I temporarily needed). But I'll try
to remember to look next weekend. Sorry, I'm leaving for work in a minute
and can't look now.
next prev parent reply other threads:[~2004-02-22 23:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 12:30 Norman Diamond
2004-02-22 20:45 ` Jamie Lokier
2004-02-22 23:35 ` Norman Diamond [this message]
2004-02-23 6:10 ` Robin Rosenberg
2004-02-23 11:34 ` Norman Diamond
2004-02-23 12:15 ` Robin Rosenberg
2004-02-23 12:00 ` Jamie Lokier
2004-02-23 23:42 ` Norman Diamond
2004-02-24 0:02 ` Jamie Lokier
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='008d01c3f99c$9033e3c0$34ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=jamie@shareable.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®