...because I didn't (personally) know to what character · should resolve. :-)
-----Original Message----- From: Arnaud Le Hors [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2001 8:27 PM To: [EMAIL PROTECTED] Subject: Re: unsupported characters in Xerces "Swanson, Brion" wrote: > > One hack solution to this particular problem is to define the entity in > question (·) so that the parser evaluates it as: &middot; This > is the more difficult way. > > A simpler solution (in some respects) is to simply replace all instances of > · in the input XML with &middot; which will resolve the & > into your '&', but won't break the parser. I agree these will make the parser happy, but why not simply fix the problem?? All you need is to define this entity. Simply add: <!ENTITY middot "·"> to the internal subset. -- Arnaud Le Hors - IBM Cupertino, XML Strategy Group --------------------------------------------------------------------- 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]
