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 f1DDpLH25919 for ; Tue, 13 Feb 2001 14:51:21 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1DDpKd01492 . for ; Tue, 13 Feb 2001 14:51:20 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C095C4.0BC59280" 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 f1DDpKM17953 for ; Tue, 13 Feb 2001 14:51:20 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id OAA06882 for ; Tue, 13 Feb 2001 14:51:19 +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 mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1DDpJ701499 for ; Tue, 13 Feb 2001 14:51:19 +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 <2.DF1FA79D@mail.listserv.gmd.de>; Tue, 13 Feb 2001 14:51:12 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488176 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 13 Feb 2001 14:51:07 +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 OAA01803 for ; Tue, 13 Feb 2001 14:51:06 +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 OAA19960 for ; Tue, 13 Feb 2001 14:51:06 +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 f1DDp0g13810 for ; Tue, 13 Feb 2001 14:51:00 +0100 (MET) Received: from hilbert.math.albany.edu (hilbert.math.albany.edu [169.226.23.52]) by csc.albany.edu (8.9.3/8.9.3) with ESMTP id IAA19760 for ; Tue, 13 Feb 2001 08:50:26 -0500 (EST) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.9.3/8.9.3) id IAA05912 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Tue, 13 Feb 2001 08:50:26 -0500 (EST) Return-Path: Content-class: urn:content-classes:message Subject: Re: LaTeX's internal char prepresentation (UTF8 or Unicode?) Date: Tue, 13 Feb 2001 14:50:26 +0100 Message-ID: <200102131350.IAA05912@hilbert.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: 3875 This is a multi-part message in MIME format. ------_=_NextPart_001_01C095C4.0BC59280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I could quote Frank's response to Sebastian, but I won't. The question lingers, however, as to whether we view xml as off topic here. On the one hand, xmltex is something that runs through LaTeX, and, on the other hand, if xml is a presence, it changes the package writing scene inasmuch as some of the things that people get from packages can be provided (sometimes better) before regular LaTeX action begins. I know that there were lots of bad early experiences that some had with sgml. It need not be that way. -- Bill ------_=_NextPart_001_01C095C4.0BC59280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX's internal char prepresentation (UTF8 or = Unicode?)

I could quote Frank's response to Sebastian, but I = won't.

The question lingers, however, as to whether we view = xml as off topic
here.  On the one hand, xmltex is something that = runs through LaTeX,
and, on the other hand, if xml is a presence, it = changes the package
writing scene inasmuch as some of the things that = people get from
packages can be provided (sometimes better) before = regular LaTeX
action begins.

I know that there were lots of bad early experiences = that some had
with sgml.  It need not be that way.

          &nbs= p;            = ;            =   -- Bill

------_=_NextPart_001_01C095C4.0BC59280--