Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Thu, 13 Jan 2000 22:43:19 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mailserver1.zdv.Uni-Mainz.DE (8.9.3+Sun/8.9.1) with ESMTP id WAA07931 for ; Thu, 13 Jan 2000 22:43:19 +0100 (MET) MIME-Version: 1.0 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA20074 for ; Thu, 13 Jan 2000 22:43:17 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF5E0F.349EB580" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.03132B26@mail.listserv.gmd.de>; Thu, 13 Jan 2000 22:43:02 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 447755 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 13 Jan 2000 22:41:59 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id WAA07082 for ; Thu, 13 Jan 2000 22:41:57 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.1) with ESMTP id WAA08288 for ; Thu, 13 Jan 2000 22:43:07 +0100 (MET) Received: from mailserver1.zdv.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA20062 for ; Thu, 13 Jan 2000 22:43:07 +0100 (MET) Received: from istrati.zdv.uni-mainz.de (dialin411.zdv.Uni-Mainz.DE [134.93.175.111]) by mailserver1.zdv.Uni-Mainz.DE (8.9.3+Sun/8.9.1) with ESMTP id WAA07896 for ; Thu, 13 Jan 2000 22:43:06 +0100 (MET) Received: (from design@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3) id VAA00448; Thu, 13 Jan 2000 21:25:55 +0100 In-Reply-To: <200001131857.SAA07752@mimosa.csv.warwick.ac.uk> References: <200001070658.HAA00191@istrati.zdv.uni-mainz.de> <200001131857.SAA07752@mimosa.csv.warwick.ac.uk> Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1668" "Thu" "13" "January" "2000" "21:25:55" "+0100" "Frank Mittelbach" "frank.mittelbach@LATEX-PROJECT.ORG" nil "33" "Re: environment templates" "^Date:" nil nil "1" nil nil nil nil nil]nil) X-Authentication-Warning: istrati.zdv.uni-mainz.de: design set sender to design@istrati.zdv.uni-mainz.de using -f Content-class: urn:content-classes:message Subject: Re: environment templates Date: Thu, 13 Jan 2000 21:25:55 +0100 Message-ID: <200001132025.VAA00448@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: 3499 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF5E0F.349EB580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable James, > I don't know how verbatim environments will be implemented in latex3, > but the verbatim package requires this short hand. One posiblity = that > comes to mind is that there should be a class writer's version of = \begin > and end (\BeginEnvironment ?) that do not set the current = environment, > and could perhaps be used with verbatim and other unusual things. i know that the current verbatim needs to be used in a special way to = build other environments. but I doubt that this is a serious problem. verbatim = and \verb are special in the way they circument several conventions and = syntax rules within LaTeX (due to their very nature) and if they need a special interface or different handling that would not be too bad in my opinion. > BTW, how is the vertical space handling and the rest of latex2e = coming > along, now that Y2K has come and gone. well contratry to common believe Y2K may has come but it is far from = gone. in fact in the area I earn my living the problems are now starting to = surface (quite interesting that) but yes it is now proceeding more on normal pace again and I'm about to publish what I promised. In fact the two modules now run to about 70 = pages documentation (including code) so I have done something inbetween perhaps I should put out the first (the one containing the high-level paragraphing interfaces) while finishing the documentation of the second (low-level interfaces to build modules from). They need each other to = actually run (ie to be used) but the code itself is not the interesting part but = the interfaces (types/templates/instances) and the documentation of this is = ready or mostly anyway :-) ... frank ------_=_NextPart_001_01BF5E0F.349EB580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: environment templates

James,

 > I don't know how verbatim environments will = be implemented in latex3,
 > but the verbatim package requires this = short hand.  One posiblity that
 > comes to mind is that there should be a = class writer's version of \begin
 > and end (\BeginEnvironment ?) that do not = set the current environment,
 > and could perhaps be used with verbatim = and other unusual things.

i know that the current verbatim needs to be used in a = special way to build
other environments. but I doubt that this is a = serious problem. verbatim and
\verb are special in the way they circument several = conventions and syntax
rules within LaTeX (due to their very nature) and if = they need a special
interface or different handling that would not be too = bad in my opinion.

 > BTW, how is the vertical space handling and = the rest of latex2e coming
 > along, now that Y2K has come and = gone.

well contratry to common believe Y2K may has come but = it is far from gone. in
fact in the area I earn my living the problems are = now starting to surface
(quite interesting that)

but yes it is now proceeding more on normal pace again = and I'm about to
publish what I promised. In fact the two modules now = run to about 70 pages
documentation (including code) so I have done = something inbetween

perhaps I should put out the first (the one containing = the high-level
paragraphing interfaces) while finishing the = documentation of the second
(low-level interfaces to build modules from). They = need each other to actually
run (ie to be used) but the code itself is not the = interesting part but the
interfaces (types/templates/instances) and the = documentation of this is ready
or mostly anyway :-) ...

frank

------_=_NextPart_001_01BF5E0F.349EB580--