Received: by nummer-3.proteosys id <01C19443.4A777FEC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:07 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4A777FEC" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 x-to: latex-l@vm.urz.uni-heidelberg.de Content-class: urn:content-classes:message Subject: sgmls available Date: Mon, 28 Oct 1991 13:03:40 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rainer Schoepf" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 421 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4A777FEC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I thought this one would be interesting. I'll get that piece of software, in fact, I'm currently transferring it to Berlin. Rainer --------------original Usenet message-------------------- From: jjc@jclark.com (James Clark) Newsgroups: comp.text.sgml Subject: sgmls available Date: 28 Oct 91 11:05:44 GMT Distribution: comp Organization: None, London, England A beta-test version of sgmls, a SGML parser derived from the ARCSGML parser materials, is now available for anonymous ftp from ftp.uu.net as tmp/sgmls-0.3.tar.Z (about 250k), where it will stay for a few days. (If somebody would like to give it a more permanent home, that would be great.) Sgmls outputs a simple, line oriented, ASCII representation of a SGML document's Element Structure Information Set, which can easily be parsed by awk, perl, C or whatever. The idea is that sgmls can be used as the front end for a structure-controlled SGML application. It is primarily intended for Unix systems, but it works also on MS-DOS. I've tested it on the following architecture/OS/compiler combinations: sparc/SunOS 4.1.1/cc, sparc/SunOS 4.1.1/gcc, 386/SVR3.2/cc, 286/MS-DOS/Borland C++ 2.0. It should be straightforward to port to most systems that have 8-bit bytes and a character set consistent with ISO 646 IRV. I know of one bug that (arguably) prevents it from being fully conforming: documents are parsed and validated as though ``SHORTTAG YES'' was specified in the SGML declaration even if ``SHORTTAG NO'' was in fact specified. There are probably other bugs. If you report them to me, I will try to fix them. I aim to make sgmls fully conforming to ISO 8879. Suggestions for improvements and new features are also welcome. James Clark jjc@jclark.com ------_=_NextPart_001_01C19443.4A777FEC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable sgmls available

I thought this one would be interesting. I'll get that = piece of
software, in fact, I'm currently transferring it to = Berlin.

Rainer

--------------original Usenet = message--------------------
From: jjc@jclark.com (James Clark)
Newsgroups: comp.text.sgml
Subject: sgmls available
Date: 28 Oct 91 11:05:44 GMT
Distribution: comp
Organization: None, London, England

A beta-test version of sgmls, a SGML parser derived = from the ARCSGML
parser materials, is now available for anonymous ftp = from ftp.uu.net
as tmp/sgmls-0.3.tar.Z (about 250k), where it will = stay for a few
days.  (If somebody would like to give it a more = permanent home, that
would be great.)

Sgmls outputs a simple, line oriented, ASCII = representation of a SGML
document's Element Structure Information Set, which = can easily be
parsed by awk, perl, C or whatever.  The idea is = that sgmls can be
used as the front end for a structure-controlled SGML = application.

It is primarily intended for Unix systems, but it = works also on
MS-DOS.  I've tested it on the following = architecture/OS/compiler
combinations: sparc/SunOS 4.1.1/cc, sparc/SunOS = 4.1.1/gcc,
386/SVR3.2/cc, 286/MS-DOS/Borland C++ 2.0.  It = should be
straightforward to port to most systems that have = 8-bit bytes and a
character set consistent with ISO 646 IRV.

I know of one bug that (arguably) prevents it from = being fully
conforming: documents are parsed and validated as = though ``SHORTTAG
YES'' was specified in the SGML declaration even if = ``SHORTTAG NO''
was in fact specified.

There are probably other bugs.  If you report = them to me, I will try
to fix them.  I aim to make sgmls fully = conforming to ISO 8879.
Suggestions for improvements and new features are = also welcome.

James Clark
jjc@jclark.com

------_=_NextPart_001_01C19443.4A777FEC--