That's too bad. For those unfamiliar with Xalan, they will not understand the behavior. Furthermore, they might not even understand that the processing is being done by Xalan in their particular application; Xalan may be hidden within a larger application/system.
In either case, a user who sets "indent='yes'", and gets only line breaks and not actual "indentation" will just assume the feature is not implemented or is defective (hence the bug report and my assumption likewise). It never occurred to me to look for an implementation specific attribute to achieve the expected result. It is unfortunate that the spec says the default indent value for HTML is "yes". I would rather see this default to "no" and have the default indent-amount > 0. Thus, when someone explicitly sets indent to "yes", they get expected behavior, without impacting performance in the default case. I believe default behavior should favor usability, with settings to tune for performance, rather than the reverse (imho). Ok, nuf said. Thanks for bringing me up to date. Regards, Brian Atkins "Voytenko, Dimitry" wrote: > > Hi Brian, > > There was some discussion and it was decided that such behaviour is OK since > XSLT specification doesn't set any specific rules for indenting. It just > says: > <quot> > If the indent attribute has the value yes, then the xml output method may > output whitespace in addition to the whitespace in the result tree > </quot> > Xalan actually adds whitespaces, but only line breaks by default because of > performance issues. > > Thanks, > Dmitry > -- Brian Atkins [EMAIL PROTECTED] (970) 288-2114 Agilent Technologies 4800 Wheaton Drive Ft. Collins, CO 80525
