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 f1L76r125587 for ; Wed, 21 Feb 2001 08:06:53 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1L76rd02575 . for ; Wed, 21 Feb 2001 08:06:53 +0100 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 f1L76mH22812 for ; Wed, 21 Feb 2001 08:06:48 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09BD4.DE38A480" 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 IAA25106 for ; Wed, 21 Feb 2001 08:06:47 +0100 (MET) 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 f1L76lQ03491 for ; Wed, 21 Feb 2001 08:06:47 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.ADB423B1@mail.listserv.gmd.de>; Wed, 21 Feb 2001 8:06:37 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 491120 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 21 Feb 2001 08:06:43 +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 IAA02661 for ; Wed, 21 Feb 2001 08:06:42 +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 IAA30586 for ; Wed, 21 Feb 2001 08:06:35 +0100 Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1L76Yx08336 for ; Wed, 21 Feb 2001 08:06:34 +0100 (MET) Received: from [195.20.224.219] (helo=mrvdom03.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 14VTMA-00087n-00 for LATEX-L@urz.uni-heidelberg.de; Wed, 21 Feb 2001 08:06:34 +0100 Received: from manz-3e3645b0.pool.mediaways.net ([62.54.69.176] helo=istrati.zdv.uni-mainz.de) by mrvdom03.kundenserver.de with esmtp (Exim 2.12 #2) id 14VTM2-0008LD-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Wed, 21 Feb 2001 08:06:26 +0100 Received: (from latex3@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id IAA27674; Wed, 21 Feb 2001 08:04:25 +0100 In-Reply-To: References: <14980.23750.628032.305093@gargle.gargle.HOWL> <200102091445.JAA00482@plmsc.psu.edu> <200102091643.RAA23818@mozart.ujf-grenoble.Fr> Return-Path: X-Mailer: VM 6.75 under Emacs 20.4.1 X-Authentication-Warning: istrati.zdv.uni-mainz.de: latex3 set sender to frank@mittelbach-online.de using -f Content-class: urn:content-classes:message Subject: Re: Font encodings Date: Wed, 21 Feb 2001 08:04:25 +0100 Message-ID: <14995.26745.159797.466842@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" 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: 3999 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09BD4.DE38A480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Lars, > At 22.20 +0100 2001-02-11, Frank Mittelbach wrote: > >should it perhaps be LY1 suitably renamed (or something similar)? > > No. Unless you can provide a good argument for why letters and the = kind of > symbols which currently reside in TS1 have to appear in the same font = there > is no reason for switching to LY1 or something similar to that. sorry, I should not have mentioned an explicit encoding (and didn't even = know what is in LY1). you are quite right, there is no need to have symbols = that do not take part in kerning > It is another matter though that T1 cannot cover all the European = languages > with latin scripts (as I suspect was originally the intention), so = for e.g. > Romanian and other languages that need comma accents one would need = another > encoding (say T1A). Until someone sits down and creates that however, = could > there perhaps be a slot in TS1 assigned to the comma accent (like it > currently is for the \t accent)? It wouldn't be sufficient for = hyphenation, > but it would at least make it possible to use the accent in general = texts. > (My interest in the matter is that it would be nice to have that put = into > ts1.etx before the final fontinst v1.9 is released.) I think that the use of texual glyphs in the TS encodings is actually = wrong for the very same reason that you pointed out that encodings like LY1 = need not have all the symbols. as long as we only have T1 and TS1 that might be approrpiate, but better would be to have a text encoding covering other languages not covered by T1. frank ------_=_NextPart_001_01C09BD4.DE38A480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Font encodings

Lars,

 > At 22.20 +0100 2001-02-11, Frank Mittelbach = wrote:
 > >should it perhaps be LY1 suitably = renamed (or something similar)?
 >
 > No. Unless you can provide a good argument = for why letters and the kind of
 > symbols which currently reside in TS1 have = to appear in the same font there
 > is no reason for switching to LY1 or = something similar to that.

sorry, I should not have mentioned an explicit = encoding (and didn't even know
what is in LY1). you are quite right, there is no = need to have symbols that do
not take part in kerning

 > It is another matter though that T1 cannot = cover all the European languages
 > with latin scripts (as I suspect was = originally the intention), so for e.g.
 > Romanian and other languages that need = comma accents one would need another
 > encoding (say T1A). Until someone sits = down and creates that however, could
 > there perhaps be a slot in TS1 assigned to = the comma accent (like it
 > currently is for the \t accent)? It = wouldn't be sufficient for hyphenation,
 > but it would at least make it possible to = use the accent in general texts.
 > (My interest in the matter is that it = would be nice to have that put into
 > ts1.etx before the final fontinst v1.9 is = released.)

I think that the use of texual glyphs in the TS = encodings is actually wrong
for the very same reason that you pointed out that = encodings like LY1 need not
have all the symbols. as long as we only have T1 and = TS1 that might be
approrpiate, but better would be to have a text = encoding covering other
languages not covered by T1.

frank

------_=_NextPart_001_01C09BD4.DE38A480--