Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f1NJ2Yr08339 for ; Fri, 23 Feb 2001 20:02:34 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1NJ2Ys13270 . for ; Fri, 23 Feb 2001 20:02:34 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1NJ1XQ27697 for ; Fri, 23 Feb 2001 20:01:33 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09DCB.2DE0C100" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id UAA28956 for ; Fri, 23 Feb 2001 20:01:33 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1NJ1VQ27686 for ; Fri, 23 Feb 2001 20:01:31 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <12.D98FFAF4@mail.listserv.gmd.de>; Fri, 23 Feb 2001 20:01:18 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 493588 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 23 Feb 2001 20:01:26 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id UAA23912 for ; Fri, 23 Feb 2001 20:01:25 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id UAA35900 for ; Fri, 23 Feb 2001 20:01:24 +0100 Received: from ams.org (sun06.ams.org [130.44.1.6]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1NJ1Nh16653 for ; Fri, 23 Feb 2001 20:01:24 +0100 (MET) Received: (from mjd@localhost) by ams.org (8.11.2/8.11.2) id f1NJ1MJ26231; Fri, 23 Feb 2001 14:01:22 -0500 (EST) In-Reply-To: Lars Hellström's message of "Fri, 23 Feb 2001 19:39:22 +0100" Lines: 23 References: Return-Path: X-Mailer: Gnus v5.7/Emacs 20.7 Content-class: urn:content-classes:message Subject: Re: insufficent NFSS model (?) Date: Fri, 23 Feb 2001 20:01:22 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Michael John Downes" 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: 4011 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09DCB.2DE0C100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Lars Hellstr=F6m writes: > lu for upper and lower case, > su for caps and small caps, > ll for all lower case, > uu for all upper case, and > ss for all small caps. I think "all uppercase" should either go into a separate axis or be combined with the font encoding. If lu, ll, uu are handled through the font encoding then it leaves only small caps to be handled through the font shape. Something like T1/.../.../sc for cap&small caps, T1L/.../.../sc for all small caps, and T1U/.../.../sc identical to T1U/.../.../n. In normal use only these three would be frequently used, I think: T1/.../.../n T1U/.../.../n T1/.../.../sc although T1L/.../.../sc might be useful for acronyms. ------_=_NextPart_001_01C09DCB.2DE0C100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: insufficent NFSS model (?)

Lars Hellstr=F6m <Lars.Hellstrom@MATH.UMU.SE> = writes:

>    lu   for upper and = lower case,
>    su   for caps and = small caps,
>    ll   for all lower = case,
>    uu   for all upper = case, and
>    ss   for all small = caps.

I think "all uppercase" should either go = into a separate axis or be
combined with the font encoding.

If lu, ll, uu are handled through the font encoding = then it leaves only
small caps to be handled through the font shape. = Something like
T1/.../.../sc for cap&small caps, T1L/.../.../sc = for all small caps, and
T1U/.../.../sc identical to T1U/.../.../n.

In normal use only these three would be frequently = used, I think:

  T1/.../.../n
  T1U/.../.../n
  T1/.../.../sc

although T1L/.../.../sc might be useful for = acronyms.

------_=_NextPart_001_01C09DCB.2DE0C100--