Reply-to: Mailing list for the LaTeX3 project <LATEX-L@VM.URZ.UNI-HEIDELBERG.DE>
Message-id: <m0sZDug-0006MzC@rumple.soas.ac.uk>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date: Fri, 21 Jul 1995 08:58:00 +0000 (GMT)
From: Frank Bennett <fbennett@RUMPLE.SOAS.AC.UK>
Sender: Mailing list for the LaTeX3 project <LATEX-L@VM.URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L <LATEX-L@VM.URZ.UNI-HEIDELBERG.DE>
Subject: Virtual Filenames
Status: R

Dear all,

It seems to me that there is a really important function that a
`virtual' file reader such as that proposed by Matt Swift could
provide, unrelated to whether it is easier or harder to change
the visual layout of a document under LaTeX without changing the
source in any way.  I throw it out for comments.  The idea should
be taken in the spirit of cheering at a boxing match --- I'm not
proposing to get into the ring...

Rather than translating filenames, a virtual filename macro set
could be used to pass *default options* --- particularly dates.
A significant amount of the traffic on comp.text.tex relates to
out-of-date versions of non-core style packages.  LaTeX should
include, by default, a call on an external `register' of styles,
covered by the same conditions as everything else --- not to be
modified, if it's to be called LaTeX.  The contents of this file
would be read in anytime \usepackage or \RequirePackage is used
without an option.  This would feed a most-recent-version date to
any package loaded without options that is contained in the
register.

It should be possible to toggle this behaviour off (or, as it is
being introduced, on), and it should not kick in in compatibility
mode.

This would provide some degree of control for non-`core' packages
--- addressing a complaint about the difficulties of system
maintenance.  This would require, of course, that a register be
maintained.  While it is a bit shirty of me to come up with
suggestions for what the CTAN maintainers should be doing in
their ample free time, it can build forward with *relatively*
little effort if a suitable PERL script --- to insert the date
details into the file if necessary, and to add or update an entry
in the register --- is written for use by the site maintainers in
installing packages on CTAN.

In view of the fact that this involves modifying submitted code,
such a script might also copy the modified file to an \outgoing
directory, from whence the author can pick up the file for
inspection.

Site maintainers are the ones in the front line of this problem,
so their say should, I suppose, be final.

Thoughts?
--
Frank G Bennett, Jr
Law Department, SOAS, London
Tel: (071)323-6351
email: fbennett@rumple.soas.ac.uk
WWW: http://rumple.soas.ac.uk/~fbennett/