I am working with ePub3 ebooks and have found the following problem.
I've added the template below to my customization layer for ePub3 publishing
It adds the items as requested but it inserts an empty xmlns="" declaration.
The resulting lines in the manifest file l
Actually, you do need a namespace in your output, just not the null namespace.
Epub3 output elements must be in the XHTML namespace. Any customization layer
must declare the default output namespace like this:
http://www.w3.org/1999/xhtml"; ...
Bob Stayton
Sagehill Enterprises
b...@sagehill.
On 17.4.2012 21:16, Bob Stayton wrote:
> Actually, you do need a namespace in your output, just not the null
> namespace. Epub3 output elements must be in the XHTML namespace. Any
> customization layer must declare the default output namespace like this:
>
> http://www.w3.org/1999/xhtml"; ...
I don't know if I'm missing something here but wouldn't the default namespace
on the root element of the package be enough to cover the namespace
requirements?
All other generated items in the package have the following syntax
and only the items added to the template have the namespace d
On 17.4.2012 23:11, Carlos Araya wrote:
> and now it validates. I think my question is whether we can skip the NS
> declaration and use the default from the package. Either way I'm good :-)
Please note that xsl:import/xsl:include doesn't affect in-scope
namespaces. So if you are emitting namesp
