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 f1FF6fH15649 for ; Thu, 15 Feb 2001 16:06:41 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1FF6ed10921 . for ; Thu, 15 Feb 2001 16:06:40 +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 f1FF6e726811 for ; Thu, 15 Feb 2001 16:06:40 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09760.E6BA5680" 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 QAA10528 for ; Thu, 15 Feb 2001 16:06:40 +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 f1FF6dM12274 for ; Thu, 15 Feb 2001 16:06:39 +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.B989701A@mail.listserv.gmd.de>; Thu, 15 Feb 2001 16:06:31 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488947 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 15 Feb 2001 16:06:35 +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 QAA15296 for ; Thu, 15 Feb 2001 16:06:34 +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 QAA18324 for ; Thu, 15 Feb 2001 16:06:32 +0100 Received: from angel.algonet.se (angel.algonet.se [194.213.74.112]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1FF6Wx02662 for ; Thu, 15 Feb 2001 16:06:32 +0100 (MET) Received: (qmail 17260 invoked from network); 15 Feb 2001 16:06:30 +0100 Received: from delenn.tninet.se (HELO algonet.se) (195.100.94.104) by angel.algonet.se with SMTP; 15 Feb 2001 16:06:30 +0100 Received: from [195.100.226.147] (du147-226.ppp.su-anst.tninet.se [195.100.226.147]) by delenn.tninet.se (BLUETAIL Mail Robustifier 2.2.1) with ESMTP id 929651.249588.982delenn-s2 for ; Thu, 15 Feb 2001 16:06:28 +0100 In-Reply-To: References: Your message of "Thu, 15 Feb 2001 13:37:18 +0100." Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: Side remarks about TeX input sequence Date: Thu, 15 Feb 2001 16:05:28 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" 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: 3939 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09760.E6BA5680 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 12:41 +0000 2001/02/15, Robin Fairbairns wrote: >> No, you got it wrong: One can open a file as a text file or as binary = file: > >in fact, rainer (as one would expect, given his background) has got it >right. > >you (as always) are dragging irrelevancies into the discussion, and >adding nothing whatever to the discussion of the development of latex. Who has said it would bring anything to LaTeX? :-) -- I am interested in the question for Hugs and similar programs, and for writing my own = parsers (I write on a macro based formatting program right now): If there only = are the UNIX, MSOS & MacOS conventions available, one can open files as = binary and parse it as such, but otherwise you cannot. Are you claiming that if the files are input as binary, one does not have to worry about newlines one has in the internal representation? As for LaTeX, I recall that I can write a file that uses MacOS character encoding but which uses (say) UNIX newlines. Then Textures would not be able to read it (even if the file is only ASCII), whereas OzTeX can. -- My guess is that LaTeX is written to assume the one that ports TeX to the local OS does a local translation of line separators to whatever TeX = is used to have in its internals, and therefore you do not consider the newline input encoding issue a part of LaTeX. Hans Aberg ------_=_NextPart_001_01C09760.E6BA5680 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Side remarks about TeX input sequence

At 12:41 +0000 2001/02/15, Robin Fairbairns = wrote:
>> No, you got it wrong: One can open a file as = a text file or as binary file:
>
>in fact, rainer (as one would expect, given his = background) has got it
>right.
>
>you (as always) are dragging irrelevancies into = the discussion, and
>adding nothing whatever to the discussion of the = development of latex.

Who has said it would bring anything to LaTeX? :-) -- = I am interested in
the question for Hugs and similar programs, and for = writing my own parsers
(I write on a macro based formatting program right = now): If there only are
the UNIX, MSOS & MacOS conventions available, one = can open files as binary
and parse it as such, but otherwise you cannot. Are = you claiming that if
the files are input as binary, one does not have to = worry about newlines
one has in the internal representation?

As for LaTeX, I recall that I can write a file that = uses MacOS character
encoding but which uses (say) UNIX newlines. Then = Textures would not be
able to read it (even if the file is only ASCII), = whereas OzTeX can.

-- My guess is that LaTeX is written to assume the one = that ports TeX to
the local OS does a local translation of line = separators to whatever TeX is
used to have in its internals, and therefore you do = not consider the
newline input encoding issue a part of LaTeX.

  Hans Aberg

------_=_NextPart_001_01C09760.E6BA5680--