One further additional detail that wasn't apparent to me at first is that
the environmental variables described below are/may be set in your
autoexec.bat file.
Michael

Michael Fox
Head of Processing
Minnesota Historical Society
345 Kellogg Blvd West
St. Paul MN 55102-1906
phone: 651-296-1014
fax:  651-296-9961
[log in to unmask]
**NOTE NEW AREA CODE EFFECTIVE JULY 12, 1998**

> ----------
> From:         Pawson, David[SMTP:[log in to unmask]]
> Sent:         Friday, January 21, 2000 1:20 AM
> To:   [log in to unmask]
> Subject:      Re: XML Parsers
>
> >Can anybody recommend an XML parser?
> >
> >Thanks to a past recommendation from this listserv, we have very
> >successfully made use of SP Wizard, a freeware SGML parser which can be
> >downloaded from the WWW.  From what I understand, this parser
> >is basically
> >James Clark's SP parser, with a Visual Basic front end.  This
> >parser, once
> >set-up with a catalog file, has proven reliable and extremely
> >user friendly.
>
> Its also capable of parsing XML.
>
> Under Win32, it needs two other env vars setting,
> and a couple of additional parms and access to the
> XML declaration and catalog (supplied with nsgmls)
>
> HTH DaveP
>
> SET SP_CHARSET_FIXED=YES
> SET SP_ENCODING=XML
>
>
>
> NSGMLS.EXE -wxml -c pathto\xml.soc -f .\errs pathto\xml.dcl %1.xml >%1.op
> SET SP_ENCODING=ISO-8859-1
> SET SP_CHARSET_FIXED=NO
> MORE ERRS
>