Received: by nummer-3.proteosys id <01C19443.9A07536C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:21 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.9A07536C" 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: Re: Validating LaTeX output Date: Mon, 3 Feb 1992 12:41:04 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Eberhard Mattes" Sender: "LaTeX-L Mailing list" To: "Multiple recipients of" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 570 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.9A07536C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Several people pointed out that DVI files created by different TeX implemenations should only differ due to differences in floating point arithmetic. That is not true. DVI files created by different true TeX implementations can be quite different if the TeX implementations use different values for dvi_buf_size. TeX implementations may even omit the `DVI file optimizer': | @ Versions of \TeX\ intended for small computers might well choose to = omit | the ideas in the next few parts of this program, since it is not = really | necessary to optimize the \.{DVI} code by making use of the |w0|, = |x0|, | |y0|, and |z0| commands. [...] -- = tex.web Eberhard Mattes (mattes@azu.informatik.uni-stuttgart.de) ------_=_NextPart_001_01C19443.9A07536C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Validating LaTeX output

Several people pointed out that DVI files created by = different
TeX implemenations should only differ due to = differences in
floating point arithmetic. That is not true. DVI = files created
by different true TeX implementations can be quite = different
if the TeX implementations use different values for = dvi_buf_size.
TeX implementations may even omit the `DVI file = optimizer':

| @ Versions of \TeX\ intended for small computers = might well choose to omit
| the ideas in the next few parts of this program, = since it is not really
| necessary to optimize the \.{DVI} code by making = use of the |w0|, |x0|,
| |y0|, and |z0| commands. [...]

          &nbs= p;            = ;            =             &= nbsp;           &n= bsp;    -- tex.web

Eberhard Mattes = (mattes@azu.informatik.uni-stuttgart.de)

------_=_NextPart_001_01C19443.9A07536C--