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 f1JKfF105228 for ; Mon, 19 Feb 2001 21:41:15 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1JKfEd28885 . for ; Mon, 19 Feb 2001 21:41:14 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1JKfEQ12102 for ; Mon, 19 Feb 2001 21:41:14 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09AB4.4D6AA780" 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 VAA12357 for ; Mon, 19 Feb 2001 21:41:14 +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 f1JKf7Q12089 for ; Mon, 19 Feb 2001 21:41:12 +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 <1.1BEAC5DA@mail.listserv.gmd.de>; Mon, 19 Feb 2001 21:40:58 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 490827 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 19 Feb 2001 21:41:03 +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 VAA04686 for ; Mon, 19 Feb 2001 21:40:54 +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 VAA05204 for ; Mon, 19 Feb 2001 21:40:54 +0100 Received: from moutvdom01.kundenserver.de (moutvdom01.kundenserver.de [195.20.224.200]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1JKetx28552 for ; Mon, 19 Feb 2001 21:40:55 +0100 (MET) Received: from [195.20.224.208] (helo=mrvdom01.schlund.de) by moutvdom01.kundenserver.de with esmtp (Exim 2.12 #2) id 14Ux70-0005lV-00 for LATEX-L@urz.uni-heidelberg.de; Mon, 19 Feb 2001 21:40:46 +0100 Received: from manz-3e3648a2.pool.mediaways.net ([62.54.72.162] helo=istrati.zdv.uni-mainz.de) by mrvdom01.schlund.de with esmtp (Exim 2.12 #2) id 14Ux72-0002OC-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Mon, 19 Feb 2001 21:40:48 +0100 Received: (from latex3@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id VAA19441; Mon, 19 Feb 2001 21:33:05 +0100 In-Reply-To: References: Return-Path: X-Mailer: VM 6.75 under Emacs 20.4.1 X-Authentication-Warning: istrati.zdv.uni-mainz.de: latex3 set sender to frank@mittelbach-online.de using -f Content-class: urn:content-classes:message Subject: Re: New template macro families Date: Mon, 19 Feb 2001 21:33:04 +0100 Message-ID: <14993.33536.859326.523832@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" 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: 3989 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09AB4.4D6AA780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Lars, David I don't mind either way and happily leave the decision to David but one question: > Compare with the case for the NFSS fontdef tokens. I understood the = meaning > of e.g. \T1/pad/m/n/12 (when TeX was showling an hlist) the first = time I > looked at it, but it took several months before I realised how tricky = it > really was. how tricky was what? are you saying that the decision within NFSS was good or bad? I mean it disallows / as part of a name but it resulted in (given the length) = quite readable names, didn't it? and in practice the use of / did not result = in any practical problems (or does the above statement mean you tried to call a family something/something and then noticed that this is not working?) so perhaps using / for separation so that you get \TP@I/frontmatter/heading/section might be an option too. it would have the advantage of splitting csnames = in their parts is a bit simpler. frank ------_=_NextPart_001_01C09AB4.4D6AA780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: New template macro families

Lars, David

I don't mind either way and happily leave the decision = to David but one
question:

 > Compare with the case for the NFSS fontdef = tokens. I understood the meaning
 > of e.g. \T1/pad/m/n/12 (when TeX was = showling an hlist) the first time I
 > looked at it, but it took several months = before I realised how tricky it
 > really was.

how tricky was what?

are you saying that the decision within NFSS was good = or bad? I mean it
disallows / as part of a name but it resulted in = (given the length) quite
readable names, didn't it? and in practice the use of = / did not result in any
practical problems (or does the above statement mean = you tried to call a
family something/something and then noticed that this = is not working?)

so perhaps using / for separation so that you = get

 \TP@I/frontmatter/heading/section

might be an option too. it would have the advantage of = splitting csnames in
their parts is a bit simpler.

frank

------_=_NextPart_001_01C09AB4.4D6AA780--