LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael John Downes <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Tue, 6 Feb 2001 13:14:20 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
jbezos <[log in to unmask]> writes:
> One of the solutions I considered was to generate a file recording the
> decisions taken in a system when a document is typeset, so that if we
> really want to ensure that TeX complains if there is a different
> configuration we can distribute that file with the main .tex ones.

I wrote a package "snapshot" that provides a way to make such
complaints, by providing a way to embed a dependency list of all
external files used by the document, along with their version numbers.
But only files that use normal LaTeX input mechanisms are trackable.
Because the checksum information of .tfm files is not accessible to
LaTeX, this cannot be written into the dependency list by LaTeX. An
external script could do it. There are some tricky questions such as, do
we include all fonts whose .tfm files are loaded, or only those which
actually have a glyph used in the document? (And I think most of you
will see how it begins to get trickier from there ...)

ATOM RSS1 RSS2