Received: by nummer-3.proteosys id <01C19443.499CF7A4@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:06 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil t 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.499CF7A4" 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: "Don Hosek" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 410 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.499CF7A4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Regarding loading additional hyphenation patterns: don't change hyphen.tex--not even to rename it. Instead, just load in a file which loads all your extra patterns after TeX has completed its basic loads. This file could look something like: \global\chardef\english=3D0 \newlanguage\french \language\french \input frhyph.tex \everyjob=3D\expandafter{\the\everyjob \typeout{Includes French patterns}} [all other languages loaded similarly] \language\english % I think that it's safe for users to assume % that the default language is English --end of file-- Now as regards modifying TeX to handle various different encodings, let me just say NO, DON'T DO IT! The sort of change which occurs in emTeX makes it non-TeX. (Incidentally, probably the most thought-out extension of this sort is the new mlTeX with its \charsubdef). 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. I think that there is something to be said for the development of a deuteroTeX, but it's very important to not get this confused with the development of TeX itself. Making a change like the \charsubdef is doubtless useful, but it also violates the terms of the copyright on the TeX program and trademark on the TeX name. -dh ------_=_NextPart_001_01C19443.499CF7A4 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX 2.09 <Oct 91> beta-test

Regarding loading additional hyphenation patterns: = don't change
hyphen.tex--not even to rename it. Instead, just load = in a file
which loads all your extra patterns after TeX has = completed its
basic loads. This file could look something = like:

\global\chardef\english=3D0

\newlanguage\french
\language\french
\input frhyph.tex
\everyjob=3D\expandafter{\the\everyjob
   \typeout{Includes French = patterns}}

[all other languages loaded similarly]

\language\english % I think that it's safe for users = to assume
          &nbs= p;       % that the default language is = English

--end of file--

Now as regards modifying TeX to handle various = different
encodings, let me just say NO, DON'T DO IT! The sort = of change
which occurs in emTeX makes it non-TeX. = (Incidentally, probably
the most thought-out extension of this sort is the = new mlTeX with
its \charsubdef). 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.

I think that there is something to be said for the = development of
a deuteroTeX, but it's very important to not get this = confused
with the development of TeX itself. Making a change = like the
\charsubdef is doubtless useful, but it also violates = the terms
of the copyright on the TeX program and trademark on = the TeX
name.

-dh


------_=_NextPart_001_01C19443.499CF7A4--