Actually, that's a good point. The tags are on different lines, not a single line, so maybe that's what they consider indented!?!?
Given the fact that the processor cannot know whitespace is not significant, maybe it's even a better behavior. It's OK to 'indent' that way for XML to be consumed by an XSL stylesheet for example, but for generating XML to be potentially read by humans, the lack of real indenting (nested tag offset from parent tag) is problematic. Maybe the real answer is to adapt Ant's DOMElementWriter code to allow outputting directly (instead of requiring a DOM tree), and leverage the logic there to escape invalid characters... --DD -----Original Message----- From: [EMAIL PROTECTED] To: Ant Developers List Sent: 12/19/2003 5:35 AM Subject: RE: Bug 25564 - CVS tagdiff does not escape XML characters > I noticed though that with JDK 1.4.2, even when requesting indenting, > the resulting file is not indented :-( I have found this to be very implementation dependent, with the version I used, not setting the indent put every thing on a single line. I'll have to have a look at the xalan/xerces source code to see what is going on. Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
