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 f1K2Zv106602 for ; Tue, 20 Feb 2001 03:35:57 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1K2Zvd30177 . for ; Tue, 20 Feb 2001 03:35:57 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09AE5.DA7A2480" 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 f1K2ZuH13502 for ; Tue, 20 Feb 2001 03:35:56 +0100 (MET) 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 DAA25588 for ; Tue, 20 Feb 2001 03:35:56 +0100 (MET) 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 f1K2ZuQ26309 for ; Tue, 20 Feb 2001 03:35:56 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.AD286BEC@mail.listserv.gmd.de>; Tue, 20 Feb 2001 3:35:47 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 490215 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 20 Feb 2001 03:35:52 +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 DAA08894 for ; Tue, 20 Feb 2001 03:35:51 +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 DAA58216 for ; Tue, 20 Feb 2001 03:35:51 +0100 Received: from matups.math.u-psud.fr (matups.math.u-psud.fr [129.175.50.4]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1K2Zqx17119 for ; Tue, 20 Feb 2001 03:35:52 +0100 (MET) Received: from stats.math.u-psud.fr (beryl.math.u-psud.fr [129.175.54.194]) by matups.math.u-psud.fr (8.11.0/jtpda-5.3.3) with ESMTP id f1K2ZXG01267 ; Tue, 20 Feb 2001 03:35:33 +0100 (MET) Received: (from sieben@localhost) by stats.math.u-psud.fr (8.9.1b+Sun/8.9.1) id DAA25418; Tue, 20 Feb 2001 03:37:24 GMT Return-Path: Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Tue, 20 Feb 2001 04:37:24 +0100 Message-ID: <200102200337.DAA25418@stats.math.u-psud.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Laurent Siebenmann" 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: 3991 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09AE5.DA7A2480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I was surprised to hear that the use of one TeX hyphenation trie for French (say) is incompatible with the use of several font encodings, say T1 and the Y&Y encoding. To my mind, the problem had in principle been solved long ago. Approximately as follows:- Use the hyphenation tables for T1 encoding. Where the Y&Y encoding is in force, use a hyphenation reincoding vector (\lccode in TeX, \hyphencode for eTeX) to map from Y&Y encoding points to "equivalant". Well, we all know that TeX blew it since the linking between \lccode and hyphenation is assayed only when a paragraph closes. Strangely, eTeX blew it too (so far) -- by allowing only one \hyphencode vector *per* trie, whereas in in the example in hand two are wanted, one for T1 and one for the Y&Y encoding. Why did the eTeX folks tolerate such a silly restriction? Clearly to discourage immoral deviations from T1 encoding! Unfortunately morals like fashions do change from year to year, and then TeXies find themselves wearing shoes that do not fit. Cheers Laurent Siebenmann ------_=_NextPart_001_01C09AE5.DA7A2480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

I was surprised to hear that the use of one TeX = hyphenation trie
for French (say) is incompatible with the use of = several font encodings,
say T1 and the Y&Y encoding.

To my mind, the problem had in principle been solved = long ago.
Approximately as follows:- Use the hyphenation tables = for T1 encoding.
Where the Y&Y encoding is in force, use a = hyphenation reincoding vector
(\lccode in TeX, \hyphencode for eTeX) to map = from  Y&Y encoding points
to "equivalant". Well, we all know that TeX = blew it since the linking
between \lccode and hyphenation is assayed only when = a paragraph
closes. Strangely, eTeX blew it too (so far) -- by = allowing only one
\hyphencode vector *per* trie, whereas in in the = example in hand two
are wanted, one for T1 and one for the Y&Y = encoding.

Why did the eTeX folks tolerate such a silly = restriction?  Clearly to
discourage immoral deviations from T1 encoding!  = Unfortunately morals
like fashions do change from year to year, and then = TeXies find
themselves wearing shoes that do not fit.

Cheers

Laurent Siebenmann

------_=_NextPart_001_01C09AE5.DA7A2480--