Received: by nummer-3.proteosys id <01C19443.A84D3F74@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:45 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.A84D3F74" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: patching the pool file Date: Sun, 26 Apr 1992 19:48:39 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Dominik Wujastyk" Sender: "Mailing list for the LaTeX3 project" To: "Rainer M. Schoepf" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 684 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.A84D3F74 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable \begin{quotation} > So one solution to the extension problem (i.e. making .ltx the = default > extension) would be a separate pool file for ltx3. Such a pool file > could be automatically generated from an existing one if necessary. = To > install ltx3 it would then be necessary to use the ltx3 pool file > instead of the usual one. This could be achieved by renaming the pool > file for format generation. \end{quotation} Once, a long time ago, I did do exactly this with sbTeX's tex.poo file. I just did a search-and-replace for the string ".tex" and changed it to ".ltx", and got exactly the result I wanted, with no apparent problems at all. I reverted to normal usage, however, since I was reluctant to use a non-standard TeX. However, I never experimented with help messages etc. It never occured to me, though, that such a change could be done by a macro at the time of LaTeX format installation. Very interesting idea. I think that meddling with the pool file *is* something that could indeed be seriously beneficial, but of course one has to weigh up the pros and cons very carefully. Does this impinge on things like the trip test? I assume the trip test only applies to TeX+plain. What is the actual status of tex.pool. Is it considered an integral part of tex.the.program, which -- if changed -- would make TeX a different program? Changing tex.pool with clever macros might be dangerously system-specific. On the other hand, the fact that it is done using tex's input/output might make it system-free(er). Dominik ------_=_NextPart_001_01C19443.A84D3F74 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: patching the pool file

\begin{quotation}
 > So one solution to the extension problem = (i.e. making .ltx the default
 > extension) would be a separate pool file = for ltx3. Such a pool file
 > could be automatically generated from an = existing one if necessary. To
 > install ltx3 it would then be necessary to = use the ltx3 pool file
 > instead of the usual one. This could be = achieved by renaming the pool
 > file for format generation.
\end{quotation}

Once, a long time ago, I did do exactly this with = sbTeX's tex.poo
file.  I just did a search-and-replace for the = string ".tex" and
changed it to ".ltx", and got exactly the = result I wanted, with
no apparent problems at all.  I reverted to = normal usage, however,
since I was reluctant to use a non-standard = TeX.  However, I
never experimented with help messages etc.

It never occured to me, though, that such a change = could be done
by a macro at the time of LaTeX format = installation.  Very interesting
idea.

I think that meddling with the pool file *is* = something that
could indeed be seriously beneficial, but of course = one has to weigh up
the pros and cons very carefully.  Does this = impinge on things
like the trip test?   I assume the trip = test only applies to
TeX+plain.  What is the actual status of = tex.pool.  Is it considered
an integral part of tex.the.program, which -- if = changed --
would make TeX a different program?  Changing = tex.pool with clever
macros might be dangerously system-specific.  On = the other hand,
the fact that it is done using tex's input/output = might make it
system-free(er).

Dominik



------_=_NextPart_001_01C19443.A84D3F74--