Re: Thoughts about characters transmission

Jim Conklin <> Fri, 16 July 1993 13:59 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa01917; 16 Jul 93 9:59 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01909; 16 Jul 93 9:59 EDT
Received: from by CNRI.Reston.VA.US id aa08134; 16 Jul 93 9:59 EDT
Received: by (5.59/SMI4.0/RU1.5/3.08) id AA24266; Fri, 16 Jul 93 09:39:47 EDT
Received: from by (5.59/SMI4.0/RU1.5/3.08) id AA24262; Fri, 16 Jul 93 09:39:40 EDT
Received: from by (5.64/A/UX-3.00) id AA15691; Fri, 16 Jul 93 09:42:04 EDT
Message-Id: <>
Date: Fri, 16 Jul 1993 09:39:31 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jim Conklin <>
Subject: Re: Thoughts about characters transmission

Masataka Ohta  reminds us that:

>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.
>So, please don't say "international" when what you mean is merely

  I think it's terribly important that we keep this in mind as we develop
standards for the future, and design, insofar as it's possible to doso, for
the long-range goal of a truly international -- not just intereuropean --
network, though it will probably be necessary to miss that goal for
pragmatic, interim solutions for a while, just to keep moving on some of
the issues for which there are no clear solutions.

  I must confess that I like Rick Troth's idea in this context, though I
certainly don't understand its practical implications yet:
>  ...    I say we scrap the 16-bit
>stop-gap solution and go directly to 32-bit and then start looking
>toward bit-unconstrained (bit-free?) representations.