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 p44CYuXE020064 for ; Wed, 4 May 2011 14:34:57 +0200 Received: (qmail 31190 invoked by alias); 4 May 2011 12:34:51 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 04 May 2011 12:34:50 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx009) with SMTP; 04 May 2011 14:34:50 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id p44CWZWf013540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 May 2011 14:32:35 +0200 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 p44AWmdR017058; Wed, 4 May 2011 14:32:34 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1227564 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 4 May 2011 14:32:34 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p44CWYRS023484 for ; Wed, 4 May 2011 14:32:34 +0200 Received: from nm4-vm1.access.bullet.mail.mud.yahoo.com (nm4-vm1.access.bullet.mail.mud.yahoo.com [66.94.237.154]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with SMTP id p44CWKau013427 for ; Wed, 4 May 2011 14:32:21 +0200 Received: from [66.94.237.199] by nm4.access.bullet.mail.mud.yahoo.com with NNFMP; 04 May 2011 12:32:20 -0000 Received: from [66.94.237.108] by tm10.access.bullet.mail.mud.yahoo.com with NNFMP; 04 May 2011 12:32:20 -0000 Received: from [127.0.0.1] by omp1013.access.mail.mud.yahoo.com with NNFMP; 04 May 2011 12:32:20 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 231485.107.bm@omp1013.access.mail.mud.yahoo.com Received: (qmail 63993 invoked by uid 60001); 4 May 2011 12:32:20 -0000 X-YMail-OSG: vnT._FcVM1mSHbHo7cqzHENSJ__cHikt7OPlc0_vwbz3VVy y4hesadkuk_9heVJYVO__HG4LhhYA3hrC4N4.5XgTfDfZdKIJOsuy5daQxnY wDDgTGuIY5JcyQinum6KicLXf978hAbk1AkikBD.ZgqxnUJOkHn.36Wld1vh R.4ymxAiWd3SlvfTHwjfttUQqOSGRwMx_G7sBjT3XQGrmT1Wc1D0yzalnruA Nnq5_QGbslJk4uYHucHw8m7XvwEmBjVH0co1jhPsizAs_P21mTkK6W65w.4T LER7_Vlk5lnQ38SnYR94kvShnN.xEzojA3rSRIaqe_G7HKezJb3qZs56f8xg dOmwdJX4E8g1uAHJHmZ8YLPttDWKohnpHo3yRdpsdbjG49l7CYIj8tZ6lvMq JwyKhc1.eeDr_ Received: from [174.22.77.137] by web82007.mail.mud.yahoo.com via HTTP; Wed, 04 May 2011 05:32:19 PDT X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.110.299900 References: <5BCAF3F0-F09B-4E5A-BC8C-FFC17987F603@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-10088115-1304512339=:63661" Message-ID: <939846.63661.qm@web82007.mail.mud.yahoo.com> Date: Wed, 4 May 2011 05:32:19 -0700 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Paul Thompson Subject: Re: Policy regarding engine specific fixes To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <5BCAF3F0-F09B-4E5A-BC8C-FFC17987F603@gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (eXpurgate); Detail=5D7Q89H36p4qWX7V4skqN6/OUNajYwphP9BdI/Uq0xkxGajBHpVo8/T4WHimb7gXS1SRL 8BsH3jWOzq+/QydlIUq9X1rD7s+n1C/1US94zEQa5vHN+FCQvGoSDt7uiMdfE0DqNbsNo9BWoA24 0ceI4rJcI+YrAN1iJjlQx3BSEPKnqoZHrKrC8LNgxx2LAfz/UaiCQf3KXAoGuSy5GBIsw==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: 6726 --0-10088115-1304512339=:63661 Content-Type: text/plain; charset=us-ascii It's always been the "policy" of The LaTeX Collective, meeting in great hall of the LaTeX Parliament, to allow developers to do as they wish. That is, you can't have a policy if you don't have central direction. LaTeX/TeX is open-source. The developers must do as they wish. There is no there there. Paul Thompson ________________________________ From: Will Robertson To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Sent: Wed, May 4, 2011 7:06:28 AM Subject: Re: Policy regarding engine specific fixes On 04/05/2011, at 9:02 PM, Philipp Stephani wrote: > coming from a comment in the question >http://tex.stackexchange.com/questions/17265, I wonder what the policy of the >LaTeX project is concerning packages that work only under pdfTeX or make some >assumptions that are not valid in the newer engines. Is it intended that such >necessary fixes will be included in the packages or in the kernel, or will the >fixes have to be provided in separate packages? Speaking for myself, I guess it largely depends. We've spoken here before about adding a switch to deactivate inputenc in XeLaTeX/LuaLaTeX but no proposals ever got off the ground. As for amsmath, that's still maintained by the AMS, and I believe they're currently working on an update to that at the moment -- it would be best to contact them directly. (I'm not sure who the best contact there would be.) Cheers, -- Will --0-10088115-1304512339=:63661 Content-Type: text/html; charset=us-ascii
It's always been the "policy" of The LaTeX Collective, meeting in great hall of the LaTeX Parliament, to allow developers to do as they wish.

That is, you can't have a policy if you don't have central direction. LaTeX/TeX is open-source. The developers must do as they wish. There is no there there.
 
Paul Thompson


From: Will Robertson <wspr81@GMAIL.COM>
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Sent: Wed, May 4, 2011 7:06:28 AM
Subject: Re: Policy regarding engine specific fixes

On 04/05/2011, at 9:02 PM, Philipp Stephani wrote:

> coming from a comment in the question http://tex.stackexchange.com/questions/17265, I wonder what the policy of the LaTeX project is concerning packages that work only under pdfTeX or make some assumptions that are not valid in the newer engines. Is it intended that such necessary fixes will be included in the packages or in the kernel, or will the fixes have to be provided in separate packages?


Speaking for myself, I guess it largely depends. We've spoken here before about adding a switch to deactivate inputenc in XeLaTeX/LuaLaTeX but no proposals ever got off the ground. As for amsmath, that's still maintained by the AMS, and I believe they're currently working on an update to that at the moment -- it would be best to contact them directly. (I'm not sure who the best contact there would be.)

Cheers,
-- Will
--0-10088115-1304512339=:63661--