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 f5ALSVf03153 for ; Sun, 10 Jun 2001 23:28:31 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f5ALSVp22105 . for ; Sun, 10 Jun 2001 23:28:31 +0200 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 f5ALSUU16128 for ; Sun, 10 Jun 2001 23:28:30 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F1F4.4BA82980" 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 XAA27118 for ; Sun, 10 Jun 2001 23:28:30 +0200 (MEST) 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 f5ALSTU16124 for ; Sun, 10 Jun 2001 23:28:30 +0200 (MET DST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <13.3093F727@mail.listserv.gmd.de>; Sun, 10 Jun 2001 23:26:07 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 497282 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 10 Jun 2001 23:28:26 +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 XAA09209 for ; Sun, 10 Jun 2001 23:28:24 +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 XAA42542 for ; Sun, 10 Jun 2001 23:28:25 +0200 Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5ALSO110791 for ; Sun, 10 Jun 2001 23:28:24 +0200 (MET DST) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 159Cky-0004Pg-00 for LATEX-L@urz.uni-heidelberg.de; Sun, 10 Jun 2001 23:28:24 +0200 Received: from b0e61.pppool.de ([213.7.14.97] helo=localhost.localdomain) by mx3.freenet.de with esmtp (Exim 3.22 #2) id 159Cky-0008Oa-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 10 Jun 2001 23:28:24 +0200 Received: (from marcel@localhost) by localhost.localdomain (8.11.2/8.11.2) id f5ALRAe01955; Sun, 10 Jun 2001 23:27:10 +0200 In-Reply-To: References: <15119.62808.151690.192812@gargle.gargle.HOWL> Return-Path: X-Mailer: VM 6.92 under Emacs 20.7.1 Content-class: urn:content-classes:message Subject: Re: \InputTranslation Date: Sun, 10 Jun 2001 22:27:10 +0100 Message-ID: <15139.58926.526127.21111@localhost.localdomain> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Marcel Oliver" 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: 4119 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0F1F4.4BA82980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Lars =3D?iso-8859-1?Q?Hellstr=3DF6m?=3D writes: > At 14.29 +0200 2001-06-05, Chris Rowley wrote: > >1. How should LICR strings be written out to files used only by = LaTeX > > itself? In the LICR, everything else will be a big mess... so UTF8 if the LICR is Unicode. > Are there technically any such files today? BibTeX reads .aux files. > Copying and editing the contents of .toc, .lof, etc. files is an > established (although maybe not kosher) method for finetuning the = table of > contents and such. I don't think this means we have to support arbitrary encodings of auxiliary files. Editing such files is, after all, undocumented practice, and using an UTF8 editor will (rather elegantly) provide full access to these files. Do we need more? Marcel ------_=_NextPart_001_01C0F1F4.4BA82980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \InputTranslation

Lars =3D?iso-8859-1?Q?Hellstr=3DF6m?=3D writes:
 > At 14.29 +0200 2001-06-05, Chris Rowley = wrote:
 > >1.  How should LICR strings be = written out to files used only by LaTeX
 > >    itself?

In the LICR, everything else will be a big mess... so = UTF8 if the LICR
is Unicode.

 > Are there technically any such files today? = BibTeX reads .aux files.
 > Copying and editing the contents of .toc, = .lof, etc. files is an
 > established (although maybe not kosher) = method for finetuning the table of
 > contents and such.

I don't think this means we have to support arbitrary = encodings of
auxiliary files.  Editing such files is, after = all, undocumented
practice, and using an UTF8 editor will (rather = elegantly) provide
full access to these files.  Do we need = more?

Marcel

------_=_NextPart_001_01C0F1F4.4BA82980--