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 f4F8hxf27661 for ; Tue, 15 May 2001 10:43:59 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f4F8hx726276 . for ; Tue, 15 May 2001 10:43:59 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0DD1B.2F12F180" Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f4F8hw001872 for ; Tue, 15 May 2001 10:43:58 +0200 (MET DST) 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 KAA13599 for ; Tue, 15 May 2001 10:43:58 +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 f4F8hv001866 for ; Tue, 15 May 2001 10:43:57 +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 <1.2DA95780@mail.listserv.gmd.de>; Tue, 15 May 2001 10:42:18 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 495415 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 15 May 2001 10:43:54 +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 KAA01305 for ; Tue, 15 May 2001 10:43:53 +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 KAA33078 for ; Tue, 15 May 2001 10:43:52 +0200 Received: from smtp.wanadoo.es (m1smtpisp02.wanadoo.es [62.36.220.21] (may be forged)) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f4F8hlQ11626 for ; Tue, 15 May 2001 10:43:47 +0200 (MET DST) Received: from [62.37.92.95] (62-37-92-95.dialup.uni2.es [62.37.92.95]) by smtp.wanadoo.es (8.10.2/8.10.2) with ESMTP id f4F8hiI25065 for ; Tue, 15 May 2001 10:43:44 +0200 (MET DST) Return-Path: X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.2 Date: Tue, 15 May 2001 10:40:31 +0100 Message-ID: <200105150843.f4F8hiI25065@smtp.wanadoo.es> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Javier Bezos" 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: 4071 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0DD1B.2F12F180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >>The same should apply to, say, Greek. If I write "barbaros" [well, >>imagine it written in Greek] using the same beta, sometimes I would = like to >>see the first one using a differenf glyph from the second one (a = medial >>beta, not used currently). > > And then I suggest that you do this by selecting a (top level) font in > which the beta has the medial form, not by using a special \medialbeta > command or by requesting that the LICR should incorporate something > equivalent to this. Thus, we need 2 virtual font for every font encoding. Don't forget that iota can be rendered below a letter or "in-line" (2), iota and upsilon can be rendered inverted (2), and there is the lunate sigma (2). Since these options are independent, are you suggesting the creation of 16 (!) vf files and tfm files for every font (and encoding)? (And regarding that, Greek is easy compared with scripts like Devanagari or Arabic.) > Provided that both glyphs have slots in the same font, yes, but I = cannot > see any reason why they should. Because they both are necessary at the same time! Are you suggesting that the font must be changed just to select a glyph?!? Javier ------_=_NextPart_001_01C0DD1B.2F12F180 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.2

>>The same should apply to, say, Greek. If I = write "barbaros" [well,
>>imagine it written in Greek] using the same = beta, sometimes I would like to
>>see the first one using a differenf glyph = from the second one (a medial
>>beta, not used currently).
>
> And then I suggest that you do this by selecting = a (top level) font in
> which the beta has the medial form, not by using = a special \medialbeta
> command or by requesting that the LICR should = incorporate something
> equivalent to this.

Thus, we need 2 virtual font for every font encoding. = Don't forget
that iota can be rendered below a letter or = "in-line" (2),
iota and upsilon can be rendered inverted (2), and = there is
the lunate sigma (2). Since these options are = independent, are you
suggesting the creation of 16 (!) vf files and tfm = files for every
font (and encoding)? (And regarding that, Greek is = easy compared
with scripts like Devanagari or Arabic.)

> Provided that both glyphs have slots in the same = font, yes, but I cannot
> see any reason why they should.

Because they both are necessary at the same time! Are = you suggesting
that the font must be changed just to select a = glyph?!?

Javier

------_=_NextPart_001_01C0DD1B.2F12F180--