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 f1FLrQH19988 for ; Thu, 15 Feb 2001 22:53:26 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1FLrQd12228 . for ; Thu, 15 Feb 2001 22:53:26 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09799.B93DCF00" 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 f1FLrPM13977 for ; Thu, 15 Feb 2001 22:53:25 +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 WAA06609 for ; Thu, 15 Feb 2001 22:53:25 +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 f1FLrOM13972 for ; Thu, 15 Feb 2001 22:53:25 +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 <15.8C4F9F65@mail.listserv.gmd.de>; Thu, 15 Feb 2001 22:53:16 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 489327 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 15 Feb 2001 22:53:21 +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 WAA22998 for ; Thu, 15 Feb 2001 22:53: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 WAA51446 for ; Thu, 15 Feb 2001 22:53:20 +0100 Received: from dcdrjh.fnal.gov (dcdrjh.fnal.gov [131.225.232.66]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1FLrLx05072 for ; Thu, 15 Feb 2001 22:53:21 +0100 (MET) Received: (from herber@localhost) by dcdrjh.fnal.gov (SGI-8.9.3/8.9.3) id PAA58904; Thu, 15 Feb 2001 15:53:11 -0600 (CST) References: Return-Path: Content-class: urn:content-classes:message Subject: Re: Side remarks about TeX input sequence Date: Thu, 15 Feb 2001 22:53:11 +0100 Message-ID: <200102152153.PAA58904@dcdrjh.fnal.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Randolph J. Herber" 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: 3947 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09799.B93DCF00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The following header lines retained to effect attribution: |Date: Thu, 15 Feb 2001 21:29:07 +0100 |From: Hans Aberg |Subject: Re: Side remarks about TeX input sequence |To: Multiple recipients of list LATEX-L |Reply-to: Mailing list for the LaTeX3 project = [BIG SNIP] |>From what I understand from VMS, one can set a file attributes to = provide |the desired translations. Thus, even if one writes a version where = files |are opened as binary, with say \n, \r, \r\n interpreted as newlines, = one |can set an attribute to provide the proper translation; or this was the |impression I got from Phillip Helbig's description. There are sysem utility programs to do such conversions and there are system services for a program to determine what the file attributes are and select an appropriate conversion to be done within the program. VMS supports all three of the stream line terminators. I wrote such a program about 6 years ago. Since VMS is not one of my major operating systems, I do not remember the small details. |-- 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. 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. 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. | Hans Aberg Randolph J. Herber, herber@fnal.gov, +1 630 840 2966, CD/CDFTF PK-149F, Mail Stop 318, Fermilab, Kirk & Pine Rds., PO Box 500, Batavia, IL = 60510-0500, USA. (Speaking for myself and not for US, US DOE, FNAL nor URA.) = (Product, trade, or service marks herein belong to their respective owners.) ------_=_NextPart_001_01C09799.B93DCF00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Side remarks about TeX input sequence

The following header lines retained to effect = attribution:
|Date: Thu, 15 Feb 2001 21:29:07 +0100
|From: Hans Aberg = <haberg@MATEMATIK.SU.SE>
|Subject: Re: Side remarks about TeX input = sequence
|To: Multiple recipients of list LATEX-L = <LATEX-L@URZ.UNI-HEIDELBERG.DE>
|Reply-to: Mailing list for the LaTeX3 project = <LATEX-L@URZ.UNI-HEIDELBERG.DE>

        [BIG = SNIP]

|>From what I understand from VMS, one can set a = file attributes to provide
|the desired translations. Thus, even if one writes a = version where files
|are opened as binary, with say \n, \r, \r\n = interpreted as newlines, one
|can set an attribute to provide the proper = translation; or this was the
|impression I got from Phillip Helbig's = description.

        There are = sysem utility programs to do such conversions and
        there are = system services for a program to determine what the
        file = attributes are and select an appropriate conversion to
        be done = within the program.  VMS supports all three of the
        stream = line terminators.

        I wrote = such a program about 6 years ago.  Since VMS is not
        one of my = major operating systems, I do not remember the
        small = details.

|-- 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.  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.

        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.

|  Hans Aberg

Randolph J. Herber, herber@fnal.gov, +1 630 840 2966, = CD/CDFTF PK-149F,
Mail Stop 318, Fermilab, Kirk & Pine Rds., PO Box = 500, Batavia, IL 60510-0500,
USA.  (Speaking for myself and not for US, US = DOE, FNAL nor URA.)  (Product,
trade, or service marks herein belong to their = respective owners.)

------_=_NextPart_001_01C09799.B93DCF00--