All system id's passes through the entity resolver before the parser does the default search. You can thereby hijack any url and redirect the parser to another location. And YES all children to the DTD must also be resolved properly. But if you use the path functionality in my resolver all that is handled automaticly as long as you do not have duplicates in the search path.
/ Erik -----Original Message----- From: Ing. Hans Pesata [mailto:[EMAIL PROTECTED]] Sent: den 14 maj 2002 15:50 To: [EMAIL PROTECTED] Subject: AW: DTD-/XML-location Hi ! // You will have to implement a entity resolver. // Write one and plug it into the parser. // // What the hell... You can have mine :) // Written for Win32. It implements direct match entities, search paths and // even DTD's in application resource. Thanx a lot for your help ! I understand that this EntityResolver is called by the parser in case it cant find an entity (e.g. a DTD) and uses it to provide the full path ?! I am also using sub-DTDs within my main-DTD, I suppose I have to resolve these ones too. Best regards, Hans Pesata --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
