Though I think "CHOP" defaulting to true is a bug compared to the expected behaviour of XML.
And while it's very useful to have CHOP there for some kinds of data, for other kinds it's a severe hazard that it's the default. People have major freakouts when their documentation XML documents look like they've lost the white spaces around bold tags and will have nothing to do with BaseX thereafter.
-- Graydon
On Wed, Mar 26, 2014 at 1:08 PM, Dirk Kirsten dk@basex.org wrote:
Sorry, mail was supposed to be send to the mailing list... Information is the same as in Leos mail
-------- Original Message -------- Subject: Re: [basex-talk] whitespaces in import Date: Wed, 26 Mar 2014 17:59:12 +0100 From: Dirk Kirsten dk@basex.org To: Stefan Sechelmann sechel@math.tu-berlin.de
Hello Stefan,
On 26/03/14 17:51, Stefan Sechelmann wrote: Is there some kind of whitespace normalization
going on during import?
Yes, it is.
Can I set options that influence this behavior or is this a bug?
Yes, you can. Set the CHOP option to false (see https://docs.basex.org/wiki/Options#CHOP for details) or start BaseX with the -w flag (which sets CHOP to false).
Hope that helps.
Cheers, Dirk
-- Dirk Kirsten, BaseX GmbH, http://basex.org |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk