Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.6713); Sat, 6 Dec 2003 00:28:45 +0100 Received: by mail.proteosys.com (8.12.10/8.12.2) with ESMTP id hB5NSgHV022713 for ; Sat, 6 Dec 2003 00:28:43 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id hB5NLMSe018849; Sat, 6 Dec 2003 00:21:22 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3BB87.869E3480" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id hB5N0Ec7014233; Sat, 6 Dec 2003 00:14:22 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0112 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 6 Dec 2003 00:14:22 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id hB5NELZt014568 for ; Sat, 6 Dec 2003 00:14:21 +0100 Received: from localhost.localdomain (p3EE20C80.dip.t-dialin.net [62.226.12.128]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id hB5NLCSe018829 for ; Sat, 6 Dec 2003 00:21:13 +0100 (MET) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hB5MRctM012084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Dec 2003 23:27:39 +0100 Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id hB5MRcXe012080; Fri, 5 Dec 2003 23:27:38 +0100 In-Reply-To: <2BD713C8-276E-11D8-A703-0050E4455404@atlis.com> Lines: 55 References: <2BD713C8-276E-11D8-A703-0050E4455404@atlis.com> Return-Path: X-OriginalArrivalTime: 05 Dec 2003 23:28:45.0783 (UTC) FILETIME=[8715AE70:01C3BB87] User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0 () Content-class: urn:content-classes:message Subject: Re: latex template design style Date: Fri, 5 Dec 2003 23:27:37 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: latex template design style Thread-Index: AcO7h4c0xeeEV7eWTI+Bm9hMTI3c9w== From: "David Kastrup" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4744 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3BB87.869E3480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable "William F. Adams" writes: > Did anyone ever volunteer for this? > > I've been working my way through some things at work and for TUGboat > and've had some thoughts along these lines, which I've just posted to > comp.text.tex---assuming my reasoning is decently good, and no one = else > has volunteered, I'd like to look into this once I've finished up two > things for TUGboat. > > Here's the post to CTT: > > Here's a question I've tried to pose elsewhere and will shamelessly > insert here: > > Will matters like this be addressed / ameliorated / solved by Latex3? > (See Frank Mittelbach's post that now that the new edition of the = Latex > Companion is done he'll have time to work on Latex3 again). > > For my part, I'd really like to see a more granular approach to > documentclasses and packages so that it would be easier to integrate > different bits reliably. > > say something like: > > %\language[American]{English} > \languages{English, Chinese, Finish, Spanish} > > \typespecification[headings]{Univers-condensed} > \typespecification[captions]{Univers} > \typespecification[text, 10]{TimesTen} > \typespecification[math]{Euler} > \typespecification[monospace]{Courier} > > \pagelayout[cropmarks, sheet-information, picas, 36 x 54, > golden]{classics} > > \end{document} [...] > Maybe I'm a wuss---but I find umpteen dozen iterations of > \usepackage confusing.... Are you thinking of something like Emacs autoloaded macros? So one would want to have things be autoloaded upon first macro use or so? I think that something like this was optional for some versions of the picture environment, for LaTeX2e installations short of memory space. Should one have such a thing for a vast amount of packages without having to name them explicitly? Catering for the standard problem of "I tried using this code from the LaTeX Companion and it did not work." "Have you loaded the package soandso in your preamble?" -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ------_=_NextPart_001_01C3BB87.869E3480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: latex template design style

"William F. Adams" <wadams@ATLIS.COM> = writes:

> Did anyone ever volunteer for this?
>
> I've been working my way through some things at = work and for TUGboat
> and've had some thoughts along these lines, = which I've just posted to
> comp.text.tex---assuming my reasoning is = decently good, and no one else
> has volunteered, I'd like to look into this once = I've finished up two
> things for TUGboat.
>
> Here's the post to CTT:
>
> Here's a question I've tried to pose elsewhere = and will shamelessly
> insert here:
>
> Will matters like this be addressed / = ameliorated / solved by Latex3?
> (See Frank Mittelbach's post that now that the = new edition of the Latex
> Companion is done he'll have time to work on = Latex3 again).
>
> For my part, I'd really like to see a more = granular approach to
> documentclasses and packages so that it would be = easier to integrate
> different bits reliably.
>
> say something like:
>
> %\language[American]{English}
> \languages{English, Chinese, Finish, = Spanish}
>
> = \typespecification[headings]{Univers-condensed}
> \typespecification[captions]{Univers}
> \typespecification[text, 10]{TimesTen}
> \typespecification[math]{Euler}
> \typespecification[monospace]{Courier}
>
> \pagelayout[cropmarks, sheet-information, picas, = 36 x 54,
> golden]{classics}
>
> \end{document}
[...]

> Maybe I'm a wuss---but I find umpteen dozen = iterations of
> \usepackage confusing....

Are you thinking of something like Emacs autoloaded = macros?  So one
would want to have things be autoloaded upon first = macro use or so?

I think that something like this was optional for some = versions of the
picture environment, for LaTeX2e installations short = of memory space.
Should one have such a thing for a vast amount of = packages without
having to name them explicitly? Catering for the = standard problem of
"I tried using this code from the LaTeX = Companion and it did not
work." "Have you loaded the package soandso = in your preamble?"

--
David Kastrup, Kriemhildstr. 15, 44793 Bochum

------_=_NextPart_001_01C3BB87.869E3480--