LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Mailing list for the LaTeX3 project <[log in to unmask]>
David Carlisle <[log in to unmask]>
Fri, 1 Oct 1999 14:06:25 +0100
<[log in to unmask]> (message from James Kilfiger on Fri, 1 Oct 1999 13:46:35 +0100)
Mailing list for the LaTeX3 project <[log in to unmask]>
text/plain (31 lines)
> Also are there plans to release any experimental template definitions,
> to supplement the two caption templates and the initial example on the
> slides?

Yes. One reason for the delay between the xparse release and the
template release was that we planned to ship with some examples
(possibly journal front matter) but we've been hard pressed to find
any `spare' time to work on latex this week so decided to let out
template as is. With a bit of luck will get some of the example
applications (and more to the point, their documentation) in a fit state
by next week.

> My idea is that templates could be put into files named <type>.td

Hmm interesting idea. I am not sure if <type>.fd is quite the right
granularity for automatic loading. If there was, say, a template type
for `section headings' then this `type' would be commonly known,
perhaps (one day) known in the format. However a setup wanting a
particular fancy heading layout not obtainable from the existing
templates may well want to have a new template (of the same type)
and then generate instances of that. So perhaps type+name is more what
you would want for automatic loading. (You could of course try both)

In either case, automatic loading might have some implications on
conventions used for names of types and templates. (Just as it does on
font family names, which try to be three letter, to keep the
encoding+family fd file name reasonably short.)