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 f1FNupH21714 for ; Fri, 16 Feb 2001 00:56:51 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1FNupd12842 . for ; Fri, 16 Feb 2001 00:56:51 +0100 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 f1FNuoM21000 for ; Fri, 16 Feb 2001 00:56:50 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C097AA.F6F72380" 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 AAA25455 for ; Fri, 16 Feb 2001 00:56: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 f1FNunM20991 for ; Fri, 16 Feb 2001 00:56:49 +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 <15.C9DDA980@mail.listserv.gmd.de>; Fri, 16 Feb 2001 0:56:41 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488085 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 16 Feb 2001 00:56:47 +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 AAA24083 for ; Fri, 16 Feb 2001 00:55:20 +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 AAA54100 for ; Fri, 16 Feb 2001 00:55:19 +0100 Received: from musse.tninet.se (musse.tninet.se [195.100.94.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1FNtIx03670 for ; Fri, 16 Feb 2001 00:55:18 +0100 (MET) Received: (qmail 29776 invoked from network); 16 Feb 2001 00:55:18 +0100 Received: from delenn.tninet.se (HELO algonet.se) (195.100.94.104) by musse.tninet.se with SMTP; 16 Feb 2001 00:55:18 +0100 Received: from [195.100.226.135] (du135-226.ppp.su-anst.tninet.se [195.100.226.135]) by delenn.tninet.se (BLUETAIL Mail Robustifier 2.2.1) with ESMTP id 565496.281316.982delenn-s2 for ; Fri, 16 Feb 2001 00:55:16 +0100 In-Reply-To: <200102152153.PAA58904@dcdrjh.fnal.gov> References: Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: Side remarks about TeX input sequence Date: Fri, 16 Feb 2001 00:34:47 +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: 3948 This is a multi-part message in MIME format. ------_=_NextPart_001_01C097AA.F6F72380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 15:53 -0600 2001/02/15, Randolph J. Herber wrote: >|-- Under UNIX, MacOS, or MSOS, binary files are not translated at all, = so >|if one does not make the right newline convention or translate the = files >|first by some other means, it will not work. > > It would if it were done along the lines I described previously > in this thread. It works for Adobe PostScript and in Sun Java; > that is enough examples to convince me that it can be done. Yes, and this is also my point. > I > do remember enough of the VMS work to realize that it would = only > be a page or so of code in VMS. In UNIX, it would be a few = lines. > I do not know enough about MacOS to offer a guess. The easiest way to implement it is to change the library functions that read files. In C, one can do it either by a macro in the program source code that changes the name of this file reading function to something = else, and the re-program it. Or one can simply add a file with the new version = -- modern compilers usually let new versions in source code override = library functions. This would work under UNIX/MacOS/MSOS with just a few lines. > A brief summary of the method: read the files adding line > terminators to record format files, if the operating system > supports such, and recognize all three line terminator > sequences and standardize them to one format. Under VMS, I understand it is more complicated, if th efile does not already have line terminators. Hans Aberg ------_=_NextPart_001_01C097AA.F6F72380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Side remarks about TeX input sequence

At 15:53 -0600 2001/02/15, Randolph J. Herber = wrote:
>|-- Under UNIX, MacOS, or MSOS, binary files are = not translated at all, so
>|if one does not make the right newline = convention or translate the files
>|first by some other means, it will not = work.
>
>        It = would if it were done along the lines I described previously
>        in = this thread.  It works for Adobe PostScript and in Sun Java;
>        that = is enough examples to convince me that it can be done.

Yes, and this is also my point.

>  I
>        do = remember enough of the VMS work to realize that it would only
>        be a = page or so of code in VMS.  In UNIX, it would be a few = lines.
>        I do = not know enough about MacOS to offer a guess.

The easiest way to implement it is to change the = library functions that
read files. In C, one can do it either by a macro in = the program source
code that changes the name of this file reading = function to something else,
and the re-program it. Or one can simply add a file = with the new version --
modern compilers usually let new versions in source = code override library
functions.

This would work under UNIX/MacOS/MSOS with just a few = lines.

>        A brief = summary of the method: read the files adding line
>        = terminators to record format files, if the operating system
>        = supports such, and recognize all three line terminator
>        = sequences and standardize them to one format.

Under VMS, I understand it is more complicated, if th = efile does not
already have line terminators.

  Hans Aberg

------_=_NextPart_001_01C097AA.F6F72380--