[EMAIL PROTECTED] wrote: > Would it be possible for you to do this tonight Andy? I think I heard > something about you heading off on holiday after Friday; so I'm wondering
I started working on it but it's a very big change. And I noticed in the process that XMLDocumentFragmentHandler was not modified to include Augmentations. So I had to update that as well. But there are some additional API changes that I would like to make. First, I have a problem with the characters method in the XMLDTDHandler interface. Once I add the Augmentations parameter, it conflicts with the characters method in the XMLDocumentHandler interface. So this brings me to my point: I think that the methods in the various interfaces should NOT overlap, at least as little as possible. There are a number of methods that overlap among the interfaces. They are: characters, startEntity, textDecl, endEntity, processingInstruction, and comment. I can change the XMLDTDHandler#characters method to ignoredCharacters. That would take care of that case. And we could go further and change the startEntity and endEntity methods in the XMLDocumentHandler interface to more explicit, as well. For example: startGeneralEntity and endGeneralEntity. And then the XMLDTDHandler methods would be changed to start/endParameterEntity. But then the start of the DTD entity, which is passed as the entity name "[dtd]", would not make sense to be passed via the startGeneralEntity AND startParameterEntity methods. Which means that we would need additional methods in the DTD handler. For example: start/endExternalSubset. What do you think? -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
