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 f4EFduf24413 for ; Mon, 14 May 2001 17:39:56 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f4EFdt722171 . for ; Mon, 14 May 2001 17:39:55 +0200 MIME-Version: 1.0 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 f4EFdtU09119 for ; Mon, 14 May 2001 17:39:55 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0DC8C.20312E00" 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 RAA10356 for ; Mon, 14 May 2001 17:39:54 +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 f4EFds009525 for ; Mon, 14 May 2001 17:39:54 +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 <8.1F2E8B24@mail.listserv.gmd.de>; Mon, 14 May 2001 17:38:16 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 496168 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 14 May 2001 17:34:17 +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 RAA17779 for ; Mon, 14 May 2001 17:34:16 +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 RAA34486 for ; Mon, 14 May 2001 17:34:17 +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 f4EFYFQ27126 for ; Mon, 14 May 2001 17:34:16 +0200 (MET DST) Received: from wanadoo.es (m1wmail1.wanadoo.es [62.36.220.41]) by smtp.wanadoo.es (8.10.2/8.10.2) with ESMTP id f4EFYCI10291 for ; Mon, 14 May 2001 17:34:12 +0200 (MET DST) Return-Path: x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id RAA17780 x-xam3-api-version: 1.1.11.1.6 x-senderip: 195.53.220.3 Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.2 Date: Mon, 14 May 2001 16:34:12 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "jbezos" 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: 4064 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0DC8C.20312E00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > If Unicode doesn't consider them to be distinct characters, then I see = no > reason why LaTeX should. In general, we don't (as users of TeX or some > extension) select a glyph from a font, as the font is already a = mapping > from characters to glyphs. If the user wants a The mapping is not always unique. >specific rendering of a > character then he should choose a font where the character is rendered = in > that way, not request that each font should provide all alternative > renderings. No, no. A font can contain glyphs variants so that the user can select that he wants (for example, Greek lunate sigma and medial beta are included in several fonts, as well as simplied and traditional Chinese ideograms). They are completely different glyphs, even if they represent the same char; note that many of them are included in Unicode only for compatibility and their use is discouraged. > You have to encode the hyphenation patterns somehow. As Unicode will = cover > all known scripts it can be used as a universal encoding. Furthermore = I > thought that there were OCPs (acting approximately at \shipout time) = that > converted from Unicode to the actual font encodings when they are not = the > same. Is this not correct? But even so, the encoding used when hyphenating is _always_ the font encoding. Javier _____________________________________________________________________ Conoce la que ser=E1 la pel=EDcula del verano y ll=E9vate una camiseta = de cine en http://www.marujasasesinas.com/html/concurso.html ------_=_NextPart_001_01C0DC8C.20312E00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.2

> If Unicode doesn't consider them to be distinct = characters, then I see no
> reason why LaTeX should. In general, we don't = (as users of TeX or some
> extension) select a glyph from a font, as the = font is already a mapping
> from characters to glyphs. If the user wants = a

The mapping is not always unique.

>specific rendering of a
> character then he should choose a font where the = character is rendered in
> that way, not request that each font should = provide all alternative
> renderings.

No, no. A font can contain glyphs variants so = that
the user can select that he wants (for = example,
Greek lunate sigma and medial beta are included = in
several fonts, as well as simplied and = traditional
Chinese ideograms). They are completely = different
glyphs, even if they represent the same char; = note
that many of them are included in Unicode only = for
compatibility and their use is discouraged.

> You have to encode the hyphenation patterns = somehow. As Unicode will cover
> all known scripts it can be used as a universal = encoding. Furthermore I
> thought that there were OCPs (acting = approximately at \shipout time) that
> converted from Unicode to the actual font = encodings when they are not the
> same. Is this not correct?

But even so, the encoding used when hyphenating
is _always_ the font encoding.

Javier
________________________________________________________________= _____
Conoce la que ser=E1 la pel=EDcula del verano y = ll=E9vate una camiseta de cine en http://www.mar= ujasasesinas.com/html/concurso.html

------_=_NextPart_001_01C0DC8C.20312E00--