Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Wed, 20 Sep 2000 18:06:00 +0200 (MEST) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id SAA07328 for ; Wed, 20 Sep 2000 18:06:00 +0200 (MEST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0231C.AAEBA400" Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id e8KG5xU15469 for ; Wed, 20 Sep 2000 18:05:59 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <10.E2E3088E@mail.listserv.gmd.de>; Wed, 20 Sep 2000 18:05:56 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 471797 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 20 Sep 2000 18:05:53 +0200 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 SAA06746 for ; Wed, 20 Sep 2000 18:05:52 +0200 (MET DST) 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 SAA23168 for ; Wed, 20 Sep 2000 18:05:52 +0200 Received: from abel.math.umu.se (abel.math.umu.se [130.239.20.139]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id SAA10329 for ; Wed, 20 Sep 2000 18:05:52 +0200 (MET DST) Received: from [130.239.20.144] (mac144.math.umu.se [130.239.20.144]) by abel.math.umu.se (8.9.2/8.9.2) with ESMTP id SAA04423 for ; Tue, 19 Sep 2000 18:59:13 +0200 (CEST) In-Reply-To: <008b01c022d6$71d4efa0$78e2fea9@servus> Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id SAA06747 Content-class: urn:content-classes:message Subject: Re: Baseline grid alignment after headings Date: Wed, 20 Sep 2000 17:05:49 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= 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: 3601 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0231C.AAEBA400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 09.42 +0200 2000-09-20, Ulrich Dirr wrote: [snip] >May be it would be helpful if -- and what is in the AFM files -- to >incorporate the ascender/cap height into the TFM (and let TeX know = about >that), so that one could align special material with respect to the >ascender/cap heigth. T1 encoded fonts in general already include these two parameters and a couple of others. I would guess that the ones that interest you are: \fontdimen 8 is cap height \fontdimen 9 is ascender height \fontdimen 10 is accented cap height \fontdimen 11 is descender's depth \fontdimen 12 is max height \fontdimen 13 is max depth I don't think there is a proper LaTeX interface for using them yet = though (although I think something like a fontdimen interface was part of some early template example). OTOH I have the impression that the usual way of getting predictable = height and depth of a box is to include a \strut in them (this is not all that nice since the dimensions of the \strutbox only depends on the \baselineskip, but people usually make do anyway). Lars Hellstr=F6m ------_=_NextPart_001_01C0231C.AAEBA400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Baseline grid alignment after headings

At 09.42 +0200 2000-09-20, Ulrich Dirr wrote:
[snip]
>May be it would be helpful if -- and what is in = the AFM files -- to
>incorporate the ascender/cap height into the TFM = (and let TeX know about
>that), so that one could align special material = with respect to the
>ascender/cap heigth.

T1 encoded fonts in general already include these two = parameters and a
couple of others. I would guess that the ones that = interest you are:
  \fontdimen  8  is cap height
  \fontdimen  9  is ascender = height
  \fontdimen 10  is accented cap = height
  \fontdimen 11  is descender's = depth
  \fontdimen 12  is max height
  \fontdimen 13  is max depth
I don't think there is a proper LaTeX interface for = using them yet though
(although I think something like a fontdimen = interface was part of some
early template example).

OTOH I have the impression that the usual way of = getting predictable height
and depth of a box is to include a \strut in them = (this is not all that
nice since the dimensions of the \strutbox only = depends on the
\baselineskip, but people usually make do = anyway).

Lars Hellstr=F6m

------_=_NextPart_001_01C0231C.AAEBA400--