[jdom-interest] Debugging Output

Kenworthy, Edward edward.kenworthy at exchange.co.uk
Thu Jun 14 00:46:10 PDT 2001

What would be really useful for debugging would be if JDom could be
persuaded to output its XML in a more user-friendly manner. The current
format is basically unreadable for a human, sure it's correct but that
doesnt help with debugging.

-----Original Message-----
From: philip.nelson at omniresources.com
[mailto:philip.nelson at omniresources.com]
Sent: 13 June 2001 22:03
To: jhunter at collab.net; philip.nelson at omniresources.com
Cc: jdom-interest at jdom.org
Subject: RE: [jdom-interest] Questions regarding implementation of
DocTyp e.internalSubset[eg]

> > * what to do (if anything) about character entities in the 
> source doc like
> >   <!ENTITY Ouml '&#214;'>
> > 
> > The parser turns this into a String from the parsed entity 
> and that is what
> > gets output.
> Try to create a string as close to the original as possible.

I think all the other questions have been addressed and I agree with the
conclusions from Jason and Harry.  This one is not so easy.  The problem is,
we have no way of knowing whether the original data came from a character
entity or not.  The parser doesn't report this in any way I could find. we
just get a Unicode string. 

Harry, off the top of my head, I have modified DocType, XMLOutputter,
SAXBuilder and SAXHandler.  None of this is in CVS.  I'll send you what I
have tonight and if you could do the same, we may save a few steps.  My code
seemed to work pretty well except for the issues I have brought up. 

Could you send yours?
To control your jdom-interest membership:

More information about the jdom-interest mailing list