[ 
https://issues.apache.org/jira/browse/DERBY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094511#comment-13094511
 ] 

Knut Anders Hatlen commented on DERBY-5359:
-------------------------------------------

I found a good explanation here: http://www.xmlplease.com/xhtmlxhtml

Following those steps and adding both an xmlns and an xmlns:xhtml attribute to 
the xsl:stylesheet element made the xmlns attribute appear at the right place 
(and only there) in the generated documents. However, I had to do that both in 
the xsl files in the lib directory and in all the xsl files under 
DITA-OT1.1.2.1/xsl/xslhtml. So it looks like we'd either need to check in 
modified versions of more xsl files, or add a rewrite rule in the build script 
to modify the toolkit at build-time. Unless someone knows a better way to do 
the html generation, of course.

> Missing xmlns attribute for html element in docs
> ------------------------------------------------
>
>                 Key: DERBY-5359
>                 URL: https://issues.apache.org/jira/browse/DERBY-5359
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Jayaram Subramanian
>         Attachments: derby5359.diff, html.zip
>
>
> The html files in the documentation that are declared as XHTML don't pass as 
> valid XHTML because the html elements lack the xmlns attribute. Examples:
> http://db.apache.org/derby/docs/dev/ref/index.html
> --> 
> http://validator.w3.org/check?uri=http%3A%2F%2Fdb.apache.org%2Fderby%2Fdocs%2Fdev%2Fref%2Findex.html
> http://db.apache.org/derby/docs/dev/ref/toc.html
> --> 
> http://validator.w3.org/check?uri=http%3A%2F%2Fdb.apache.org%2Fderby%2Fdocs%2Fdev%2Fref%2Ftoc.html
> http://db.apache.org/derby/docs/dev/ref/rrefcallprocedure.html
> --> 
> http://validator.w3.org/check?uri=http%3A%2F%2Fdb.apache.org%2Fderby%2Fdocs%2Fdev%2Fref%2Frrefcallprocedure.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to