In the future, please post these sorts of message to the Mulberry XSL list.
This question is not appropriate for the general list, and isn't even
appropriate for the Xalan list, since it involves behavior that is
described in the XSLT 1.0 recommendation.
>From the paragraph _before_ the one you're quoting in the recommendation:
The html output method should not output an element differently from the
xml output method unless the expanded-name of the element has a null
namespace URI; an element whose expanded-name has a non-null namespace
URI should be output as XML. If the expanded-name of the element has a
null namespace URI, but the local part of the expanded-name is not
recognized as the name of an HTML element, the element should output in
the same way as a non-empty, inline element such as span.
Since your stylesheet declares a default namespace, all of the literal
result elements in your stylesheet are _not_ recognized as HTML elements,
but as XML elements. Remove the default namespace declaration from your
stylesheet to fix the problem.
Dave
Britta Schüle
<britta.schuel To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
[EMAIL PROTECTED]> cc: (bcc: David N Bertoni/CAM/Lotus)
Subject: RE: <br> and </br> tags
06/11/2001
10:46 AM
Please respond
to general
oops, forgot to include the files - sorry! and as was pointed out
repeatedly
- we do actually set output method to html ... weird.
-----Original Message-----
From: Britta Schüle [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 11, 2001 3:36 PM
To: '[EMAIL PROTECTED]'
Subject: RE: <br> and </br> tags
hiya,
thanks for the feedback so far, but i think i haven't quite said clearly
enough what's happening ; (
we're using the sax parser to parse documents. according to the w3c
recommendations,
"The html output method should not output an end-tag for empty elements.
For
HTML 4.0, the empty elements are area, base, basefont, br, col, frame, hr,
img, input, isindex, link, meta and param. For example, an element written
as <br/> or <br></br> in the stylesheet should be output as <br>."
BUT, no matter what we try, the parser always seems to insert a <br /> when
it finds a <br> in the xsl.
i enclosed the xml, xsl and the rendered html files as examples.
thanks, britta
-----Original Message-----
From: Britta Schüle [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 11, 2001 12:28 PM
To: [EMAIL PROTECTED]
Subject: <br> and </br> tags
hi folks,
we seem to have a problem with our xml's: no matter what we do, the parser
always inserts a </br> when encountering a <br>. the real problem is that
netscape doesn't understand the closing tag and then simply omits it, so
that the output looks, to put it that way, shite.
now my question: has anyone had that problem before and managed to solve
it?
or could it possibly be a known or unknown problem with the parser?
cheers, britta
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
