X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	["1436" "Fri" "1" "October" "1999" "14:06:25" "+0100" "David Carlisle" "davidc@NAG.CO.UK" nil "31" "Re: Experimental `template' interface code" "^Date:" nil nil "10" nil nil nil nil nil]
	nil)
Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5])
	by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id PAA09012
	for <schoepf@UNI-MAINZ.DE>; Fri, 1 Oct 1999 15:09:53 +0200 (MET DST)
Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <1.7810E374@mail.listserv.gmd.de>; Fri, 1 Oct 1999 15:09:49 +0200
Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE
          (LISTSERV-TCP/IP release 1.8b) with spool id 445152 for
          LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 1 Oct 1999 15:08:24 +0200
Received: from nag.co.uk (openmath.nag.co.uk [192.156.217.16]) by
          relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id PAA18957 for
          <LATEX-L@URZ.UNI-HEIDELBERG.DE>; Fri, 1 Oct 1999 15:08:04 +0200 (MET
          DST)
Received: (from davidc@localhost) by nag.co.uk (AIX4.2/UCB 8.7/8.7) id
          OAA18170; Fri, 1 Oct 1999 14:06:25 +0100 (BST)
References:  <199910011246.NAA04394@mimosa.csv.warwick.ac.uk>
Message-ID:  <199910011306.OAA18170@nag.co.uk>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <199910011246.NAA04394@mimosa.csv.warwick.ac.uk> (message from
              James Kilfiger on Fri, 1 Oct 1999 13:46:35 +0100)
Date:         Fri, 1 Oct 1999 14:06:25 +0100
From: David Carlisle <davidc@NAG.CO.UK>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Subject:      Re: Experimental `template' interface code
Status: R
X-Status: 
X-Keywords:                  
X-UID: 3345

> 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.)


David