From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>
Cc: "Jamie Lokier" <jamie@shareable.org>, <linux-kernel@vger.kernel.org>
Subject: Re: UTF-8 filenames
Date: Mon, 23 Feb 2004 20:34:57 +0900 [thread overview]
Message-ID: <015d01c3fa01$32c15c30$34ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 200402230710.12549.robin.rosenberg.lists@dewire.com
Robin Rosenberg replied to me:
> > Of course. Perhaps my use of reductio al absurdum was unclear.
Actually Mark Hahn got me on that, it should be ad, but I get too many ads
already. Now reminiscing about the days before I posted to LKML, because my
inbox was less than 75% spams in those days.
> > I was trying to show that UTF-8, despite its sanity, is not universally
> > agreeable. The actual reason is because it came late to the scene
> > (around 20 years ago) and it is not backwards compatible.
>
> Even later, it's from 1992 I believe
Oh, then it was even later to the scene than I thought.
> and a standard even later. That is long after we went from national
> variants of ASCII to ISO-Latin-1. If I recall it correctly it was the
> years around 1987 that we started having multiple encodings fo text.
SJIS and EUC both existed before 1987.
next prev parent reply other threads:[~2004-02-23 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 12:30 UTF-8 filenames Norman Diamond
2004-02-22 20:45 ` Jamie Lokier
2004-02-22 23:35 ` Norman Diamond
2004-02-23 6:10 ` Robin Rosenberg
2004-02-23 11:34 ` Norman Diamond [this message]
2004-02-23 12:15 ` Robin Rosenberg
2004-02-23 12:00 ` Jamie Lokier
2004-02-23 23:42 ` Norman Diamond
2004-02-24 0:02 ` Jamie Lokier
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='015d01c3fa01$32c15c30$34ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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