From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] UTF-8 handling in non-plan9 app: help finding bug
Date: Tue, 25 Mar 2003 18:14:30 +0100 [thread overview]
Message-ID: <3E808E76.4000008@strakt.com> (raw)
In-Reply-To: <20030325170507.GA2127@castor>
Jack Johnson wrote:
>If it's unrepresentable, why not just do:
>
> cmh@nic.or.kr
>
>
Loss of data is a bad idea. You should try and hang onto it somehow.
next prev parent reply other threads:[~2003-03-25 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 5:47 [9fans] output of ps(1) memory usage YAMANASHI Takeshi
2003-02-21 5:55 ` Russ Cox
2003-02-21 6:08 ` [9fans] alg to make a good colour palette for a graph George Michaelson
2003-02-21 6:39 ` Eric Grosse
2003-02-21 6:57 ` George Michaelson
2003-02-21 7:46 ` Skip Tavakkolian
2003-02-21 12:56 ` [9fans] " Jim Choate
2003-03-24 1:48 ` [9fans] UTF-8 handling in non-plan9 app: help finding bug George Michaelson
2003-03-24 2:31 ` Russ Cox
2003-03-24 3:01 ` David Presotto
2003-03-25 16:15 ` Boyd Roberts
2003-03-25 17:04 ` Russ Cox
2003-03-25 17:13 ` Boyd Roberts
2003-03-25 17:05 ` Jack Johnson
2003-03-25 17:14 ` Boyd Roberts [this message]
2003-03-25 22:55 ` George Michaelson
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=3E808E76.4000008@strakt.com \
--to=boyd@strakt.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).