> If trim()'d element content is a popular option, I agree that a
> SAXBuilder option is warranted. (XMLFilter's are not easy to write.)
I think trim'd content would be popular (for example it's mandated that
servlet deployment descriptor web.xml files behave that way). As for
the filter, so long as it's possible for us to write one and it could
perform efficiently, it seems exposing the filter API would be a more
general purpose approach. Then we'd just provide a nice whitespace
stripping filter. Those are two big if's though. I'll need to do some
experimentation (unless someone beats me to it).
-jh-