DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15007>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15007 & to &amp ------- Additional Comments From [EMAIL PROTECTED] 2003-06-11 18:20 ------- I'm not sure what you want the parser to be doing. 'amp' is a predefined entity whose replacement text is '&'. Even if you use a reference to amp in an (general) entity declaration, the parser will only expand it when the enclosing entity is expanded. For example, consider these two entity declarations: <!ENTITY one "&"> <!ENTITY two "&amp;"> When referenced in content, 'one' expands to '&', and 'two' expands to '&'. The parser doesn't futher expand this. It is the replacement text. When the parser serializes a text node, it has to replace each '&' with a '&' reference. It can't assume that the occurence of & in a text node should be left as is. Once the DOM is constructed from a document, all entity and character reference replacement has taken place. So even if you hand craft your own document in memory using DOM's factory methods (createTextNode, etc...), they'll be interpreted as if all entity and character references have already been replaced. Adding a feature to the serializer which leaves & as & doesn't seem reasonable me. The behaviour seems to be non-compliant. If I misinterpreted your request, could you please clarify? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
