Re: [basex-talk] bug (?) in fn:serialize

Thanks, Alexander and everybody for your remarks and observations. As it happens, in the meantime I've found the reason: it is the boundary-space policy, which can either be "preserve" or "strip" and which a boundary-space declaration of the prolog can explicitly choose (overriding the

Re: [basex-talk] bug (?) in fn:serialize

... just checked. When the node is from a document instance than serialize does keep whitespace (with or without xml:space). And this clears up a confusion I had about what an element constructor is and what a direct element constructor is. For fun I tried serialize(element e { ' ' }) which

Re: [basex-talk] bug (?) in fn:serialize

> On 08.09.2016, at 23:17, Hans-Juergen Rennau wrote: > > Dear BaseX team, > > is this a bug? > > serialize( ) > > returns > > > > I need my blanks! > > Hans-Jürgen Maybe your data is stored/processed with whitespaces stripped off?

Re: [basex-talk] bug (?) in fn:serialize

It seems to be a problem with elements containing only whitespace characters: serialize( Demonstrating the CHOP flag To be , or not to be dasdf , that is the question. ) Tags work as expected, but Tags will be stripped to the empty element . Maybe this has to do with

Re: [basex-talk] bug (?) in fn:serialize

Hmm first I thought not a bug and that the fix would be to do serialize( ) but to my surprise this results in (with CHOP = false) That doesn't seem right. Whereas serialize() does what you expect. --Marc