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 f5BJ7Kf13685 for ; Mon, 11 Jun 2001 21:07:20 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f5BJ7Jp28316 . for ; Mon, 11 Jun 2001 21:07:19 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F2A9.BCF5E400" 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 f5BJ7I002120 for ; Mon, 11 Jun 2001 21:07:18 +0200 (MET DST) 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 VAA00901 for ; Mon, 11 Jun 2001 21:07:18 +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 f5BJ7IU19981 for ; Mon, 11 Jun 2001 21:07:18 +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 <4.A0609ABD@mail.listserv.gmd.de>; Mon, 11 Jun 2001 21:04:54 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 498160 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 11 Jun 2001 21:07:14 +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 VAA21057 for ; Mon, 11 Jun 2001 21:07:13 +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 VAA107744 for ; Mon, 11 Jun 2001 21:07:14 +0200 Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5BJ7E123974 for ; Mon, 11 Jun 2001 21:07:14 +0200 (MET DST) Received: from wing6.herald.ox.ac.uk ([163.1.0.230] ident=exim) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #3) id 159X1k-0007io-00 for LATEX-L@urz.uni-heidelberg.de; Mon, 11 Jun 2001 20:07:04 +0100 Received: from httpd by wing6.herald.ox.ac.uk with local (Exim 2.02 #1) id 159X1k-0002M7-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Mon, 11 Jun 2001 20:07:04 +0100 Return-Path: X-Mailer: MIME-tools 4.103 (Entity 4.115) Content-class: urn:content-classes:message Subject: Re: \InputTranslation Date: Mon, 11 Jun 2001 20:07:04 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Sebastian Rahtz" 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: 4128 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0F2A9.BCF5E400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In message Mailing list = for the LaTeX3 project = writes: > At 16:06 +0100 2001/06/11, Sebastian Rahtz wrote: > >Any XML tool is mandated to handle UTF-8, fwiw. > > The main thing is that you are sure that Unicode editors supports = UTF8. If > you are sure of that, then perhaps support for other Unicode encodings = will > not be needed. I'd be surprised at a Unicode tool that didnt do UTF8. not impossible, = but unusual > But past experience has shown that it is difficult to dictate what = people > will use, so perhaps there pop up other favored formats than just = UTF8. sure. its easier to move between them, anyway sebastian ------_=_NextPart_001_01C0F2A9.BCF5E400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \InputTranslation

In message  = <v03110702b74ab27d2396@[195.100.226.135]>     = Mailing list for the LaTeX3 = project           =    <LATEX-L@URZ.UNI-HEIDELBERG.DE> writes:

> At 16:06 +0100 2001/06/11, Sebastian Rahtz = wrote:
> >Any XML tool is mandated to handle UTF-8, = fwiw.
>
> The main thing is that you are sure that Unicode = editors supports UTF8. If
> you are sure of that, then perhaps support for = other Unicode encodings will
> not be needed.
I'd be surprised at a Unicode tool that didnt do = UTF8. not impossible, but unusual


> But past experience has shown that it is = difficult to dictate what people
> will use, so perhaps there pop up other favored = formats than just UTF8.

sure. its easier to move between them, anyway



sebastian

------_=_NextPart_001_01C0F2A9.BCF5E400--