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 f17DpDH23819 for ; Wed, 7 Feb 2001 14:51:13 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f17DpCd09302 . for ; Wed, 7 Feb 2001 14:51: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 f17DpBM10122 for ; Wed, 7 Feb 2001 14:51:11 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0910D.08865E80" 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 OAA10433 for ; Wed, 7 Feb 2001 14:51:11 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 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 f17DpA719442 for ; Wed, 7 Feb 2001 14:51:10 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.DC809A8F@mail.listserv.gmd.de>; Wed, 7 Feb 2001 14:51:05 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488619 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 7 Feb 2001 14:50:53 +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 OAA27927 for ; Wed, 7 Feb 2001 14:50:52 +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 OAA05914 for ; Wed, 7 Feb 2001 14:50:52 +0100 Received: from abel.math.umu.se (abel.math.umu.se [130.239.20.139]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f17Doqu10171 for ; Wed, 7 Feb 2001 14:50:52 +0100 (MET) Received: from [130.239.20.144] (mac144.math.umu.se [130.239.20.144]) by abel.math.umu.se (8.9.2/8.9.2) with ESMTP id OAA32060; Wed, 7 Feb 2001 14:49:05 +0100 (CET) In-Reply-To: <14971.10163.320991.33744@istrati.zdv.uni-mainz.de> References: <14968.6710.114015.220264@ux28.nets.de.eds.com> <200101292234.RAA14964@pluto.math.albany.edu> <14967.8829.903878.620595@istrati.zdv.uni-mainz.de> <200101310003.BAA02073@peano.cs.uni-dortmund.de> <14967.46479.253389.421142@istrati.zdv.uni-mainz.de> Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id OAA27928 Content-class: urn:content-classes:message Subject: Re: inputenc -> text+math Date: Wed, 7 Feb 2001 14:50:50 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= 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: 3737 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0910D.08865E80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 22.33 +0100 2001-02-02, Frank Mittelbach wrote: >Lars wrote: [snip] > > What I suspect is the right solution is to have \protect set to > > \@unexpandable@protect when scanning for \omit and have it reset to Actually, after thinking about it a bit more I think it should be \noexpand\protect rather than \noexpand\protect\noexpand; there's no = need for the extra \noexpand as the expansion is stopped at the first thing which is \noexpand'ed. > > \@typeset@protect in the column template---then the robustness = mechanisms > > for normal robust commands, text commands, and in the \IeC command > > respectively would take care of sorting things out. I doubt this can = be > > done by patching the \halign primitive, but it could be built into = e.g. the > > array package. > >yes, that would solve the problem i'm pretty sure of it but as i said = in my >earlier mail this really doesn't help because it would then only work = in array >but not in, any contributed package that uses \halign (this is why = Vladimir >tries to patch \halign). > >perhaps one should investigate combining your solution (change of = protect) >with a patch to \halign after all, eg via a clever use of \everycr and = the >like. One variant would be to start offering LaTeX-variants of \halign and \valign which (i) has less corny syntax, (ii) takes care to prevent = errors of the kind discussed, and (iii) might offer a few extra features (e.g. calc-like syntax for \tabskip glue specifications or something; I don't know if that might be useful). What I'm thinking of is that you could = write something like \latex@halign[]{ ... \do[]{} ... } \latex@endhalign and have it work sort of like \tabskip=3D \halign{ ... &\tabskip=3D& ... \cr \crcr} but also do the (ii) above (so there would probably be a = prepended to each ). The arguments are optional in case you = don't want to set the \tabskip glue (but occurs to me that an explicit = \NoValue would be more appropriate for this level). The idea is that since we = don't try to invent a new syntax for the