From: Rob Pike <robpike@gmail.com>
To: Russ Cox <russcox@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] name that character set
Date: Thu, 6 Jan 2005 13:34:41 -0800 [thread overview]
Message-ID: <7359f04905010613347eb09585@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0501061303369c86c7@mail.gmail.com>
We should do a global substitution of 0xFFFD for Runeerror.
0xFFFD is now the standard value representing an encoding
error.
-rob
prev parent reply other threads:[~2005-01-06 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 20:01 Steve Simon
2005-01-06 20:13 ` andrey mirtchovski
2005-01-06 20:41 ` boyd, rounin
2005-01-06 21:03 ` Russ Cox
2005-01-06 21:34 ` Rob Pike [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=7359f04905010613347eb09585@mail.gmail.com \
--to=robpike@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).