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

Kim Haase commented on DERBY-4408:
----------------------------------

Thanks, Knut! That does work. Part of the patch was rejected when I applied it 
(the part with the xsl:output tag) so the omit-xml-declaration attribute stayed 
in. I fixed that.

I needed to put the xml declaration and license in the index.html file, too. 

I don't think we need to put the license into the -single html files, since the 
full license is near the top of the file anyway -- that's why it wasn't there 
before. With the frames version, the license was in only one topic rather than 
every file. However, it can do no harm. What do you think?

> missing DOCTYPE and META tags in toc.html and index.html pages
> --------------------------------------------------------------
>
>                 Key: DERBY-4408
>                 URL: https://issues.apache.org/jira/browse/DERBY-4408
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.3.3.0
>            Reporter: Myrna van Lunteren
>            Assignee: Kim Haase
>         Attachments: DERBY-4408-2.diff, DERBY-4408.diff, DERBY-4408.diff, 
> DERBY-4408.stat, DERBY-4408.zip, index.html, insert-header.diff, toc.html
>
>
> I found a tool that analyzes the documentation for possible accessibility 
> issues, and it found that the index.html and toc.html files from all 6 books 
> have issues:
>   INDEX.HTML
>      977   Missing DOCTYPE tag.  Required to define version of XHTML being 
> used.           
>      833   Missing META tag.  Required CHARSET value must be defined in this 
> file.         
>  TOC.HTML                                        
>      831   Missing DOCTYPE tag.  Required to define version of HTML being 
> used.  Line: 1    

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

        

Reply via email to