Thank you Dominique, Matt & Michael for your responses.
For the time being I simply wrapped the text inside tags
(since I'm trying to generate a time html file). I did not have any
special styles for the spans in the document, so this serves my
purpose for now.
I will look into details of the xs
On Fri, Apr 8, 2011 at 2:57 PM, Matt Benson wrote:
>> So yeah, I'm afraid it's by design... A proper was need
>> access to the full infoset provided by the parser, and thus require
>> deeper changes into Ant core to provide that infoset. --DD
>
> EchoXML has, I'm afraid, been a largely unsuccessf
On Fri, Apr 8, 2011 at 1:49 PM, Dominique Devienne wrote:
> On Fri, Apr 8, 2011 at 11:10 AM, Parag Doke
> wrote:
>> Notice that the "text outside the child node" appears before the child
>> node itself, though it was after the child node in the original input to
>> echoxml task.
>
> I vaguely r
On Fri, Apr 8, 2011 at 11:10 AM, Parag Doke wrote:
> Notice that the "text outside the child node" appears before the child
> node itself, though it was after the child node in the original input to
> echoxml task.
I vaguely recall that when I wrote (Stefan is the one who
introduced it into Ant
Parag Doke schrieb am 08.04.2011 um 21:40 (+0530):
> Hello ant experts.
> I am trying to use the echoxml task in ant (1.7 / 1.8) but have
> observed a weird thing about the node text.
> Notice that the "text outside the child node" appears before the child
> node itself, though it was after the ch
Hello ant experts.
I am trying to use the echoxml task in ant (1.7 / 1.8) but have
observed a weird thing about the node text. Here is my project file
===
text inside the child node
text outside the child node
===
What I can see in the test_output.xml is:
==
