Empty element match

[Tjerk Wolterink]

i have the following rule,
<xsl:template match="br">
<br/>
</xsl:template>
This should convert all <br/> to <br/>
but, my transformer transforms it all to
<br></br>
Ok this does not look like a problem but i use it in a
web application and microsoft interpretes this
as 2 <br/><br/>

How can i force the transformer to not use the
implicit end tag like this <br/> ?

[David Carlisle]

Ok i will try to set the response mime type to text/xml, ok (or application/xml is probably better) is text/xhtml also possible?

no, the declared type for xhtml is text/xhtml+xml but IE doesn't know
about that.

You will need to use <?xml-stylesheet to specify a stylesheet (which can
simply be <xsl:copy-of select="."/>

But if you need to send to IE, why not send HTML, which it understands,
rather than XHTML, which it doesn't?

David

[David Håsäther]

David Carlisle <da****@nag.co. uk> wrote:

no, the declared type for xhtml is text/xhtml+xml

ITYM application/xhtml+xml :-)

--
David Håsäther

[David Carlisle]

ITYM application/xhtml+xml :-)

er yes, thanks.

[David Carlisle]

but why how do i overcome the problem that the parser/transformer
on the hostingprovider does not listen to the xsl:output method attribute?
You need to tell your serialser to output using html.
You haven't said which system you are using. The onlt one I use that
doesn't use xsl:output is cocoon where the serialisers (be it html,
xhtml, text, pdf, ...) are set up in sitemap.xmap with lines looking
something like

<map:serializer s default="html">
<map:serializ er logger="sitemap .serializer.lin ks" name="links" src="org.apache .cocoon.seriali zation.LinkSeri alizer"/>

<map:serializ er logger="sitemap .serializer.xml " mime-type="applicati on/xml" name="xml" src="org.apache .cocoon.seriali zation.XMLSeria lizer"/>

<map:serializ er logger="sitemap .serializer.htm l" mime-type="text/html" name="html" pool-grow="4" pool-max="32" pool-min="4" src="org.apache .cocoon.seriali zation.HTMLSeri alizer">
<buffer-size>1024</buffer-size>
</map:serializer>

the above is just boiler plate declarations part of the default
site map

then for a particular file that is to be serialised as html:

<map:pipeline >
<map:match pattern="index. html">
<map:generate src="xml/frontpage.xml" type="file"/>
<map:transfor m src="stylesheet s/html/om-page.xsl"/>
<map:serializ e type="html"/>
^^^^^^^^^^^^^^^ ^
</map:match>
</map:pipeline>
If you are not using cocoon then the above syntax will be wrong, but
probably something similar is available...
David

[Tjerk Wolterink]

David Carlisle wrote:

but why how do i overcome the problem that the parser/transformer

The hosting provider is running:

xsl
XSL enabled
libxslt Version 1.1.12
libxslt compiled against libxml Version 2.6.16
EXSLT enabled
libexslt Version 1.1.12

so libxslt 1.1.12.

With sablotron (i'm using that) there is no problem.
But what im doing is:

data.xml + form.xsl(output =xml) -> temp.xml (contains html tags but in
xml format)
temp.xml + page.xsl(output =html) -> page.html

In page.xsl there is a rule like this:

<!--
! All html should remain html
!-->
<xsl:template match="*[namespace-uri(.)='' or
namespace-uri(.)='http://www.w3.org/1999/xhtml']">
<xsl:copy>
<xsl:for-each select="@*">
<xsl:copy/>
</xsl:for-each>
<xsl:apply-templates select="./node()"/>
</xsl:copy>
</xsl:template>
Maybe this rule forces <br/> to convert to <br></br>
????

[Martin Honnen]

Tjerk Wolterink wrote:

In page.xsl there is a rule like this:

<!--
! All html should remain html
!-->
<xsl:template match="*[namespace-uri(.)='' or
namespace-uri(.)='http://www.w3.org/1999/xhtml']">
<xsl:copy>
<xsl:for-each select="@*">
<xsl:copy/>
</xsl:for-each>
<xsl:apply-templates select="./node()"/>
</xsl:copy>
</xsl:template>
Maybe this rule forces <br/> to convert to <br></br>

If you really want HTML output then you should strip the namespace from
XHTML elements e.g.
<xsl:template match="xhtml:*" >
xmlns:xhtml="ht tp://www.w3.org/1999/xhtml">
<xsl:element name="{local-name()}">
<xsl:copy-of select="@*" />
<xsl:apply-templates />
</xsl:element>
</xsl:template>

--

Martin Honnen
http://JavaScript.FAQTs.com/

[Tjerk Wolterink]

Martin Honnen wrote:

Tjerk Wolterink wrote:

In page.xsl there is a rule like this:

<!--
! All html should remain html
!-->
<xsl:template match="*[namespace-uri(.)='' or
namespace-uri(.)='http://www.w3.org/1999/xhtml']">
<xsl:copy>
<xsl:for-each select="@*">
<xsl:copy/>
</xsl:for-each>
<xsl:apply-templates select="./node()"/>
</xsl:copy>
</xsl:template>
Maybe this rule forces <br/> to convert to <br></br>

If you really want HTML output then you should strip the namespace from
XHTML elements e.g.
<xsl:template match="xhtml:*" >
xmlns:xhtml="ht tp://www.w3.org/1999/xhtml">
<xsl:element name="{local-name()}">
<xsl:copy-of select="@*" />
<xsl:apply-templates />
</xsl:element>
</xsl:template>

Ok thus namespaces are not allowed in html?

I cannot wait until browser truely support xml syntax.

Another question,

How does xsl handle empty elements,
does it convert them to
<element/>
or to
<element></element>

And are there any settings in the parser to control that?

[Richard Tobin]

In article <da**********@n etlx020.civ.utw ente.nl>,
Tjerk Wolterink <tj***@wolterin kwebdesign.com> wrote:

Ok thus namespaces are not allowed in html?
HTML, being SGML rather than XML, knows nothing about namespaces.
As far as HTML is concerned, xhtml:html is an element it's never
heard of, and <html xmlns="whatever-the-xhtml-namespace-is"> has
an invalid attribute (though it probably wouldn't mind that).

But as far as outputting HTML from XSLT goes, only elements in no
namespace are output according to the HTML rules. So you have to
choose between outputting XHTML using the appropriate namespace, or
outputtting HTML with no namespace.
How does xsl handle empty elements,
does it convert them to
<element/>
or to
<element></element>

When outputting XML, it's up to the implementation, because they are
equivalent as XML. When outputting HTML, it will do the Right Thing,
according to what kind of HTML element it is (so it will output
always-empty elements as, for example, <br>).

-- Richard

[Tjerk Wolterink]

Richard Tobin wrote:

In article <da**********@n etlx020.civ.utw ente.nl>,
Tjerk Wolterink <tj***@wolterin kwebdesign.com> wrote:

Ok thus namespaces are not allowed in html?

HTML, being SGML rather than XML, knows nothing about namespaces.
As far as HTML is concerned, xhtml:html is an element it's never
heard of, and <html xmlns="whatever-the-xhtml-namespace-is"> has
an invalid attribute (though it probably wouldn't mind that).

But as far as outputting HTML from XSLT goes, only elements in no
namespace are output according to the HTML rules. So you have to
choose between outputting XHTML using the appropriate namespace, or
outputtting HTML with no namespace.

ok but my output method is set to html, why are the namespaces still
there?

How does xsl handle empty elements,
does it convert them to
<element/>
or to
<element></element>

When outputting XML, it's up to the implementation, because they are
equivalent as XML. When outputting HTML, it will do the Right Thing,
according to what kind of HTML element it is (so it will output
always-empty elements as, for example, <br>).

-- Richard

ok thanks