Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: tetex 3.0.0-3 format file problem
Date: Thu, 19 May 2005 17:24:38 -0500
Message-ID: <365B741739683A43A84B3AA09C16AA21579FEB@EXCH01.purdue.lcl>
From: "Mcdougall, Robert A." <mcdougar@purdue.edu>
To: <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

From: cygwin-owner@cygwin.com on behalf of Christopher Faylor
[cgf-no-personal-reply-please@cygwin.com]
Sent: Thursday, May 19, 2005 2:59 PM
To: cygwin@cygwin.com
Subject: Re: tetex 3.0.0-3 format file problem [tetex maintainer --
please respond]

> Jan, can you provide any insight here?

Apologies if this is unnecessary, but by way of clarification
to my previous message:

*   teTeX is working fine for me now (I can't of course speak for
    "m. z.".

*   The problems I had been having, as it turned out, were not
    cygwin-specific, but turned on generic teTeX issues (so, I'm
    afraid, the whole thread's OT).

*   The problems, as it turned out, arose from no defect in the
    programs but my local teTeX administration.

Also, by way of correction:  as I should have seen from my own
message 789, the "pdfetex thang" bit me not because of local
configuration files, but because I had an old 'latex.fmt' in my
local tree.

A draft morals list:

*   Once you customize a config file or install stuff in your
    local tree, you own its maintenance forever.

*   In particular, expect breakage between teTeX 2 and teTeX 3.

*   Even more particularly, expect breakage from old versions of
    'texmf.cnf' and '*.fmt'.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/