Received: by nummer-3.proteosys id <01C19443.9873E1AC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:18 +0100 In-Reply-To: Your message of Thu, 30 Jan 92 15:13:52 +0100. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.9873E1AC" Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> 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: Validating LaTeX output Date: Thu, 30 Jan 1992 17:00:39 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 556 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.9873E1AC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > With the trip and trap tests Don Knuth has given us a tool to validate > TeX and Metafont. But up to now there is no similar tool to validate > LaTeX (nor any other macro package). > One might argue that one could use the same strategy (i.e. producing a > dvi file and using dvitype to check its contents) but there are some > problems: > [...] > 3. The output of dvitype slightly differs between different > implementations. This makes it almost unusable, except for > specialists. Wouldn't it be possible to write a program that parses the dvitype output and checks whether the deviation from some `standard' is within acceptable limits? But it seems that it could be difficult to implement *this* program in an implementation-independent manner. Anyhow, it'd be nice to be able to check an implementation of LaTeX by running a program that said Well, some dimensions were off by as much as 0.0001%. Other than that, everything seems O. K. Anselm. -- Anselm Lingnau, Buchenweg 1, 6239 Eppstein| You see things, and you say = `Why?' lingnau@informatik.uni-frankfurt.de | But I dream things that = never were, University of Frankfurt, CompSci and Maths| and say `Why not?' --- G. = B. Shaw ------_=_NextPart_001_01C19443.9873E1AC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Validating LaTeX output

> With the trip and trap tests Don Knuth has given = us a tool to validate
> TeX and Metafont. But up to now there is no = similar tool to validate
> LaTeX (nor any other macro package).

> One might argue that one could use the same = strategy (i.e. producing a
> dvi file and using dvitype to check its = contents) but there are some
> problems:

> [...]

> 3. The output of dvitype slightly differs between = different
>    implementations. This makes it = almost unusable, except for
>    specialists.

Wouldn't it be possible to write a program that parses = the dvitype
output and checks whether the deviation from some = `standard' is within
acceptable limits? But it seems that it could be = difficult to implement
*this* program in an implementation-independent = manner. Anyhow, it'd be
nice to be able to check an implementation of LaTeX = by running a program
that said

        Well, some = dimensions were off by as much as 0.0001%.
        Other than = that, everything seems O. K.

Anselm.
--
Anselm Lingnau, Buchenweg 1, 6239 Eppstein| You see = things, and you say `Why?'
lingnau@informatik.uni-frankfurt.de     = ;  | But I dream things that never were,
University of Frankfurt, CompSci and Maths| and say = `Why not?'  --- G. B. Shaw

------_=_NextPart_001_01C19443.9873E1AC--