IETF Logo Mail Archive

Re: Revision of RFC 1494 - Teletex mapping?

Christian Huitema <Christian.Huitema@sophia.inria.fr> Wed, 11 January 1995 15:23 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03738; 11 Jan 95 10:23 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03733; 11 Jan 95 10:23 EST
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa07862; 11 Jan 95 10:23 EST
Received: from mitsou.inria.fr by survis.surfnet.nl with SMTP (PP); Wed, 11 Jan 1995 15:55:14 +0100
Received: by mitsou.inria.fr (5.65c8/IDA-1.2.8) id AA19437; Wed, 11 Jan 1995 15:54:32 +0100
Message-Id: <199501111454.AA19437@mitsou.inria.fr>
To: Harald.T.Alvestrand@uninett.no
Cc: mime-mhs@surfnet.nl
Subject: Re: Revision of RFC 1494 - Teletex mapping?
In-Reply-To: Your message of "Wed, 11 Jan 1995 09:20:59 +0100." <199501110821.JAA05926@dale.uninett.no>
Date: Wed, 11 Jan 1995 15:54:30 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Christian Huitema <Christian.Huitema@sophia.inria.fr>

Harald,

The problem you mention vs. T.61 "sequence of pages" is real. In fact, I do
not care very much of the T.61 char set itself. I have yet to find someone who
uses it "naturally." I remember studying the problem and arguing strongly that
what should never convert anything into T.61. I would very much prefer a
translation from T.61 to the T.61 charset, because there is not one single 8
bits alphabet that captures the 500 and some characters defined in T.61. But if
you really feel a need to do it, you can as well convert T.61 to
text/plain/unicode; it will not prevent me from sleeping...

Christian Huitema

v2.23.0 | Report a Bug | By Email