Re: Thoughts about characters transmission

Andr'e PIRARD <> Tue, 13 July 1993 11:07 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa01303; 13 Jul 93 7:07 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id ac01279; 13 Jul 93 7:07 EDT
Received: from by CNRI.Reston.VA.US id aa01003; 13 Jul 93 5:04 EDT
Received: by (5.59/SMI4.0/RU1.5/3.08) id AA13445; Tue, 13 Jul 93 04:32:32 EDT
Received: from by (5.59/SMI4.0/RU1.5/3.08) id AA13426; Tue, 13 Jul 93 04:32:25 EDT
Message-Id: <>
Received: from BLIULG11 by (IBM VM SMTP V2R2) with BSMTP id 5196; Tue, 13 Jul 93 10:31:29 +0200
Received: from BLIULG11 (PIRARD) by BLIULG11 (Mailer R2.10 ptf000) with BSMTP id 0501; Tue, 13 Jul 93 10:31:28 +0200
Date: Tue, 13 Jul 93 10:22:42 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andr'e PIRARD <>
Organization: University of Liege (Belgium), SEGI (Computing Center)
Subject: Re: Thoughts about characters transmission
To: Masataka Ohta <>, Multi-byte Code Issues <ISO10646@JHUVM>
Cc:,,, ietf@CNRI.Reston.VA.US,
In-Reply-To: Message of Mon, 12 Jul 93 0:49:59 JST from <>

On Mon, 12 Jul 93 0:49:59 JST you said:
>The problem is that, from the view point outside of Europe and US, ISO
>10646 is merely a poor extension to ISO 8859-1.
>It assignes a single code point to different but similar characters
>in Japan and China.

I thought that this was the problem of Unicode and not of ISO 10646.

>So, please don't say "international" when what you mean is merely

At least the voting is, isn't it.
Note that some even go for the bet of calling such a code "universal" :-)