LATEX-L Archives

Mailing list for the LaTeX3 project


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
James Kilfiger <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Fri, 1 Oct 1999 13:46:35 +0100
text/plain (31 lines)
> I am pleased to announce that the first public test release of [the
> template] code is now available from the project web site.

Thoughts on template loading.

There seems to me to be a qualitative difference between the
\DeclareTemplate command and the \DeclareInstance, \UseInstance and
xparse commands.  FMi mentions that \DeclareTemplate is not for end
users, not even for class-writers.  This is somewhat similar to nfss
\DeclareFontShape compared with \fontshape{..} or \itshape. Perhaps a
similar scheme would be useful.

My idea is that templates could be put into files named <type>.td
When the class or package writer says
the system would first check if a template of that type/name is known,
if not then attempt to load <type>.td.  The analogy is with .fd loading.

This would separate out the low-level Tex from the declaration of
instances and document commands, and would be easier than loading
packages containing template definitions by hand.  It would also make
distribution of templates easier. There would also be a distinction in
file name between classes and packages -- for loading by end-users, and
template definition files -- for loading by classes and packages.

Also are there plans to release any experimental template definitions,
to supplement the two caption templates and the initial example on the