From: "Clayton Weaver" <cgweav@email.com>
To: linux-kernel@vger.kernel.org
Subject: Re: stty utf8
Date: Fri, 20 Feb 2004 15:57:33 -0500 [thread overview]
Message-ID: <20040220205733.C900F1535E6@ws3-1.us4.outblaze.com> (raw)
[Note: I didn't have legacy hardware terminals in mind.
I was thinking more of a software terminal written from
scratch in utf-8 filesystems world.]
> > Done that way, Jamie's delete example is
> > backspace-space-backspace and remove sizeof(wchar_t)
> > from the input.
> You could store wchar_t in the terminal queue, but what would be the
> point? Removing a UTF-8 character from the input is _trivial_.
> > Ok, it takes more space than operating on the utf-8
> > encoding directly, but otherwise why not?
> Because there's no point.
Ie the convenience of iterating over a fixed size
character encoding in the terminal queue is negated
by other costs (legacy 8-bit filesystem support,
utf-8 control characters, et al)?
(I caught the discussion further down after posting.)
I'm spiritually with the "abort" people on this issue,
any opportunity to stab locale-overloaded character
values and arcane character encodings with shift
states in the heart is not to be passed up. "Every
character in every language has a unique value
everywhere that it is used, or we are not finished
fixing this yet."
But I agree with Linus that it is an admin policy
issue, not a kernel issue.
Thanks for your time,
Clayton Weaver
<mailto: cgweav@email.com>
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
next reply other threads:[~2004-02-20 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 20:57 Clayton Weaver [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 20:19 Markus Kuhn
2004-02-19 18:53 Clayton Weaver
2004-02-20 0:13 ` Jamie Lokier
2004-02-17 22:59 Andries.Brouwer
2004-02-17 23:15 ` Linus Torvalds
[not found] <04Feb13.163954est.41760@gpu.utcc.utoronto.ca>
2004-02-14 23:06 ` JFS default behavior Robin Rosenberg
2004-02-14 23:29 ` viro
2004-02-15 0:07 ` Robin Rosenberg
2004-02-15 2:41 ` Linus Torvalds
2004-02-16 15:05 ` stty utf8 Jamie Lokier
2004-02-16 16:10 ` Gerd Knorr
2004-02-16 22:03 ` Jamie Lokier
2004-02-16 22:17 ` Linus Torvalds
2004-02-16 22:04 ` 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=20040220205733.C900F1535E6@ws3-1.us4.outblaze.com \
--to=cgweav@email.com \
--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®