Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f1JG9C104264 for ; Mon, 19 Feb 2001 17:09:12 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1JG9Cd27926 . for ; Mon, 19 Feb 2001 17:09:12 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1JG98H09583 for ; Mon, 19 Feb 2001 17:09:08 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09A8E.4C268400" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id RAA20487 for ; Mon, 19 Feb 2001 17:09:07 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1JG97Q22346 for ; Mon, 19 Feb 2001 17:09:07 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.1C905C91@mail.listserv.gmd.de>; Mon, 19 Feb 2001 17:08:58 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 490528 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 19 Feb 2001 17:09:04 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id RAA27105 for ; Mon, 19 Feb 2001 17:09:03 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id RAA49714 for ; Mon, 19 Feb 2001 17:08:56 +0100 Received: from server-11.tower-4.starlabs.net (mail.london-1.starlabs.net [212.125.75.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1JG8ux07370 for ; Mon, 19 Feb 2001 17:08:56 +0100 (MET) Received: (qmail 16949 invoked from network); 19 Feb 2001 16:04:38 -0000 Received: from nagmx1e.nag.co.uk (HELO nag.co.uk) (62.232.54.130) by server-11.tower-4.starlabs.net with SMTP; 19 Feb 2001 16:04:38 -0000 Received: from penguin.nag.co.uk (IDENT:root@penguin.nag.co.uk [192.156.217.14]) by nag.co.uk (8.9.3/8.9.3) with ESMTP id QAA13900 for ; Mon, 19 Feb 2001 16:08:52 GMT Received: by penguin.nag.co.uk (8.9.3) id QAA03679; Mon, 19 Feb 2001 16:04:56 GMT In-Reply-To: (message from Lars =?iso-8859-1?Q?Hellstr=F6m?= on Mon, 19 Feb 2001 00:13:56 +0100) References: Return-Path: X-VirusChecked: Checked Content-class: urn:content-classes:message Subject: Re: New template macro families Date: Mon, 19 Feb 2001 17:04:56 +0100 Message-ID: <200102191604.QAA03679@penguin.nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3983 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09A8E.4C268400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > but no new naming scheme was specified. sorry. I got tied up in MathML2 (and Frank in unicode issues, judging by this weekends activity on th elist:-) Yes your names definitely seem better than the old ones. It would be possible I suppose to make it even harder to "accidentally" create these names by having mismatched } in the names rather than {} pairs which are still easy to enter in commands that pass their argument to csname: *\begin{a{b}c} ! LaTeX Error: Environment a{b}c undefined. I thought that was what you had originally suggested? so where you have Current name: \describecsfamily{TP@<\meta{type}>} New name: \describecsfamily{TP@T{\meta{type}}} ie a name of the form \csname TP@T{xxx}\endcsname you could have names \csname TP@T}xxx}\endcsname Thoughts? David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet = delivered through the MessageLabs Virus Control Centre. For further information = visit http://www.star.net.uk/stats.asp ------_=_NextPart_001_01C09A8E.4C268400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: New template macro families

> but no new naming scheme was specified.

sorry.
I got tied up in MathML2 (and Frank in unicode = issues, judging by this
weekends activity on th elist:-)

Yes your names definitely seem better than the old = ones.
It would be possible I suppose to make it even harder = to "accidentally"
create these names by having mismatched } in the = names rather than
{} pairs which are still easy to enter in commands = that pass their
argument to csname:

*\begin{a{b}c}

! LaTeX Error: Environment a{b}c undefined.


I thought that was what you had originally = suggested?

so where you have

 Current name: = \describecsfamily{TP@<\meta{type}>}
  New name: = \describecsfamily{TP@T{\meta{type}}}

ie a name of the form

\csname TP@T{xxx}\endcsname

you could have names

\csname TP@T}xxx}\endcsname

Thoughts?

David

________________________________________________________________= _____
This message has been checked for all known viruses = by Star Internet delivered
through the MessageLabs Virus Control Centre. For = further information visit
http://www.star.net.uk/stats.as= p

------_=_NextPart_001_01C09A8E.4C268400--