db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (DERBY-5136) Simple accessibility fixes to frames HTML doc output
Date Tue, 05 Apr 2011 18:45:05 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase reopened DERBY-5136:

Part of the build.xml init task, the dita.regex target, makes a change to the DITA-OT1.1.2.1/xsl/xslhtml/dita2htmlImpl.xsl
file before the copy task copies the fixed version from lib. This means that by default, in
a freshly checked out workspace, the copy is not done because the version in DITA-OT1.1.2.1/xsl/xslhtml
is newer than the one in lib. 

To fix this, the copy task needs to have the overwrite parameter set:

<copy file="${dita.lib.dir}/dita2htmlImpl.xsl" todir="${dita.dir}/xsl/xslhtml" overwrite="true"/>

> Simple accessibility fixes to frames HTML doc output
> ----------------------------------------------------
>                 Key: DERBY-5136
>                 URL: https://issues.apache.org/jira/browse/DERBY-5136
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>             Fix For:
>         Attachments: DERBY-5135.diff, DERBY-5135.stat, index.html, rrefcopyright.html
> The frames versions of the HTML manuals have some accessibility errors that are quite
easy to fix, involving the index.html file and section heads.
> The index.html file for the frames version has several errors:
> 1) The <html> element lacks a lang attribute (lang="en" in this case).
> 2) The <frameset> element lacks a <noframes> element telling people with
browsers that don't support frames where to find an alternative version of the documentation.
We can point them to the single-file HTML manual.
> 3) The <frameset> and <frame> elements require title attributes.
> It is possible to fix these issues fairly easily by providing a modified version of the
DITA-OT1.1.2.1/resource/index.html file and then by making some additional edits to the init
and html.dita tasks in the build.xml file.
> The documentation also violates the rule that heads must appear in order. The topics
in the Derby documentation generate only two HTML head tags, <h1> for the topic title
and <h4> for sections. Sections cannot be nested in DITA. 
> It is possible to fix this problem by providing a modified version of the DITA-OT1.1.2.1/xsl/xslhtml/dita2htmlImpl.xsl
file that specifies the use of <h2> tags instead of <h4>. Section heads are always
generated with the "sectiontitle" class, which is specified in the .css files, so the output
seems to look the same with either head in a browser that supports stylesheets.
> I plan to file a patch for this task tomorrow.

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

View raw message