Received: by nummer-3.proteosys id <01C19443.999C5A1C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:20 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.999C5A1C" 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: What exactly is a LaTeX format? (Re: Validating LaTeX output) Date: Fri, 31 Jan 1992 13:19:43 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Dave Love" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 566 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.999C5A1C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm somewhat confused by suggestions to diff dvi files etc., at least done by other than the Keepers of LaTeX, given that we're all free to load our own set of fonts at least. Wouldn't it be helpful first to define what a format can/can't contain to be considered LaTeX; for instance does mine (I don't think it's alone) qualify with array.sty and verbatim.sty loaded, and what if I had British hyphenation patterns? Apart from local validation it would presumably help with defining the conditions under which bug reports should (not) be made. Sorry if that's been spelt out before but I don't recall seeing it anywhere. I'd at least like to see a few canonical files that set out to exercise as wide a range of LaTeX features as possible (their mutual exclusion) to provide an easy visual check on style hacks. ------_=_NextPart_001_01C19443.999C5A1C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable What exactly is a LaTeX format? (Re: Validating LaTeX = output)

I'm somewhat confused by suggestions to diff dvi files = etc., at least
done by other than the Keepers of LaTeX, given that = we're all free to
load our own set of fonts at least.  Wouldn't it = be helpful first to
define what a format can/can't contain to be = considered LaTeX; for
instance does mine (I don't think it's alone) qualify = with array.sty
and verbatim.sty loaded, and what if I had British = hyphenation
patterns?  Apart from local validation it would = presumably help with
defining the conditions under which bug reports = should (not) be made.
Sorry if that's been spelt out before but I don't = recall seeing it
anywhere.

I'd at least like to see a few canonical files that = set out to
exercise as wide a range of LaTeX features as = possible (their mutual
exclusion) to provide an easy visual check on style = hacks.

------_=_NextPart_001_01C19443.999C5A1C--