Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.6713); Wed, 27 Apr 2005 12:47:51 +0200 Received: by mail.proteosys.com (8.12.10/8.12.2) with ESMTP id j3RAlnqc023905 for ; Wed, 27 Apr 2005 12:47:49 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.119.176]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id j3RAgXtL005567; Wed, 27 Apr 2005 12:42:34 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C54B16.8EF96580" Received: from listserv (listserv.uni-heidelberg.de [129.206.119.176]) by listserv.uni-heidelberg.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id j3QM0IFI028132; Wed, 27 Apr 2005 12:40:28 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8e) with spool id 214237 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 27 Apr 2005 12:40:27 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id j3RAeRrw017189 for ; Wed, 27 Apr 2005 12:40:27 +0200 Received: from smtp110.tiscali.dk (smtp110.tiscali.dk [62.79.79.110]) by relay.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id j3RAgMfK006470 for ; Wed, 27 Apr 2005 12:42:23 +0200 (MET DST) Received: from [192.168.0.103] (h172n4c1o260.bredband.skanova.com [81.231.35.172]) by smtp110.tiscali.dk (8.12.10/8.12.10) with ESMTP id j3RAeV35079361 for ; Wed, 27 Apr 2005 12:40:31 +0200 (CEST) (envelope-from Lars.Hellstrom@math.umu.se) In-Reply-To: <20050427075026.GD10313@mathematik.tu-darmstadt.de> Return-Path: X-OriginalArrivalTime: 27 Apr 2005 10:47:51.0950 (UTC) FILETIME=[8F8A5AE0:01C54B16] x-mime-autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id j3RAeRrw017190 X-Scanned-By: MIMEDefang at proteosys.com X-ProteoSys-SPAM-Score: 0 () Content-class: urn:content-classes:message Subject: Re: new^2 font selection scheme Date: Wed, 27 Apr 2005 11:39:31 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: new^2 font selection scheme Thread-Index: AcVLFo+vrZEvSXtQQNKSGGHMVCIDPA== From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4863 This is a multi-part message in MIME format. ------_=_NextPart_001_01C54B16.8EF96580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 09.50 +0200 2005-04-27, Achim Blumensath wrote: >Hello, > >the MinionPro project was asked about our wishes for an improved font >selection scheme. Say again? Who did the asking and who did the answering? >Currently there are three things which we miss in >NFSS: > >o Separate values of \bfdefault,... depending on the font family. > >o Support for many-dimensional font shapes. We need: > - one axis for roman/italic/swash, > - one axis for u&lc/small caps/spaced small caps/versals, Are you sure "versal" is a proper English term here? I see what you = mean, but I fear "all-caps" is what the English are stuck with for this = concept. As for "spaced small caps": what is that supposed to be for? Some = variation on the ugly spacing for e m p h a s i s tradition, or what? If on the contrary it is semantically equivalent to smallcaps, then it doesn't = belong as a separate position on this axis. > - one axis for text figures/lining figure, and > - one axis for proportional figures/tabular figures. That last one is rather a special case of width. A point to note here is that these first two "o" level items could have = a common solution. \bfdefault is an example of a higher level (than \fontseries, \fontshape, and friends) font selection, but in LaTeX2e = this is very rudimentary; the problem is IMO that there is no interface for a font declaration file to supply the necessary information about what can = be chosen. Multiple shape axes could similarly be implemented on top of the NFSS2 shape axis, if the higher level font selection was more = intelligent. >o The ability to change math fonts within the document. Doesn't \mathversion provide precisely that? > Currently, > \SetSymbolFont and friends are declared \@onlypreamble. This is > needed, for example, to switch to tabular figures when setting = tables. It could be argued, on the grounds that math mode material is full of = glue which would anyway spoil equal-char-width alignment, that in tables = where equal digit widths are important one should not use math mode, but = instead text mode. Lars Hellstr=F6m ------_=_NextPart_001_01C54B16.8EF96580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: new^2 font selection scheme

At 09.50 +0200 2005-04-27, Achim Blumensath = wrote:
>Hello,
>
>the MinionPro project was asked about our wishes = for an improved font
>selection scheme.

Say again? Who did the asking and who did the = answering?

>Currently there are three things which we miss = in
>NFSS:
>
>o Separate values of \bfdefault,... depending on = the font family.
>
>o Support for many-dimensional font shapes. We = need:
>  - one axis for roman/italic/swash,
>  - one axis for u&lc/small caps/spaced = small caps/versals,

Are you sure "versal" is a proper English = term here? I see what you mean,
but I fear "all-caps" is what the English = are stuck with for this concept.

As for "spaced small caps": what is that = supposed to be for? Some variation
on the ugly spacing for  e m p h a s i s  = tradition, or what? If on the
contrary it is semantically equivalent to smallcaps, = then it doesn't belong
as a separate position on this axis.

>  - one axis for text figures/lining figure, = and
>  - one axis for proportional = figures/tabular figures.

That last one is rather a special case of = width.


A point to note here is that these first two = "o" level items could have a
common solution. \bfdefault is an example of a higher = level (than
\fontseries, \fontshape, and friends) font selection, = but in LaTeX2e this
is very rudimentary; the problem is IMO that there is = no interface for a
font declaration file to supply the necessary = information about what can be
chosen. Multiple shape axes could similarly be = implemented on top of the
NFSS2 shape axis, if the higher level font selection = was more intelligent.


>o The ability to change math fonts within the = document.

Doesn't \mathversion provide precisely that?

>  Currently,
>  \SetSymbolFont and friends are declared = \@onlypreamble. This is
>  needed, for example, to switch to tabular = figures when setting tables.

It could be argued, on the grounds that math mode = material is full of glue
which would anyway spoil equal-char-width alignment, = that in tables where
equal digit widths are important one should not use = math mode, but instead
text mode.

Lars Hellstr=F6m

------_=_NextPart_001_01C54B16.8EF96580--