Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Wed, 14 Aug 2002 14:50:20 +0200 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id g7ECoIVP028529 for ; Wed, 14 Aug 2002 14:50:19 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g7ECZddA004800; Wed, 14 Aug 2002 14:35:40 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C24391.259A8E00" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id g7E3q1AO009281; Wed, 14 Aug 2002 14:35:27 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 4355 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 14 Aug 2002 14:35:27 +0200 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.2/8.12.2/SuSE Linux 0.6) with ESMTP id g7ECZQ3s014042 for ; Wed, 14 Aug 2002 14:35:26 +0200 Received: from smtp.albany.edu (mail1.csc.albany.edu [169.226.1.133]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g7ECZZn5005697 for ; Wed, 14 Aug 2002 14:35:36 +0200 (MET DST) Received: from hilbert.math.albany.edu (hilbert.math.albany.edu [169.226.23.52]) by smtp.albany.edu (8.12.5/8.12.5) with ESMTP id g7ECZZ4B018787 for ; Wed, 14 Aug 2002 08:35:35 -0400 (EDT) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.12.5/8.12.5/Submit) id g7ECZXS1029590; Wed, 14 Aug 2002 08:35:33 -0400 (EDT) In-Reply-To: <3D5A300D.3801A7AE@ffn.ub.es> Lines: 22 References: <3D5A300D.3801A7AE@ffn.ub.es> Return-Path: X-OriginalArrivalTime: 14 Aug 2002 12:50:20.0483 (UTC) FILETIME=[25E44130:01C24391] User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 X-Scanned-By: MIMEDefang 2.6 (www dot roaringpenguin dot com slash mimedefang) Content-class: urn:content-classes:message Subject: Re: LaTeX classes Date: Wed, 14 Aug 2002 13:35:33 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: LaTeX classes Thread-Index: AcJDkSYSzcjKptj+Sfu9tXFeADJgsw== From: "William F Hammond" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4360 This is a multi-part message in MIME format. ------_=_NextPart_001_01C24391.259A8E00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Daniel Arteaga writes: > The creation of a new LaTeX class requires a deep knowledge of TeX and > LaTeX, and cannot be easily done by a "normal" user. There are not a = lot > of general purpose alternatives, and most of the people continues = using > standard LaTeX classes (specially article). However, many times = standard > classes are not completely satisfactory, and it is a usual practice to > manually adapt titles, margins, spacings, headings, etc. in a not = always > optimum way. In most cases, the best would be to have a new adapted > LaTeX class. One's view of this changes somewhat if one looks at LaTeX as a typesetting language for the formatting of, say, TEI documents. Then there is amelioration of much of what you cite because LaTeX is then no longer the storage vehicle for both one's document source and one's styling taste. Writing such a formatter IMHO is easier than making significant changes in a LaTeX class, and it poses no risk to the integrity of one's archive of document source. -- Bill ------_=_NextPart_001_01C24391.259A8E00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX classes

Daniel Arteaga <darteaga@FFN.UB.ES> = writes:

> The creation of a new LaTeX class requires a deep = knowledge of TeX and
> LaTeX, and cannot be easily done by a = "normal" user. There are not a lot
> of general purpose alternatives, and most of the = people continues using
> standard LaTeX classes (specially article). = However, many times standard
> classes are not completely satisfactory, and it = is a usual practice to
> manually adapt titles, margins, spacings, = headings, etc. in a not always
> optimum way. In most cases, the best would be to = have a new adapted
> LaTeX class.

One's view of this changes somewhat if one looks at = LaTeX as a
typesetting language for the formatting of, say, TEI = documents.
Then there is amelioration of much of what you cite = because LaTeX is
then no longer the storage vehicle for both one's = document source and
one's styling taste.

Writing such a formatter IMHO is easier than making = significant
changes in a LaTeX class, and it poses no risk to the = integrity of
one's archive of document source.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C24391.259A8E00--