Received: by nummer-3.proteosys id <01C19443.3C117C4C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:41:43 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.3C117C4C" 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]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: ?@setsize Date: Wed, 23 Jan 1991 09:55:10 +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: 280 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.3C117C4C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have used \f@size for what I think is the same purpose as = Don's use of \@currsize, so is it really necessary to re-introduce \@currsize or could the same functionality also be implemented = using features of the new schame? Johannes Braams I frequently need to know which size-changing command has been used and _not_ the current typesize. For example, I do doublespacing with a different size changing command rather than a modified \baselinestretch (produces better results, by the way) and since things like verbatim and the like should be handled differently if the enclosing environment is doublespaced than singlespaced, the loss is missed. -dh-dh ------_=_NextPart_001_01C19443.3C117C4C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: ?@setsize

        I have used = \f@size for what I think is the same purpose as Don's
        use of = \@currsize, so is it really necessary to re-introduce
        \@currsize = or could the same functionality also be implemented using
        features = of the new schame?
        Johannes = Braams

I frequently need to know which size-changing command = has been
used and _not_ the current typesize. For example, I = do
doublespacing with a different size changing command = rather than
a modified \baselinestretch (produces better results, = by the way)
and since things like verbatim and the like should be = handled
differently if the enclosing environment is = doublespaced than
singlespaced, the loss is missed.

-dh-dh


------_=_NextPart_001_01C19443.3C117C4C--