X-VM-v5-Data: ([t nil nil nil nil nil nil nil nil] ["1727" "Sun" "28" "February" "1999" "16:35:08" "+0100" "Thierry Bouche" "Thierry.Bouche@UJF-GRENOBLE.FR" nil "42" "Axis in nfss" "^Date:" nil nil "2" nil "Axis in nfss" nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id QAA15312; Sun, 28 Feb 1999 16:29:24 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <1.F4CF826F@listserv.gmd.de>; Sun, 28 Feb 1999 16:29:20 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 426905 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 28 Feb 1999 16:29:19 +0100 Received: from ujf.ujf-grenoble.fr (ujf.ujf-grenoble.fr [193.54.232.33]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id QAA20296 for ; Sun, 28 Feb 1999 16:29:17 +0100 (MET) Received: from mozart.ujf-grenoble.fr (mozart.ujf-grenoble.fr [193.54.241.5]) by ujf.ujf-grenoble.fr (8.8.5/8.8.5) with ESMTP id QAA29496; Sun, 28 Feb 1999 16:29:17 +0100 (MET) Received: (from bouche@localhost) by mozart.ujf-grenoble.fr (8.7.6/8.6.9) id QAA14126; Sun, 28 Feb 1999 16:35:08 +0100 (MET) X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Message-ID: <199902281535.QAA14126@mozart.ujf-grenoble.fr> Reply-To: Mailing list for the LaTeX3 project Date: Sun, 28 Feb 1999 16:35:08 +0100 From: Thierry Bouche Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Axis in nfss Status: R X-Status: X-Keywords: X-UID: 3249 Hi, Quite a long time ago, it was said that "the good way to implement MakeUppercase & friends would be to add a "case" axis to NFSS". I'd like to know if some activity has been undertaken to address this. It seems obvious to me that current nfss misses 2 axis, namely _width_ ("series" should be broken into weight and width, this bx as \bfdefault reflects TeX + CM history but has the notoriously bad consequence of seeing bold extended used inside text, not restricted to titling material) and _case_. The current situation as regards "series" is not too bad because the translation from markup to layout should be done in a class file, it is however bad that such classes must be dependant on the font system used. the "case" axis is really needed, and will be ever, since unicode ignores small caps, and multiple digits shapes. (It's a unicode flaw, imho, to enforce the capital/small letter distinction [two glyphs for the same charachter, no?] and reject small caps, lining/hanging/tabular figures). I think that adding the cases axis would be rather harmless, since people could simply ignore it (not the same for series vs weight&width) _and_ very usefull, since many have been temptated to turn some variant classes into families to have access to small caps in italic or slanted e.g.). Moreover, creating the few missing fonts with EC would be trivial, and maybe cleaner (accents for caps should be in an all-cap font rather than in TS1?), fontinst could similarly create a bunch more of VFs for supporting PS fonts as well. I'm thinking at least at: all caps (cap digits) c&sc (sc digits--almost inexistant in practice: cf Bell expert) all sc c&lc (lc or old style digits) all lc Thierry Bouche, Grenoble.