Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id o12HErZN032559 for ; Tue, 2 Feb 2010 18:14:55 +0100 Received: (qmail 8772 invoked by alias); 2 Feb 2010 17:14:48 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 02 Feb 2010 17:14:47 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx045) with SMTP; 02 Feb 2010 18:14:47 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id o12HCKNB020237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Feb 2010 18:12:20 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id o12FBVqx019911; Tue, 2 Feb 2010 18:12:12 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 390791 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 2 Feb 2010 18:12:12 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id o12HCCrJ029665 for ; Tue, 2 Feb 2010 18:12:12 +0100 Received: from ueamailgate01.uea.ac.uk (ueamailgate01.uea.ac.uk [139.222.131.184]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id o12HC3t5019869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 2 Feb 2010 18:12:07 +0100 Received: from ueams01.uea.ac.uk (ueams01.uea.ac.uk [139.222.131.78]) by ueamailgate01.uea.ac.uk (8.13.1/8.13.1) with ESMTP id o12HC2k9030828; Tue, 2 Feb 2010 17:12:03 GMT Received: from [139.222.201.49] by ueams01.uea.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NcMIE-0007ZG-Tn; Tue, 02 Feb 2010 17:12:02 +0000 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 References: <4B671436.4020108@morningstar2.co.uk> <19303.19218.784429.433360@morse.mittelbach-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Canit-CHI2: 0.40 X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN, outgoing) X-CanItPRO-Stream: UEA:outgoing (inherits from UEA:default,base:default) X-Canit-Stats-ID: 41627942 - e9de5716f933 X-Scanned-By: MIMEDefang 2.63 on 85.214.41.38 X-Scanned-By: CanIt (www . roaringpenguin . com) on 139.222.131.184 Message-ID: <4B685CE3.4030707@morningstar2.co.uk> Date: Tue, 2 Feb 2010 17:12:03 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: xtemplate and muskips To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <19303.19218.784429.433360@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p4WX0t+AtsdW7yLAyG7gjsvbuMBW1+iOcuX20PnIgZYSReJ2t5I3NmC7otWg svnvgvOP+eSmr2tc2TDb1dCoki7/0rILdCQ5J8e1Y1XT96mqS95amITWUgb1/CuXllYP54VpvjTX ujdQw==V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6218 On 01/02/2010 21:43, Frank Mittelbach wrote: > > Thoughts? At present, (3) is all that is on offer, but perhaps that is > > all we need (do designers care about muskips at all?). > > your last question perhaps depends on whether or not there is going to be a > lot of "templates" for math objects which I somehow doubt, mainly because most > such objects will not need a "designer interface" supporting a number of > possible layouts for some object. But I might be wrong. I'd agree, at least on the current (scant) evidence. > (1) is my favorite as it is clean and fits the rest of the types. > > As you say to implement that it would probably need an underlying support for > muskips as code level types, but you can start by simply having this type > accepting a tokenlist and you deal with it internally for the moment. That > could then later be changed to use whatever the kernel then offers as type > support. My main motivation in sending the mail was to make people aware of the question. I'm happy at the moment with the current solution (use tokenlist and sort it out in the code). This is very much the same as other specialist input (most obviously float-point numbers, but anything which has some "other" structure is handled as a tokenlist at the template level). -- Joseph Wright