From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces, separators, and utf-8
Date: Wed, 5 Jun 2002 10:03:43 +0000 [thread overview]
Message-ID: <3CF9E097.9FD638F8@null.net> (raw)
In-Reply-To: <a1be82d961ea80f8143d35f570a84ab0@collyer.net>
Geoff Collyer wrote:
> Michael may only be arguing for admitting the space character in file
> names, but I believe that others will go farther once space is
> admitted, having witnessed various wheels of reincarnation in the
> past. ...
I don't think it's so much a matter of admitting certain characters
as it is of disallowing certain characters. There should be good
reason for disallowal.
> Has anybody figured out how (or if) to cope with Unicode 3? They've
> broken their promise to stick to 16 bits, which UTF-8 can cope with,
> if we crank up UTFmax. Is switching to 32-bit runes only a minor
> performance hit?
"I told you so."
next prev parent reply other threads:[~2002-06-05 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 23:01 Geoff Collyer
2002-06-05 10:03 ` Douglas A. Gwyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-01 14:59 [9fans] lures Lucio De Re
2002-06-01 17:54 ` [9fans] spaces, separators, and utf-8 Michael Baldwin
2002-06-01 18:21 ` Scott Schwartz
2002-06-01 22:00 ` Dan Cross
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=3CF9E097.9FD638F8@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).