X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2429" "Mon" "16" "June" "1997" "00:14:32" "+0400" "Vladimir Volovich" "TeX@VVV.VSU.RU" nil "49" "Re: Multilingual TeX --- and a successor to TeX" "^Date:" nil nil "6" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.5/8.8.4) with ESMTP id WAA26068; Sun, 15 Jun 1997 22:17:45 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <5.6933190A@listserv.gmd.de>; Sun, 15 Jun 1997 22:17:44 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 153544 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 15 Jun 1997 22:17:40 +0200 Received: from cc.vsu.ru (root@[194.226.29.62]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with ESMTP id WAA12821 for ; Sun, 15 Jun 1997 22:17:26 +0200 (MET DST) Received: (from uucp@localhost) by cc.vsu.ru (8.8.5-MVC-230497/8.8.5) with UUCP id AAA13595 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 16 Jun 1997 00:15:17 +0400 Received: from vvv (vvv@localhost [127.0.0.1]) by vvv.vrn.ru (8.8.5/8.8.5) with SMTP id AAA00495 for ; Mon, 16 Jun 1997 00:14:32 +0400 X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.1.42 i586) MIME-Version: 1.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <33A44D28.37ECD856@vvv.vsu.ru> Reply-To: Mailing list for the LaTeX3 project Date: Mon, 16 Jun 1997 00:14:32 +0400 From: Vladimir Volovich Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Multilingual TeX --- and a successor to TeX Status: R X-Status: X-Keywords: X-UID: 2048 Hello, Werner Lemberg wrote: > > Both approaches work well (the former I've used in my vncmr package for > > Vietnamese to define an ET5 encoding, the latter for a experimental LLW > > encoding using the `fil' option of the LH fonts to get more characters) > > for *all* encodings in the range 0x80-0xFF since the interface used here > > for TeX is only 7bit, and \uccode and \lccode for characters >= 0x80 will > > be never used. > > This is misleading, sorry. Of course I meant case changing only. For > proper hyphenation you still need T2 encoded fonts if you don't want to > change the lccodes. I suppose that LLW encoding is something close to LWN encoding, in which one has to use sequences of latin characters which are translated by means of ligatures into russian letters (+some other, added by option `fil')? Then, if we assume the default lccode and uccode values for characters 0x00..0x7f, then \uppercase and \lowercase will work properly independently of lccode and uccode settings for characters 0x80..0xff? Is that what you meant by the phrase "both approaches work well for *all* encodings"? Then I did not catch the idea, why "for proper hyphenation you still need T2 encoded fonts"? BTW, is a ET5 encoding similar to LWN encoding in sence of using sequences of latin letters to typeset vietnamese letters via ligatures? How many letters are there in vietmamese alphabet? And what about Chinese? (are the principles the same there, too?) ;-) It is also interesting to know, is this `latin based' encoding popular in Vietnam? I'd like to say, that I'm 99.99% sure that the LWN encoding will not be widely used as a native encoding in Russia (where Russian language is the main). The LWN encoding (and all other `latin-based' russian encodings) is only useful for typesetting small text pieces (such as bibliography references) in a big non-russian text. Or maybe, when there are no packages available to russify screen fonts and keyboard. The *main* russian encoding (which will be *widely* used) will be 8-bit (for both *external* TeX encoding and internal). Why russian people should use combinations of latin characters to typeset Russian, when they are able to typeset in a `native' encoding, when each letter has it's own code and is visible on the screen? Moreover, it is not too easy to read russian texts which are written in LWN encoding. ;-) -- With best regards, Vladimir.