Greg Belenky wrote: > | To be fully honest, it's neither, but it certainly is not style. I > | wouldn't be happy saying it's content, but in the case of entities it > | can in fact contain part of the content. > > But it is content if you looking at with AxKit lens ;) > May be using something like AxDTDProvider will do the trick?
Yes, that's what I was pointing at. Not really content, but a dependency of content and thus attached to it. To be honest I would rather not see AxDTDProvider. For one it supports technology that deserves to be dragged outside and shot. Also there are other dependencies expressed in a variety of ways for other schema languages, RDDL, etc. Perhaps an AxCatalogProvider would be interesting though as it would be pluggable (for DTDs it'd have to use the PUBLICID of course -- there is already support for that in libxml, which may be an option in your case). I suspect that patches may be welcome. > | Do you need the DTD? Dropping the doctype off of the document ought to > | do the trick. It has often been observed that doing without DTDs > > DTD only have some entities - the HTML legacy... Yes, I've removed external > entities and placed DTD into the XML-document template. HTML legacy entities such as é and friends? Is there any reason why you still need them ? This is an honest question, I'm surprised they're still in use as I have to work with a lot of French content featuring accents in XML and threw the entities away three or four years ago, as soon as I could reliably use UTF-8 instead. Haven't seen them since. -- Robin Berjon <[EMAIL PROTECTED]> Research Engineer, Expway 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
