Received: by nummer-3.proteosys id <01C19443.3E93542C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:41:47 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil nil nil t t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.3E93542C" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: Standard styles Date: Sun, 3 Mar 1991 22:33:14 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "LaTeX-L Mailing list" Sender: "Don Hosek" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 297 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.3E93542C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable My feeling on the standard document styles (and this is the way that I teach this in my LaTeX classes) is that they DEFINE the structures that appear in a document type, but only give an EXAMPLE of the appearance of those structures as printed. My approach to style design is to, after some preliminaries, input the base style (report/letter/book/article) which defines the category of documents that I'm working in. Rather than trying to do something like say, let's make article look as much like some "standard" appearance for articles (good luck), let's create good structure definitions in our styles, make it easy to adjust the styles with the outline I gave above, and provide multiple versions of how those classes of documents could appear. -dh ------_=_NextPart_001_01C19443.3E93542C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Standard styles

My feeling on the standard document styles (and this = is the way
that I teach this in my LaTeX classes) is that they = DEFINE the
structures that appear in a document type, but only = give an
EXAMPLE of the appearance of those structures as = printed. My
approach to style design is to, after some = preliminaries, input
the base style (report/letter/book/article) which = defines the
category of documents that I'm working in.

Rather than trying to do something like say, let's = make article
look as much like some "standard" = appearance for articles (good
luck), let's create good structure definitions in our = styles,
make it easy to adjust the styles with the outline I = gave above,
and provide multiple versions of how those classes of = documents
could appear.

-dh


------_=_NextPart_001_01C19443.3E93542C--