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 f4EAYcf22964 for ; Mon, 14 May 2001 12:34:38 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f4EAYc720797 . for ; Mon, 14 May 2001 12:34:38 +0200 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f4EAYbU12086 for ; Mon, 14 May 2001 12:34:37 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0DC61.79D03300" 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 MAA15429 for ; Mon, 14 May 2001 12:34:37 +0200 (MEST) 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 f4EAYa012790 for ; Mon, 14 May 2001 12:34:36 +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 <6.793E6620@mail.listserv.gmd.de>; Mon, 14 May 2001 12:32:59 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 495595 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 14 May 2001 12:34:33 +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 MAA11572 for ; Mon, 14 May 2001 12:34:30 +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 MAA43782 for ; Mon, 14 May 2001 12:34:31 +0200 Received: from hromeo.algonet.se (hromeo.algonet.se [194.213.74.51]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f4EAYTQ07853 for ; Mon, 14 May 2001 12:34:29 +0200 (MET DST) Received: (qmail 10053 invoked from network); 14 May 2001 12:34:22 +0200 Received: from delenn.tninet.se (HELO algonet.se) (195.100.94.104) by hromeo.algonet.se with SMTP; 14 May 2001 12:34:22 +0200 Received: from [195.100.226.132] (du128-226.ppp.su-anst.tninet.se [195.100.226.128]) by delenn.tninet.se (BLUETAIL Mail Robustifier 2.2.2) with ESMTP id 378410.836458.989delenn-s1 for ; Mon, 14 May 2001 12:34:18 +0200 In-Reply-To: Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.2 Date: Mon, 14 May 2001 11:31:37 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" 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: 4059 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0DC61.79D03300 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 12:18 +0200 2001/05/14, jbezos wrote: >> >For example, removing the fi ligature in Turkish. Or using an = alternate >> >ortography in languages with contextual analysis. >> >> That doesn't seem like metric transformations to me, but more like > >Actually, they aren't, but for some reason Knuth >very likely understands, this information is included >in the tfm files (text font *metrics*). One reason could be that ligatures can be viewed as an extreme form of kerning: For example, the "f" and "i" are kerned together until their rendering becomes a single character. This is in fact good, because one could think of automated forms of = kerning (say making use of character renderings which are not square boxes or something), and if the information already is in the metrics file, that will become possible. Hans Aberg ------_=_NextPart_001_01C0DC61.79D03300 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.2

At 12:18 +0200 2001/05/14, jbezos wrote:
>> >For example, removing the fi ligature in = Turkish. Or using an alternate
>> >ortography in languages with contextual = analysis.
>>
>> That doesn't seem like metric = transformations to me, but more like
>
>Actually, they aren't, but for some reason = Knuth
>very likely understands, this information is = included
>in the tfm files (text font *metrics*).

One reason could be that ligatures can be viewed as an = extreme form of
kerning: For example, the "f" and = "i" are kerned together until their
rendering becomes a single character.

This is in fact good, because one could think of = automated forms of kerning
(say making use of character renderings which are not = square boxes or
something), and if the information already is in the = metrics file, that
will become possible.

  Hans Aberg

------_=_NextPart_001_01C0DC61.79D03300--