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 f1AGu1H08524 for ; Sat, 10 Feb 2001 17:56:02 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1AGu1d22158 . for ; Sat, 10 Feb 2001 17:56:01 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09382.5952BD00" 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 f1AGu0M21684 for ; Sat, 10 Feb 2001 17:56:01 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id RAA21889 for ; Sat, 10 Feb 2001 17:56:00 +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 mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1AGu0M21680 for ; Sat, 10 Feb 2001 17:56:00 +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 <11.2CFDB20B@mail.listserv.gmd.de>; Sat, 10 Feb 2001 17:55:53 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487648 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sat, 10 Feb 2001 17:55:56 +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 RAA10347 for ; Sat, 10 Feb 2001 17:55:55 +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 RAA43818 for ; Sat, 10 Feb 2001 17:55:55 +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 f1AGtuu15461 for ; Sat, 10 Feb 2001 17:55:56 +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 f1AGtsG19680 for ; Sat, 10 Feb 2001 17:55:54 +0100 (MET) Received: (from sieben@localhost) by stats.math.u-psud.fr (8.9.1b+Sun/8.9.1) id RAA08794; Sat, 10 Feb 2001 17:57:46 GMT Return-Path: Content-class: urn:content-classes:message Subject: Re: inputenc text (and/or math) Date: Sat, 10 Feb 2001 18:57:46 +0100 Message-ID: <200102101757.RAA08794@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: 3794 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09382.5952BD00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Marcel, Frank M> - Hyphenation tables should really be Unicode (so possibly UTF8 > encoded). They are logically neither input nor output encoding > related, and should work regardless whether either refers to a > castrated font set. I would add that they are in a similar sense not even TeX related. F> In other words you have a hyphenation file, say for German, which > can be used with T1 encoding but also with OT1 encoding by simply > removing all patterns which contain references to umlauts or sharp > s. It seems to be common practice (for French, German...) to even use the *same hyphenation trie* for OT1 and T1? This is something of a lucky accident, but I think it works well (no damage at all to T1 hyphenation, no big damage to OT1). > writing in a cyrillic languages where i want to use both in text as > in math cyrillic letters I suspect this need is rare since Russian math is 99% Latin and Greek and international math symbols. So typing $\Sh$ for a rare Shafarevitz symbol is pretty adequate notation. Russians always have the full US ASCII keyboard. More problematic is the situation for ordinary text in Serbian and Macedonian. There are official (heavily accented) Latin and (mostly unaccented) Cyrillic versions even of the same text; and I expect both typographies often appear in the same document. There is not much problem typing such a document in MicrosoftWord or any similar wordprocessor, and extracting the typescript as 8-bit text, for TeXing. But moving the 8-bit text to Linux or Mac with its two meshed and system dependent 8-bit encodings must be frustrating!? ASCII is the royal road to portability. Cheers Laurent S ------_=_NextPart_001_01C09382.5952BD00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: inputenc text (and/or math)

Marcel, Frank

 M> - Hyphenation tables should really be = Unicode (so possibly UTF8
 >   encoded).  They are = logically neither input nor output encoding
 >   related, and should work = regardless whether either refers to a
 >   castrated font set.

I would add that they are in a similar sense not even = TeX related.

 F> In other words you have a hyphenation = file, say for German, which
 > can be used with T1 encoding but also with = OT1 encoding by simply
 > removing all patterns which contain = references to umlauts or sharp
 > s.

It seems to be common practice (for French, German...) = to even use
the *same hyphenation trie* for OT1 and T1?  = This is something of a
lucky accident, but I think it works well (no damage = at all to T1
hyphenation, no big damage to OT1).

 > writing in a cyrillic languages where i = want to use both in text as
 > in math cyrillic letters

I suspect this need is rare since Russian math is 99% = Latin
and Greek and international math symbols. So typing = $\Sh$
for a rare Shafarevitz symbol is pretty adequate = notation.
Russians always have the full US ASCII = keyboard.

More problematic is the situation for ordinary text = in
Serbian and Macedonian.  There are official = (heavily
accented) Latin and (mostly unaccented) Cyrillic = versions
even of the same text; and I expect both typographies = often
appear in the same document. There is not much = problem
typing such a document in MicrosoftWord or any = similar
wordprocessor, and extracting the typescript as 8-bit = text,
for TeXing. But moving the 8-bit text to Linux or Mac = with
its two meshed and system dependent 8-bit encodings = must be
frustrating!?

ASCII is the royal road to portability.

          &nbs= p;        Cheers

          &nbs= p;            = ;   Laurent S

------_=_NextPart_001_01C09382.5952BD00--