Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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 14:03:41 -0500
Message-ID: <365B741739683A43A84B3AA09C16AA21579FEA@EXCH01.purdue.lcl>
From: "Mcdougall, Robert A." <mcdougar AT purdue DOT edu>
To: <cygwin AT cygwin DOT com>
X-OriginalArrivalTime: 19 May 2005 19:02:50.0639 (UTC) FILETIME=[5A6D29F0:01C55CA5]
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j4JJSlwb018068

"m. z." <mzap80AThotmailDOTcom> wrote:

BTAM, the wizards will not reply to such naive questions as
yours or mine.  FWIW, here's what I've found out:

> Why doing "latex" is invoking now pdf format ?

According to the teTeX manual ('doc/tetex/TETEXDOC.{dvi,pdf,ps}'),
section 4.6, "pdfetex: the new default TEX engine":

    teTEX uses pdfetex for all formats except ``good-old'' tex.
    So, if you run latex, the underlying engine will be pdfetex.

> In the mail below, I see that still with version 3.0.0-3, which
> still I have not installed because I failed both with 3.0.0-1
> and 3.0.0-2, when one is doing "latex filename.tex", in the line
> below the output is "pdfeTeX..." With the previous version of
> tetex (2.something) this was not happening.  Is this the source
> of the problems with tetex 3.0.0-x ?

Perhaps not.  Or if it is, it may not be an insuperable
obstacle.  My problems with teTeX 3 so far seem to relate to
outdated configuration files; local configuration files left
around from teTeX 2 are liable to break teTeX 3.  For example:

*   If you have an old customized 'web2c/texmf.cnf', even in the
    main TEXMF tree, the installer may not overwrite it, and the old
    file will break teTeX 3.  This is because the path configuration
    rules have changed significantly from teTeX 2.

*   Configuration files in local TEXMF trees may also break the new
    teTeX, perhaps for reasons related to the pdfetex thang (also
    new to teTeX 3).  Anyhow, cleaning out the old config files got
    LaTeX working again for me; YMMV.

--
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/