Elizabeth Sadler wrote:
I apologize if I'm misunderstanding the problem, but have you tried
using the exclude-result-prefixes flag in your XSL declaration? Like this:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/
Transform" xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
xmlns:dir="http://apache.org/cocoon/directory/2.0" exclude-result-
prefixes="dir">
AFAIK this will solve Geert's problem, but not mine, because
there is no XSL in my case.
My pipeline looks the following:
<map:match pattern="...">
...
<map:transform type="cinclude"/>
<map:serialize type="xhtml"/>
</map:pattern>
Unfortunately cinclude leaves its namespace in the resulting
XML - this causes the W3C validator to consider my XHTML as
not valid:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:cinclude="http://apache.org/cocoon/include/1.0">
<head>
The same is true for the i18n-transformer. Similar pipline
as above:
<map:match pattern="...">
...
<map:transform type="i18n"/>
<map:serialize type="xhtml"/>
</map:pattern>
which results in:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
<head>
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]