Received: by nummer-3.proteosys id <01C19443.A888D8FC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:45 +0100 In-Reply-To: <9204261716.AA08063@nnsa> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.A888D8FC" Return-Path: X-MimeOLE: Produced By Microsoft Exchange V6.5 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]) Content-class: urn:content-classes:message Subject: Re: patching the pool file Date: Mon, 27 Apr 1992 11:12:57 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Dave Love" 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: 690 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.A888D8FC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Isn't it true that web2c doesn't use the pool file? I just ran latex OK with a web2c TeX after moving it. ------_=_NextPart_001_01C19443.A888D8FC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: patching the pool file

Isn't it true that web2c doesn't use the pool = file?  I just ran latex
OK with a web2c TeX after moving it.

------_=_NextPart_001_01C19443.A888D8FC--