From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 wiki experiment
Date: Thu, 1 Feb 2001 23:55:43 -0500 [thread overview]
Message-ID: <200102020455.XAA26955@smtp3.fas.harvard.edu> (raw)
I just fixed that, a minute ago.
I was dutifully using isspace() rather than
reinvent the wheel, and isspace() didn't work
on UTF bytes (with the high-bit set, it thought
they were negative).
So the return value on bytes in UTF sequences
was mostly bogus. Retype the UTF, it should
stay this time.
Russ
next reply other threads:[~2001-02-02 4:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 4:55 rsc [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 13:51 nemo
2001-02-02 8:12 okamoto
2001-02-02 5:05 rsc
2001-02-02 4:56 rob pike
2001-02-02 4:49 okamoto
2001-02-02 2:24 okamoto
2001-02-01 12:20 nigel
2001-02-05 6:07 ` Dan Cross
2001-02-01 4:28 okamoto
2001-02-01 3:01 okamoto
2001-01-31 18:06 nemo
2001-01-31 11:57 Russ Cox
2001-02-01 4:03 ` Dan Cross
2001-01-31 11:27 Russ Cox
2001-02-01 8:08 ` Quinn Dunkan
2001-02-01 8:01 ` Dan Cross
[not found] ` <cross@math.psu.edu>
2001-02-01 19:38 ` Tom Duff
2001-02-05 18:55 ` 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=200102020455.XAA26955@smtp3.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--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).