From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs un-removable file
Date: Mon, 27 Oct 2003 11:06:18 -0500 [thread overview]
Message-ID: <20031027160618.14972.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: <3ff7aff7e446ebd1fe0a788c93d5d844@vitanuova.com>
| invalid utf sequences, aren't there several possible
| utf sequences that can validly map to the same character?
I think only the shortest such sequence is supposed to be allowed, so
maybe calling it an error is better than canonicalizing. On the other
hand, Tcl uses a multibyte encoding of \0 to handle embedded nuls.
That seems like a useful hack.
prev parent reply other threads:[~2003-10-27 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 13:07 steve-simon
2003-10-27 13:35 ` Russ Cox
2003-10-27 15:15 ` C H Forsyth
2003-10-27 16:15 ` ron minnich
2003-10-27 16:02 ` rog
2003-10-27 16:06 ` Scott Schwartz [this message]
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=20031027160618.14972.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--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).