Merging Table of Contents

2-10 Oracle Fusion Middleware Developers Guide for Oracle Help Figure 2–10 Results of the Merging This example assumes that the view elements defining the Contents navigators for the helpsets do not have titles. If a view for a Contents navigator includes a title, then this title is used as a parent node to all tocitem items defined by the toc.xml file. For more information, see Chapter 6, Metadata Files .

2.4 Other OHJ Features

Oracle Help for Java OHJ features, not otherwise mentioned in this Oracle Help Guide, include the following features: ■ Accessibility Features ■ Internationalization Features ■ Java Foundation Class JFC Swing Components ■ Open, Pluggable Architecture

2.4.1 Accessibility Features

OHJ has the following accessibility features: ■ All user interface features are keyboard accessible, including the default HTML display component the ICEbrowser. Oracle has modified the ICEbrowser that ships with OHJ to provide this accessibility support. ■ The most recent versions of OHJ and of the ICEbrowser have been successfully tested with the JAWS for Windows Screen Reader from Freedom Scientific. For more information, see http:www.freedomscientific.com .

2.4.2 Internationalization Features

OHJ has the following internationalization features: ■ All text strings in the user interface are stored in resource files, for easy translation. ■ The locale and encoding can be set programmatically. ■ The default HTML display component the ICEbrowser supports wrapping for non-space separated languages. ■ Help authors can set the charset of the HTML file, using the IANA character set encoding names when using the default ICEbrowser HTML display component. ■ The OHJ user interface has been translated by Oracle into several languages. OHJ User Interface 2-11

2.4.3 Java Foundation Class JFC Swing Components

The OHJ Help system is implemented using Java Foundation Class JFC Swing components from Sun Microsystems.

2.4.4 Open, Pluggable Architecture

OHJ has an open, pluggable architecture. That means that you can substitute your own components for default components such as the search facility or the HTML display component. In addition, components such as the Navigator tabs and the HTML display can be embedded into an applications user interface, to provide completely integrated help. All OHJ application class files, control files, and content files can be encapsulated and compressed into JAR Java Archive files. It is not necessary to unJAR these files to run the help system.