Re: [basex-talk] Shouldn't CHOP = false make xml:space="preserve" the default behavior?

2017-08-10 Thread Christian Grün
I agree that it might be reasonable to introduce different defaults for WebDAV communication. Problems could arise if documents are opened with WebDAV that have been stored via REST or another API… But we could give it a try. On Thu, Aug 10, 2017 at 11:28 PM, Andy Bunce wrote: > It seems globall

Re: [basex-talk] Shouldn't CHOP = false make xml:space="preserve" the default behavior?

2017-08-10 Thread Andy Bunce
It seems globally setting `indent=no` gets applied to WebDAV (and everywhere else where serialization is not explicit specified). This would be my preference for WebDAV, as it means documents can be round-tripped without any changes being introduced. The only side effect from this setting I have se

Re: [basex-talk] Shouldn't CHOP = false make xml:space="preserve" the default behavior?

2017-08-10 Thread Christian Grün
Hi Andy, > Can the WebDAV serialization be set independently of the default, in > web.xml? The defaults for whitespace chopping and serialization can only be assigned globally for all features of BaseX. Did you try to set both 'org.basex.chop' and 'org.basex.serializer' in web.xml / does it intro

Re: [basex-talk] Shouldn't CHOP = false make xml:space="preserve" the default behavior?

2017-08-10 Thread Andy Bunce
>But it may definitely cause undesirable output if a document contains no superfluous whitespaces, One situation where the default serialization indentation can be problematic is WebDAV. Can the WebDAV serialization be set independently of the default, in web.xml? /Andy On 7 August 2017 at 09:57

Re: [basex-talk] Shouldn't CHOP = false make xml:space="preserve" the default behavior?

2017-08-07 Thread Christian Grün
Dear Ottid, Thanks for providing us with the helpful example, which helped me to understand the problem. >> replace /a foo bar > "a.xml" (Line 1): Open quote is expected for attribute "xml:space" > associated with an element type "root". Just a side note: Command-line parsing is restrictive wh