As to why the compiler doesn't complain on this construction:
<xsl:choose>
<xsl:if test="count(news_post) < 3">
which the compiler should have thrown out: the only things allowed
inside
xsl:choose are xsl:when and xsl:otherwise.
It's helpful in such cases to identify the processor in question. Ideally
you should report the bug to the vendor: any respectable vendor will be
grateful for the information (this kind of error can survive in a product
for years: for example at one time Saxon didn't require xsl:param to come
before other things in a template, and either no-one noticed, or they didn't
report it).
Failing that, don't hesitate to name the processor on this list. It's useful
for the community as a whole to know that a particular processor has a
particular bug, and it also helps people to help you with your problem.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--