Received: by nummer-3.proteosys id <01C19443.4508D6DC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:41:58 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil nil nil nil t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4508D6DC" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: Support for accurate page-selection from dvi files Date: Thu, 27 Jun 1991 12:14:21 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "LaTeX-L Mailing list" Sender: "bbeeton" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 362 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4508D6DC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable re making page numbers distinct, at the american math society, we faced this problem long ago (though not in latex). the circumstance was multi-column pages where each column had to be output separately on account of memory limitations (this was tex80), and "pasted up" by the output driver. the convention we devised (and still use with some publications) is \count0 =3D \pageno (for compatibility with plain) \count1 =3D column within page (for consistency, if 1-column pages were mixed with 2-column pages -- an everyday occurrence -- two "logical" pages were put in the dvi file for each "physical" page) \count2 =3D sequential counter, 1, ..., col x number of pages although it doesn't necessarily bear any clear relation to the printed page number, the sequential counter does guarantee a unique value that can be homed in on by a device driver (although not all device drivers may give you access to all ten counters, a difficulty that should be decreasing), and is very nicely reported by tex in the transcript file. if used in conjunction with some more descriptive scheme, it gives a useful value that can help one identify pages properly even to a driver that gives no access at all to the tex counters but always considers the first page of a dvi file to be page "1" (another driver lapse that should mercifully soon be a thing of the past). -- bb ------- ------_=_NextPart_001_01C19443.4508D6DC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Support for accurate page-selection from dvi files

re making page numbers distinct, at the american math = society, we
faced this problem long ago (though not in = latex).  the circumstance
was multi-column pages where each column had to be = output separately
on account of memory limitations (this was tex80), = and "pasted up"
by the output driver.  the convention we devised = (and still use with
some publications) is
  \count0 =3D \pageno (for compatibility with = plain)
  \count1 =3D column within page (for = consistency, if 1-column pages
          &nbs= p; were mixed with 2-column pages -- an everyday occurrence --
          &nbs= p; two "logical" pages were put in the dvi file for = each
          &nbs= p; "physical" page)
  \count2 =3D sequential counter, 1, ..., col x = number of pages
although it doesn't necessarily bear any clear = relation to the printed
page number, the sequential counter does guarantee a = unique value that
can be homed in on by a device driver (although not = all device drivers
may give you access to all ten counters, a difficulty = that should be
decreasing), and is very nicely reported by tex in = the transcript file.
if used in conjunction with some more descriptive = scheme, it gives a
useful value that can help one identify pages = properly even to a driver
that gives no access at all to the tex counters but = always considers
the first page of a dvi file to be page "1" = (another driver lapse that
should mercifully soon be a thing of the = past).
        =         =         =         =         =         -- bb
-------


------_=_NextPart_001_01C19443.4508D6DC--