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 f1E9woH30997 for ; Wed, 14 Feb 2001 10:58:50 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1E9wod05508 . for ; Wed, 14 Feb 2001 10:58:50 +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 f1E9wo717470 for ; Wed, 14 Feb 2001 10:58:50 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0966C.BABDA900" 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 KAA10351 for ; Wed, 14 Feb 2001 10:58:49 +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 f1E9wmM04632 for ; Wed, 14 Feb 2001 10:58:48 +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 <1.8DDFFC69@mail.listserv.gmd.de>; Wed, 14 Feb 2001 10:58:41 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488076 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 14 Feb 2001 10:58:45 +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 KAA16922 for ; Wed, 14 Feb 2001 10:58:44 +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 KAA30560 for ; Wed, 14 Feb 2001 10:58:44 +0100 Received: from server-12.tower-4.starlabs.net (mail.london-1.starlabs.net [212.125.75.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1E9wiV26721 for ; Wed, 14 Feb 2001 10:58:44 +0100 (MET) Received: (qmail 26526 invoked from network); 14 Feb 2001 09:55:44 -0000 Received: from nagmx1e.nag.co.uk (HELO nag.co.uk) (62.232.54.130) by server-12.tower-4.starlabs.net with SMTP; 14 Feb 2001 09:55:44 -0000 Received: from penguin.nag.co.uk (IDENT:root@penguin.nag.co.uk [192.156.217.14]) by nag.co.uk (8.9.3/8.9.3) with ESMTP id JAA01449 for ; Wed, 14 Feb 2001 09:58:39 GMT Received: by penguin.nag.co.uk (8.9.3) id JAA01211; Wed, 14 Feb 2001 09:58:13 GMT In-Reply-To: <200102132036.PAA23861@pluto.math.albany.edu> (hammond@CSC.ALBANY.EDU) References: <200102132036.PAA23861@pluto.math.albany.edu> Return-Path: X-VirusChecked: Checked Content-class: urn:content-classes:message Subject: Re: Side remarks about TeX input sequence Date: Wed, 14 Feb 2001 10:58:13 +0100 Message-ID: <200102140958.JAA01211@penguin.nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" 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: 3915 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0966C.BABDA900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > So provide a front-end filter for converting UTF-16 to a better > multibyte format. well no I won't because there are already 1001 good converters freely available already. I agree that since its easy to convert that it isn't = a real problem in practice. Mainly its a problem for _me_ as I can't call xmltex an XML parser because the XML spec mandates utf16 support. (Apart from bugs, of which there are probably some) I believe xmltex does implement all the productions in the XML spec that are required of a non validating parser. With the exception of this TeX behaviour of removing spaces at ends of lines, which affects white space normalisation and utf16 support. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet = delivered through the MessageLabs Virus Control Centre. For further information = visit http://www.star.net.uk/stats.asp ------_=_NextPart_001_01C0966C.BABDA900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Side remarks about TeX input sequence

> So provide a front-end filter for converting = UTF-16 to a better
> multibyte format.

well no I won't because there are already 1001 good = converters freely
available already. I agree that since its easy to = convert that it isn't a
real problem in practice. Mainly its a problem for = _me_ as I can't call
xmltex an XML parser because the XML spec mandates = utf16 support.
(Apart from bugs, of which there are probably some) I = believe xmltex
does implement all the productions in the XML spec = that are required of
a non validating parser. With the exception of this = TeX behaviour of
removing spaces at ends of lines, which affects white = space
normalisation and utf16 support.

David

________________________________________________________________= _____
This message has been checked for all known viruses = by Star Internet delivered
through the MessageLabs Virus Control Centre. For = further information visit
http://www.star.net.uk/stats.as= p

------_=_NextPart_001_01C0966C.BABDA900--