Sorry it was not clear... did you try the source XML and XSL in Xalan? The
version with the bug is Xalan2, it works as expected in Xalan1.2. - you
should be able to see the problem if you try the sample transformation I
provided with Xalan2.

The browser is IE5.

There is a bug in the rendering of  this kind of XML source:
<span class="test">This is line 1.&lt;br&gt;&lt;/br&gt;This is line
2.</span>

This should output to the browser:
This is line 1<br></br>This is line 2.
-- in the font characteristics laid out in the class "test"

It does this in Xalan 1.2, but in Xalan 2 it outputs to the browser:
This is line 1

This is line 2.
-- For some reason when wrapped with the span (or fluff) the output comes
out like the above
-- when not wrapped in the span it comes out the same as Xalan 1.2

It is reproducible.

On the sample XSL (the for-each), it was sent to me and I didn't really look
at the XSL other than to wrap the span around the para (it was just a basic
example that worked and it doesn't change anything...). WHen I submitted the
bug to the Xalan dev list I noticed the for-each and took it out.



----- Original Message -----
From: "Mike Brown" <mike@xxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, February 01, 2001 10:24 PM
Subject: Re:  matching <br/> v. <br></br>


> Robert-
>
> Your message was still not at all clear as to what the problem is.
> Are you talking about what the user sees in their web browser? If
> so, which browser? Or are you just looking at the HTML?
>
> Are you thinking that <br></br> is different than <br/> ?
>
> Or that &lt;br&gt;&lt;/br&gt; when copied through to the result tree
> should be serialized as <br></br> rather than &lt;br&gt;&lt;/br&gt; ?
>
> Or that <xsl:template match="para"> means "go process para elements"
> instead of "here's what to do if you happen to process a para element"?
>
> Or that <xsl:for-each select="."> has any utility whatsoever?
>
> I don't understand what difference the CSS fluff in your literal
> result elements would have on the actual output.
>
> What are you trying to achieve, and what exactly is the output you
> are seeing? Can you run the transformation standalone and see what
> the output from Xalan really is?
>
> And perhaps it would help if you sketched out the XPath/XSLT node tree
> for your XML...
>
> root node
> |
> element 'test'
>   |___text '\n  '
>   |___element 'para'
>   |     |___text 'kjd...sg '
>   |     |___element 'br'
>   |     |___text ' jdf...skl\n'
>   |___text '\n  '
>   |___element 'para'
>   |     |___text 'kjd...sg '
>   |     |___text 'kjd...sg '
>   |     |___element 'br'
>   |     |___text ' jdf...skl\n'
>   |___text '\n  '
>   |___element 'para'
>   |     |___text 'Holly and Jeff'
>   |     |___element 'br'
>   |     |___text ' received some'
>   |     |___element 'br'
>   |     |___text ' training manuals<br></br> they ordered.'
>   |___text '\n'
>
> The only thing I can say with certainty is that your stylesheet
> *is* managing to process all of these nodes.
>
>    - Mike
> ____________________________________________________________________
> Mike J. Brown, software engineer at            My XML/XSL resources:
> webb.net in Denver, Colorado, USA              http://skew.org/xml/
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list