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 f5AMLqf03812 for ; Mon, 11 Jun 2001 00:21:52 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f5AMLqp22615 . for ; Mon, 11 Jun 2001 00:21:52 +0200 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f5AMLp011632 for ; Mon, 11 Jun 2001 00:21:51 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F1FB.BF9A0000" 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 AAA06117 for ; Mon, 11 Jun 2001 00:21:51 +0200 (MEST) 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 f5AMLpU18564 for ; Mon, 11 Jun 2001 00:21:51 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <2.A4EBB2E8@mail.listserv.gmd.de>; Mon, 11 Jun 2001 0:19:29 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 496786 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 11 Jun 2001 00:21:47 +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 AAA09857 for ; Mon, 11 Jun 2001 00:21:46 +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 AAA104570 for ; Mon, 11 Jun 2001 00:21:47 +0200 Received: from mail.umu.se (custer.umdac.umu.se [130.239.8.14]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5AMLk100439 for ; Mon, 11 Jun 2001 00:21:46 +0200 (MET DST) Received: from [130.239.137.13] (mariehemsv093.sn.umu.se [130.239.137.13]) by mail.umu.se (8.8.8/8.8.8) with ESMTP id AAA23306 for ; Mon, 11 Jun 2001 00:21:46 +0200 (MET DST) In-Reply-To: <15139.58926.526127.21111@localhost.localdomain> References: <15119.62808.151690.192812@gargle.gargle.HOWL> Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id AAA09859 Content-class: urn:content-classes:message Subject: Re: \InputTranslation Date: Sun, 10 Jun 2001 23:21:45 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= 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: 4121 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0F1FB.BF9A0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 23.27 +0200 2001-06-10, Marcel Oliver wrote: >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? I think Chris's original question was essentially "Can we use a = different method for encoding `language' information in internal files than in = files that are meant to be read by other programs?" and my reply was then "I don't think there are files that are that internal." For an underlying engine (e.g. Omega) that can primitively handle UTF-8 I/O, I believe we agreed that this would be the preferable way of encoding the = _characters_. Lars Hellstr=F6m ------_=_NextPart_001_01C0F1FB.BF9A0000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \InputTranslation

At 23.27 +0200 2001-06-10, Marcel Oliver wrote:
>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?

I think Chris's original question was essentially = "Can we use a different
method for encoding `language' information in = internal files than in files
that are meant to be read by other programs?" = and my reply was then "I
don't think there are files that are that = internal." For an underlying
engine (e.g. Omega) that can primitively handle UTF-8 = I/O, I believe we
agreed that this would be the preferable way of = encoding the _characters_.

Lars Hellstr=F6m

------_=_NextPart_001_01C0F1FB.BF9A0000--