Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 31 Jan 2003 19:07:29 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0VI7P6D010249 for ; Fri, 31 Jan 2003 19:07:27 +0100 Received: from exfront1.zdv.uni-mainz.de (exfront1.zdv.Uni-Mainz.DE [134.93.8.75]) by mailgate2.zdv.Uni-Mainz.DE (8.12.6/8.12.6) with ESMTP id h0VI7ONM005125 for ; Fri, 31 Jan 2003 19:07:25 +0100 (MET) Received: from spamgate1.zdv.Uni-Mainz.DE ([134.93.8.231]) by exfront1.zdv.uni-mainz.de with Microsoft SMTPSVC(5.0.2195.5329); Fri, 31 Jan 2003 19:01:48 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C953.9DFF0680" Received: from mailgate3.zdv.Uni-Mainz.DE (mailgate3.zdv.Uni-Mainz.DE [134.93.130.78]) by spamgate1.zdv.Uni-Mainz.DE (8.12.6/8.12.2) with ESMTP id h0VI1kpJ007588 for ; Fri, 31 Jan 2003 19:01:47 +0100 (MET) Received: from tug.org (tug.org [130.225.2.178]) by mailgate3.zdv.Uni-Mainz.DE (8.12.6/8.12.6) with ESMTP id h0VI1jS0010069 for ; Fri, 31 Jan 2003 19:01:46 +0100 (MET) Received: from tug.org (localhost.localdomain [127.0.0.1]) by tug.org (8.11.6/8.11.6) with ESMTP id h0VHPNx11892; Fri, 31 Jan 2003 18:25:23 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by tug.org (8.11.6/8.11.6) with ESMTP id h0VHOox11874 for ; Fri, 31 Jan 2003 18:24:50 +0100 Received: from fwd08.sul.t-online.de by mailout02.sul.t-online.com with smtp id 18eeuB-0003bc-07; Fri, 31 Jan 2003 18:24:43 +0100 Received: from localhost.localdomain (520018396234-0001@[217.80.160.68]) by fmrl08.sul.t-online.com with esmtp id 18eeu8-1BaEQCC; Fri, 31 Jan 2003 18:24:40 +0100 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.5/8.12.5) with ESMTP id h0VHNQbY006000; Fri, 31 Jan 2003 18:23:41 +0100 Received: (from dak@localhost) by localhost.localdomain (8.12.5/8.12.5/Submit) id h0VHNODj005996; Fri, 31 Jan 2003 18:23:24 +0100 In-Reply-To: Lines: 33 References: Return-Path: X-OriginalArrivalTime: 31 Jan 2003 18:01:48.0911 (UTC) FILETIME=[D3498FF0:01C2C952] List-Id: List-Post: Errors-To: tex-implementors-bounces@tug.org X-BeenThere: tex-implementors@tug.org X-Mailman-Version: 2.1 List-Archive: X-Sender: 520018396234-0001@t-dialin.net User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -4.7 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_GNUS_UA X-Spam-Report: CARRIAGE_RETURNS,IN_REP_TO,QUOTED_EMAIL_TEXT,RCVD_IN_OSIRUSOFT_COM,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_GNUS_UA,X_OSIRU_DUL Content-class: urn:content-classes:message Subject: Re: [tex-implementors] TeX+locale, solution? Date: Fri, 31 Jan 2003 18:23:24 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [tex-implementors] TeX+locale, solution? Thread-Index: AcLJU54201MUQxYATxuCV0hO2cOX8Q== List-Help: List-Subscribe: , List-Unsubscribe: , From: "David Kastrup" To: "Vladimir Volovich" Cc: Status: R X-Status: X-Keywords: X-UID: 4515 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C953.9DFF0680 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Vladimir Volovich writes: > TeX must ignore locale, and must not assume the encoding of the > document from the locale: the encoding of the TeX file must be > specified in the files itself (e.g. via an option to the inputenc > package), just like in XML documents. Actually, a _correct_ implementation as far as I feel able to judge would employ the _complete_ locale information available for mapping the complete input encoding (including latin-1, latin-2 or whatever else it is set to) to a canonical TeX encoding (currently this would probably mean T1, with Omega of course Unicode). The external locale information, however, would be completely ignored (except maybe for terminal output in some manner) when the document specified a locale itself. That is: a TeX document with declared input encodings should be transferred as a binary. A TeX document without declared input encodings should be transferred as a text file, with all necessary reencodings necessary to make it display correctly when read under a different locale. That would make TeX behave correct as an application as far as I can see. Of course, this exact behavior is, if at all, not doable with the current Web2C implementation: LaTeX has no way to tell the input machinery when it has detected it would want to override any detected locale information. A TCX-file comment in the first line of the file would be some way to specify locale overrides, but it is a way that completely bypasses LaTeX and macro control. --=20 David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ tex-implementors mailing list postmaster@tug.org http://tug.org/mailman/listinfo/tex-implementors ------_=_NextPart_001_01C2C953.9DFF0680 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [tex-implementors] TeX+locale, solution?

Vladimir Volovich <vvv@vsu.ru> writes:

> TeX must ignore locale, and must not assume the = encoding of the
> document from the locale: the encoding of the = TeX file must be
> specified in the files itself (e.g. via an = option to the inputenc
> package), just like in XML documents.

Actually, a _correct_ implementation as far as I feel = able to judge
would employ the _complete_ locale information = available for mapping
the complete input encoding (including latin-1, = latin-2 or whatever
else it is set to) to a canonical TeX encoding = (currently this would
probably mean T1, with Omega of course = Unicode).

The external locale information, however, would be = completely ignored
(except maybe for terminal output in some manner) = when the document
specified a locale itself.

That is: a TeX document with declared input encodings = should be
transferred as a binary.  A TeX document without = declared input
encodings should be transferred as a text file, with = all necessary
reencodings necessary to make it display correctly = when read under a
different locale.

That would make TeX behave correct as an application = as far as I can
see.  Of course, this exact behavior is, if at = all, not doable with
the current Web2C implementation: LaTeX has no way to = tell the input
machinery when it has detected it would want to = override any detected
locale information.  A TCX-file comment in the = first line of the file
would be some way to specify locale overrides, but it = is a way that
completely bypasses LaTeX and macro control.

--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
tex-implementors mailing list
postmaster@tug.org
http://tug.org/= mailman/listinfo/tex-implementors

------_=_NextPart_001_01C2C953.9DFF0680--