Michael Sobolev mss@transas.com
Sat, 5 Sep 1998 01:01:23 +0400

On Fri, Sep 04, 1998 at 10:19:21PM +0200, Lars Marius Garshol wrote:
> >Basically, I need more documentation.  It is not obvious how to get all
> >defined elements, for example. 
> Not so strange, since you can't. :) Another thing I've been thinking about,
> but haven't yet added. It's just two or three lines, so I'll put it in in a
> couple of days. Expect it in the next release.
Well, with current version I can easily get all elements that are used for
defining root element, can't I?  For the most cases, it's sufficient.

> >And more examples, if possible.  :)
> Maybe I can add an example program that does something interesting with
> DTD information.
Yes, please.

> >    to obtain the list of public identifiers from catalog;
> Currently you can't. I'll add this.
This would be nice.

> >    to parse a specific DTD (using its public or system id);
> Hmmm. You can do this now by using the DTDParser class in the xmlproc
> module. Give it a DTDConsumer (see the DTD API doco) to receive events.
> I want to move the DTDParser and clean up the interface a little, so I
> haven't documented this yet, but the DTDParser understands the same
> methods as XMLProcessor, expcept that you set the DTD handler with
> 'set_dtd_consumer'. Note that this will break in a future version.
What I mean here is rather an example than functionality. :)