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 f1EGorH02301 for ; Wed, 14 Feb 2001 17:50:53 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1EGord07069 . for ; Wed, 14 Feb 2001 17:50:53 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C096A6.4ACC1480" 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 f1EGoqM14648 for ; Wed, 14 Feb 2001 17:50:52 +0100 (MET) 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 RAA05602 for ; Wed, 14 Feb 2001 17:50:51 +0100 (MET) 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 f1EGopM14644 for ; Wed, 14 Feb 2001 17:50:51 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <0.1BEA4E61@mail.listserv.gmd.de>; Wed, 14 Feb 2001 17:50:40 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488932 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 14 Feb 2001 17:50:14 +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 RAA26438 for ; Wed, 14 Feb 2001 17:50:13 +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 RAA43530 for ; Wed, 14 Feb 2001 17:50:13 +0100 Received: from csc.albany.edu (sarah.albany.edu [169.226.1.103]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1EGo9x24609 for ; Wed, 14 Feb 2001 17:50:14 +0100 (MET) Received: from pluto.math.albany.edu (pluto.math.albany.edu [169.226.23.44]) by csc.albany.edu (8.9.3/8.9.3) with ESMTP id LAA14049 for ; Wed, 14 Feb 2001 11:49:34 -0500 (EST) Received: (from hammond@localhost) by pluto.math.albany.edu (8.9.3/8.9.3) id LAA27184 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Wed, 14 Feb 2001 11:49:33 -0500 (EST) Return-Path: Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Wed, 14 Feb 2001 17:49:33 +0100 Message-ID: <200102141649.LAA27184@pluto.math.albany.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "William F. Hammond" 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: 3924 This is a multi-part message in MIME format. ------_=_NextPart_001_01C096A6.4ACC1480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > However, I think the question is wrong. The right one is, > how many of the people on this list will use an editor which > can generate a utf-8 encoded file _within 4 or 5 years_? If you use an author friendly SGML document type with an encoding for your own locale, you can configure SP to (1) accept that and then (2), when you parse it for conversion to an xml version of the same document type, get UTF-8 output. The SGML document type could be made to accept special segments of direct UTF-8 for non-local material. (And the source can be made to look like LaTeX! :-) ) -- Bill ------_=_NextPart_001_01C096A6.4ACC1480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

> However, I think the question is wrong. The right = one is,
> how many of the people on this list will use an = editor which
> can generate a utf-8 encoded file _within 4 or 5 = years_?

If you use an author friendly SGML document type with = an encoding for
your own locale, you can configure SP to (1) accept = that and then (2),
when you parse it for conversion to an xml version of = the same
document type, get UTF-8 output.  The SGML = document type could be made
to accept special segments of direct UTF-8 for = non-local material.
(And the source can be made to look like LaTeX!  = :-) )

          &nbs= p;            = ;            =   -- Bill

------_=_NextPart_001_01C096A6.4ACC1480--