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 f1BHS0H11704 for ; Sun, 11 Feb 2001 18:28:00 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1BHS0d25711 . for ; Sun, 11 Feb 2001 18:28:00 +0100 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 f1BHRx717504 for ; Sun, 11 Feb 2001 18:27:59 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0944F.FAF41000" 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 SAA26459 for ; Sun, 11 Feb 2001 18:27:59 +0100 (MET) 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 f1BHRwM05615 for ; Sun, 11 Feb 2001 18:27:59 +0100 (MET) 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.CCDA48C4@mail.listserv.gmd.de>; Sun, 11 Feb 2001 18:27:49 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487664 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 11 Feb 2001 18:27:51 +0100 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 SAA23030 for ; Sun, 11 Feb 2001 18:27:49 +0100 (MET) 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 SAA35652 for ; Sun, 11 Feb 2001 18:27:50 +0100 Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1BHRnu18712 for ; Sun, 11 Feb 2001 18:27:49 +0100 (MET) Received: from [195.20.224.219] (helo=mrvdom03.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 14S0Ht-00037f-00 for LATEX-L@urz.uni-heidelberg.de; Sun, 11 Feb 2001 18:27:49 +0100 Received: from manz-3e365958.pool.mediaways.net ([62.54.89.88] helo=istrati.zdv.uni-mainz.de) by mrvdom03.kundenserver.de with esmtp (Exim 2.12 #2) id 14S0Hm-0000MI-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 11 Feb 2001 18:27:42 +0100 Received: (from latex3@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id SAA12258; Sun, 11 Feb 2001 18:25:41 +0100 In-Reply-To: References: <14982.45082.150652.74719@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: VM 6.75 under Emacs 20.4.1 X-Authentication-Warning: istrati.zdv.uni-mainz.de: latex3 set sender to frank@mittelbach-online.de using -f Content-class: urn:content-classes:message Subject: Re: LaTeX's internal char prepresentation (UTF8 or Unicode?) Date: Sun, 11 Feb 2001 18:25:41 +0100 Message-ID: <14982.51989.349221.285820@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" 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: 3804 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0944F.FAF41000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Roozbeh, > I have yet to > > see that UTF8 text (without taking precaution and externally = announcing that a > > file is in UTF8) is really properly handled by any OS platform. Is = it? > > Windows 2000 autodetects them. I can't define the proper handling in = Linux > well; you mean in a text editor? no i mean at the system level. what do you mean by windows2000 = autodetects them? my understanding of what UTF8 means as a format is that you can't autodetect it. As best you can detect that something is not UTF8, but = how do you want to detect it as being in that format and not in, say, a file = written with an 8bit inputencoding which happens to just contain an 8bit stream = which is by chance also conforming to the UTF8 spec? frank ------_=_NextPart_001_01C0944F.FAF41000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX's internal char prepresentation (UTF8 or = Unicode?)

Roozbeh,

 > I have yet to
 > > see that UTF8 text (without taking = precaution and externally announcing that a
 > > file is in UTF8) is really properly = handled by any OS platform. Is it?
 >
 > Windows 2000 autodetects them. I can't = define the proper handling in Linux
 > well; you mean in a text editor?

no i mean at the system level. what do you mean by = windows2000 autodetects
them? my understanding of what UTF8 means as a format = is that you can't
autodetect it. As best you can detect that something = is not UTF8, but how do
you want to detect it as being in that format and not = in, say, a file written
with an 8bit inputencoding which happens to just = contain an 8bit stream which
is by chance also conforming to the UTF8 spec?

frank

------_=_NextPart_001_01C0944F.FAF41000--