Received: by nummer-3.proteosys id <01C19443.49FBB734@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:06 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil nil nil nil t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.49FBB734" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: LaTeX 2.09 beta-test Date: Tue, 22 Oct 1991 01:00:00 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Jan Michael Rynning" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 407 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.49FBB734 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Don Hosek writes: > ... Modifying xchar/xord so that say, the PC > e-acute maps internally to the Cork e-acute causes the difficulty > that TeX files created under this assumption are non-portable. > The purpose of xchar/xord was not for this sort of remapping, but > rather to handle the differences between ASCII and EBCDIC. The > best pure TeX way to handle code pages is to make chars over 127 > active, but as was mentioned this disallows their use in cs > names. When I proposed to Don Knuth, two years ago, that all characters >127 should be made active and that we should use TeX macro definitions for doing the character set remapping, he said he thought it was better to use xchr/xord for that purpose. After all, they are system dependent, and you should set them up to suit the character set you are using. Jan Michael Rynning Department of Numerical Analysis Internet: jmr@nada.kth.se and Computing Science UUCP: {uunet,...}!nada.kth.se!jmr Royal Institute of Technology BITNET: jmr@sekth S-100 44 Stockholm Voice: +46-8-7906288 Sweden Fax: +46-8-7900930 ------_=_NextPart_001_01C19443.49FBB734 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX 2.09 <Oct 91> beta-test

Don Hosek writes:
> ... Modifying xchar/xord so that say, the = PC
> e-acute maps internally to the Cork e-acute = causes the difficulty
> that TeX files created under this assumption are = non-portable.
> The purpose of xchar/xord was not for this sort = of remapping, but
> rather to handle the differences between ASCII = and EBCDIC. The
> best pure TeX way to handle code pages is to = make chars over 127
> active, but as was mentioned this disallows = their use in cs
> names.

When I proposed to Don Knuth, two years ago, that all = characters >127
should be made active and that we should use TeX = macro definitions for
doing the character set remapping, he said he thought = it was better to
use xchr/xord for that purpose.  After all, they = are system dependent,
and you should set them up to suit the character set = you are using.

Jan Michael Rynning
Department of Numerical = Analysis        Internet: = jmr@nada.kth.se
  and Computing Science =         =         UUCP: = {uunet,...}!nada.kth.se!jmr
Royal Institute of Technology   =         BITNET: jmr@sekth
S-100 44 Stockholm      =         =         Voice: +46-8-7906288
Sweden  =         =         =         =         Fax: +46-8-7900930


------_=_NextPart_001_01C19443.49FBB734--