Hi Elango,
changing the serialization parameters, here: output:separator option, [1] could
do the trick.
declare option output:separator \n;
let $s :=
interfaces
interface
nameintf0/name
/interface
interface
nameintf1/name
/interface
interface
On 2013-04-05, Michael Seiferle m...@basex.org wrote:
As chopping does not change any semantics (at least with regards to
what XML thinks of semantically important) but only aesthetics this is
enabled by default.
I'm sorry to disagree, but chopping certainly *does* change the
Hello Michael,
You are certainly right that with mixed content and the example you have
given here chopping does make a semantic difference.
However, you can disable this behaviour so BaseX does what you want. So the
only reason I see why one should change the default behaviour would be
because
Dirk,
On 2013-04-05, Dirk Kirsten d...@basex.org wrote:
You are certainly right that with mixed content and the example you have
given here chopping does make a semantic difference.
However, you can disable this behaviour so BaseX does what you want. So the
only reason I see why one should
Michael (other than me :-)) you are obviously right.
—
Mit freundlichen Grüßen
Michael Seiferle
On Fri, Apr 5, 2013 at 12:29 PM, Michael Piotrowski m...@cl.uzh.ch wrote:
Dirk,
On 2013-04-05, Dirk Kirsten d...@basex.org wrote:
You are certainly right that with mixed content and the example
http://www.w3.org/TR/REC-xml/#sec-white-space
...On the other hand, significant white space that should be preserved...
So since your parser by default creates significant whitespace where there was
none,
and removes it where there was, perhaps it could be fixed please, without the
user
needing
Dear Team,
Following is my query -
for $x in db:fulltext('Doc', 'Molecular Biology')/ancestor::*:Doc
return $x/ArticleNo
This query will return all the ArticleNo having the words Molecular
Biology
The output of this query is like a PHRASE... where the phrase is Molecular
Biology
Now I want
7 matches
Mail list logo
