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 f4DJcSf17734 for ; Sun, 13 May 2001 21:38:28 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f4DJcR717360 . for ; Sun, 13 May 2001 21:38:27 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0DBE4.48655200" 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 f4DJcRU04222 for ; Sun, 13 May 2001 21:38:27 +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 VAA06358 for ; Sun, 13 May 2001 21:38:26 +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 f4DJcQU04218 for ; Sun, 13 May 2001 21:38:26 +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 <0.482F4CA0@mail.listserv.gmd.de>; Sun, 13 May 2001 21:36:49 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 495368 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 13 May 2001 21:38:23 +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 VAA05511 for ; Sun, 13 May 2001 21:38:21 +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 VAA23998 for ; Sun, 13 May 2001 21:38:21 +0200 Received: from smtp.wanadoo.es (m1smtpisp03.wanadoo.es [62.36.220.63] (may be forged)) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f4DJcLQ17119 for ; Sun, 13 May 2001 21:38:21 +0200 (MET DST) Received: from [62.36.81.99] (62-36-81-99.dialup.uni2.es [62.36.81.99]) by smtp.wanadoo.es (8.10.2/8.10.2) with ESMTP id f4DJcHi26759 for ; Sun, 13 May 2001 21:38:18 +0200 (MET DST) Return-Path: X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.2 Date: Sun, 13 May 2001 21:34:54 +0100 Message-ID: <200105131938.f4DJcHi26759@smtp.wanadoo.es> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Javier Bezos" 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: 4053 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0DBE4.48655200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I wrote: > Further, by doing so we are creating again a closed system > using its own conventions with no links with external tools adapted > to Unicode. I will be able to process a file and extract information > from it with, say, Python very easily if they use a known = representation > (iso encodings or Unicode), but if we have to parse things like = \japaneseai > or similar, things become more difficult. I think it's a lot easier > moving information with blocks of text and not with single chars. :-/ It seems I've given a good argument against what I'm upholding... = (at least in part) Javier ------_=_NextPart_001_01C0DBE4.48655200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.2

I wrote:

> Further, by doing so we are creating again a = closed system
> using its own conventions with no links with = external tools adapted
> to Unicode. I will be able to process a file and = extract information
> from it with, say, Python very easily if they = use a known representation
> (iso encodings or Unicode), but if we have to = parse things like \japaneseai
> or similar, things become more difficult.  = I think it's a lot easier
> moving information with blocks of text and not = with single chars.

:-/ It seems I've given a good argument against what = I'm upholding... (at
least in part)

Javier

------_=_NextPart_001_01C0DBE4.48655200--