From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] recent changes on sources
Date: Sun, 15 May 2005 05:11:32 +0200 [thread overview]
Message-ID: <072901c558fb$cc7459e0$aafb7d50@kilgore> (raw)
In-Reply-To: <ca281ff8355333aeff18b6a1ac672c76@plan9.bell-labs.com>
> 2. <libc.h> now defines Runeerror as 0xFFFD, the new official
> Unicode error value. We used to use 0x80, but the rest of the
> world standardized on 0xFFFD.
i know i've posted this before, but it's just a simple filter
to debug rune encoding woe:
http://www.insultant.net/code/plan9/vr.c
--
MGRS 31U DQ 52572 12604
prev parent reply other threads:[~2005-05-15 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 19:05 9trouble
2005-05-15 3:11 ` boyd, rounin [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='072901c558fb$cc7459e0$aafb7d50@kilgore' \
--to=boyd@insultant.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).