DotNet Help is a Help output format developed by MadCap Software for Windows desktop applications. It was designed to include the best attributes of Microsoft HTML Help and WebHelp, while filling the holes left behind by those formats. DotNet Help is designed specifically to support Visual Studio developers. It includes a freely redistributable viewer (MadCap Help Viewer), as well as components for the Visual Studio developer. These components can be dropped into your Flare project to facilitate context-sensitive Help, embedded Help, and features such as automated search string communication between the application and the DotNet Help documentation.
The output consists of a collection of files that you will distribute to users with the freely downloadable MadCap Help Viewer. The main entry file has an .mchelp extension.
key features
Following are some of the key features of the DotNet Help format:
- .NET Application Support
- Accessible This is a good choice if you do not want users to be burdened by the security warnings and limitations that are often encountered with Microsoft HTML Help and WebHelp.
- Customizable/Modern Interface You can produce a customizable interface that is much more modern looking than the aging Microsoft HTML Help. It will blend easily into a modern environment.
- Embedded Context-sensitive Help (CSH) You can create embedded CSH in a .NET application. This includes the ability to produce Dynamic Help.
- Multiple Languages Users can select between multiple languages for the interface when viewing your output. This is possible because the freely distributable MadCap Help Viewer lets users select English, French, German, or Japanese for the interface.
- Boolean Operator and Asterisk (*) Wildcard Character Searches These are supported on Microsoft Windows XP (and newer operating systems) when SQL Compact is installed on the local computer building the Help.
output type comparison tables
Following are tables that show the various output types available, with the distinguishing features of each.
Note
Note: If an item does not have a check mark, that does not necessarily mean the feature is unavailable in the output. Rather, it means that the feature cannot be added in Flare. For example, search cannot be added in Flare for EPUB output, but some ebook readers may have search built in.
general
Following are general features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
.NET Integration |
|
|
|
|
|
|
|
|
|
|
Single Output File |
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
.NET Integration |
|
|
|
|
|
Single Output File |
|
|
|
|
accessibility
Following are accessibility features (e.g., Section 508, WCAG) supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
context-sensitive help
Following are context-sensitive Help (CSH) features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generated content
Following are generated content features supported in each output type:
|
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1It is possible to use autonumbering in online outputs, but only in a limited way. For example, if you have notes throughout your project, you can create an autonumber format on a paragraph style class that simply has the text "Note:" followed by a space. Then whenever you want to apply that style class to note content, it will automatically start with "Note:" so that you don't have to type it each time. However, in the traditional sense where autonumbering is used to increment numbers for elements such as chapters, figures, and tables, it is really only intended for print-based outputs. 2For Clean XHTML output, MadCap-injected JavaScript is removed. In other words, features such as drop-downs, Help controls, text popups, and footnotes rely on JavaScript to work. Therefore, with Clean XHTML output, these elements are converted to text. However, custom scripts that you might have added to topics 3In HTML5, the proxies and related skin components for search bars and search results are supported only in Top Navigation output, as well as in targets not using a skin. They are not supported in Tripane output. |
|||||||||
|
|
|
PRINT (LEGACY) |
||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
glossaries
Following are glossary features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1For most online outputs, creating a glossary via a skin is the preferred method. However, it is possible to use a proxy to include glossaries in these outputs as well. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
images
Following are image features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1For Clean XHTML and WebHelp Mobile outputs, thumbnail images that are set as popups are converted to linked thumbnail images (i.e., the enlarged image opens in a new window instead of in a popup). |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
indexes
Following are index features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1For online outputs, creating an index is typically done via a skin. By default, the MadCap style that controls index proxies is set to support only print-based outputs. However, you can change this. To do so, open your stylesheet, select the MadCap|indexProxy style, and set the mc-output-support property to all (all-print is the default setting). By doing this, you can use the index proxy method to generate an index in some online outputs as well. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
language support
Following are language support features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Author and Generate Output in Left-to-Right (LTR) and Right-to-Left (RTL) Languages |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Output Interface (Display English, French, Japanese, or German) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1This is controlled on the UI Text tab in a regular HTML5 skin. 2This is controlled in a language skin. 3This is possible with the MadCap Help Viewer, where the end user selects the language. 4As an alternative to using language skins, you can use the UI Text tab in the Skin Editor to perform all of the localization tasks for HTML5 targets. Be aware that translations in the Skin Editor are prioritized over translations in a language skin, so you should try to perform your localization tasks in one place to avoid conflicts. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
Author and Generate Output in Left-to-Right (LTR) and Right-to-Left (RTL) Languages |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Output Interface—Display English, French, Japanese, or German |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
master pages and page layouts
Following are master page and page layout features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
merging output
Following are merging output features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 Flare's HTML5 Top Navigation skin does not support project merging. 2 HTML5 outputs do not support pre-merging. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
miscellaneous features
Following are miscellaneous features supported in each output type:
|
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1For online outputs, footnotes are converted to popups. |
|||||||||
|
|
|
PRINT (LEGACY) |
||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
multimedia
Following are multimedia features supported in each output type:
|
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ASF |
|
|
|
|
|
|
|
|
|
|
ASX |
|
|
|
|
|
|
|
|
|
|
AU |
|
|
|
|
|
|
|
|
|
|
AVI4 |
|
|
|
|
|
|
|
|
|
|
M4V4 |
|
|
|
|
|
|
|
|
|
|
MID |
|
|
|
|
|
|
|
|
|
|
MIDI |
|
|
|
|
|
|
|
|
|
|
MP3 |
|
|
|
|
|
|
|
|
|
|
MP44 |
|
|
|
|
|
|
|
|
|
|
MPA |
|
|
|
|
|
|
|
|
|
|
MPE |
|
|
|
|
|
|
|
|
|
|
MPEG |
|
|
|
|
|
|
|
|
|
|
MPG |
|
|
|
|
|
|
|
|
|
|
OGG4 |
|
|
|
|
|
|
|
|
|
|
OGV4 |
|
|
|
|
|
|
|
|
|
|
OPUS |
|
|
|
|
|
|
|
|
|
|
SWF |
|
|
|
|
|
|
|
|
|
|
WAV |
|
|
|
|
|
|
|
|
|
|
WEBM4 |
|
|
|
|
|
|
|
|
|
|
WMA |
|
|
|
|
|
|
|
|
|
|
WMV |
|
|
|
|
|
|
|
|
|
|
Flash (SWF) Format |
|
|
|
|
|
|
|
|
|
|
HTML5 Format (Depending on Browser)4 |
|
|
|
|
|
|
|
|
|
|
Mimic Movie Format |
|
|
|
|
|
|
|
|
|
|
Silverlight Format |
|
|
|
|
|
|
|
|
|
|
Vimeo Embedded Videos |
|
|
|
|
|
|
|
|
|
|
YouTube Embedded Videos |
|
|
|
|
|
|
|
|
|
|
1EPUB support for each element or file type depends on if a particular reader supports it. 2Support for each element or file type depends on if a particular browser supports it. This is especially true with WebHelp mobile output and mobile browsers. 3For this output, the 3D Model opens in a separate window. 4To view HTML5 movie output, end users must have a newer browser that supports these types of videos. 5If you generate DotNet Help, embedded HTML5 movies are not supported out of the box. That's because DotNet Help uses Internet Explorer 7, which does not support HTML5 movies. However, you can make it work by adding the default meta tag to your target: <meta http-equiv="X-UA-Compatible" content="IE=Edge" />. 6This file format does not work in Internet Explorer. 7If you generate DotNet Help or Microsoft HTML Help, YouTube videos are rendered smaller than in other outputs and Vimeo Advanced settings are not supported. However, you can make it work by adding the default meta tag to your target: <meta http-equiv="X-UA-Compatible" content="IE=Edge" />. |
|||||||||
|
|
|
PRINT (LEGACY) |
||||
|---|---|---|---|---|---|---|
|
|
|
|
|
|
||
|
|
|
|
|
|||
|
ASF |
|
|
|
|
||
|
ASX |
|
|
|
|
||
|
AU |
|
|
|
|
||
|
AVI |
|
|
|
|
||
|
M4V |
|
|
|
|
||
|
MID |
|
|
|
|
||
|
MIDI |
|
|
|
|
||
|
MP3 |
|
|
|
|
||
|
MP4 |
|
|
|
|
||
|
MPA |
|
|
|
|
||
|
MPE |
|
|
|
|
||
|
MPEG |
|
|
|
|
||
|
MPG |
|
|
|
|
||
|
OGG |
|
|
|
|
||
|
OGV |
|
|
|
|
||
|
OPUS |
|
|
|
|
||
|
SWF |
|
|
|
|
||
|
WAV |
|
|
|
|
||
|
WEBM |
|
|
|
|
||
|
WMA |
|
|
|
|
||
|
WMV |
|
|
|
|
||
|
Flash (SWF) Format |
|
|
|
|
||
|
HTML5 Format (Depending on Browser) |
|
|
|
|
||
|
Mimic Movie Format |
|
|
|
|
||
|
Silverlight Format |
|
|
|
|
||
|
Vimeo Embedded Videos |
|
|
|
|
||
|
YouTube Embedded Videos |
|
|
|
|
||
|
1PDF support for 3D Models requires Adobe Reader 7.0+. |
|
|
||||
navigation links
Following are navigation link features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Responsive Output
Following are responsive output features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1This refers to the use of the Responsive Layout window pane (Home>Responsive Layout) to create content that adjusts automatically, depending on the screen size. 2Responsive content is supported in Clean XHTML output only if you do not select the target option to convert styles to inline. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
search
Following are search features supported in each online output type.
general support
The table below summarizes search support in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
end user search features
The table below summarizes the key search features and capabilities for each output type. With HTML5 and WebHelp outputs, you can distribute either client- or server-based outputs. This is why the table below lists them twice—under client- and server-based output.
End user search features are supported by the Eclipse Help Viewer and search operations are provided by a plug-in that you develop using the Eclipse platform (for more information, see org.eclipse.help.ui.searchEngine). The Flare search engine does not handle Eclipse Help search operations.
|
CLIENT-BASED OUTPUT |
SERVER-BASED OUTPUT |
||||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|||
|
Glossary Search (Find Matching Terms) |
|
|
|
|
|
|
|
||
|
Index Search (Find Matching Terms) |
|
|
|
|
|
|
|
||
|
Search Favorites (Save Queries to Favorites List) |
|
|
|
|
|
|
|
||
|
Search Query (Asterisk (*) Wildcard Character) |
|
|
|
|
|
|
|
||
|
Search Query (Boolean Operators) |
|
|
|
|
|
|
|
||
|
Search Query (Full-text Search—not case sensitive) |
|
|
|
|
|
|
|
||
|
Search Query (Enclose Terms in Quotes) |
|
|
|
|
|
|
|
||
|
Search Results (Narrow Search Scope Using Search Filter Sets) |
|
|
|
|
|
|
|
||
|
Search Results (Results Listed in Ranked Order and Show Rank Number) See Optimizing Search. |
|
|
|
|
|
|
|
||
|
Search Results (Search Hits Highlighted in Topics) See Search Highlighting. |
|
|
|
|
|
|
|
||
|
Search Results (Search Hits Bolded) |
|
|
|
|
|
|
|
||
|
1Use CTRL+F in the Glossary pane. 2SQL Server Compact is required. 3Select the operator from the built-in list. 4Results are listed in order. Rank number is not visible. |
|
|
|||||||
content developer search features
This table summarizes the key search features and capabilities that are available to you, the content developer, for each output type. With HTML5 and WebHelp outputs, you can distribute either client- or server-based outputs. This is why the table below lists them twice—under client- and server-based output.
|
CLIENT-BASED OUTPUT |
SERVER-BASED OUTPUT |
||||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|||
|
Enable Search Feature |
|
|
|
|
|
|
|
||
|
Content Optimization (Adjust Abstract Character Limit) |
|
|
|
|
|
|
|
||
|
Content Optimization (Enable or Disable Importance in Search Results) |
|
|
|
|
|
|
|
||
|
Content Optimization (Include or Exclude Glossary Terms in Search Results) |
|
|
|
|
|
|
|
||
|
Content Optimization (Set Number of Results Displayed Per Page) |
|
|
|
|
|
|
|
||
|
Search Highlighting (Set Highlight Color) |
|
|
|
|
|
|
|
||
|
Search Performance (Chunk Large Search Database Files) |
|
|
|
|
|
|
|
||
|
Search Performance (Enable Partial-word Searching and Set Minimum Word Size) |
|
|
|
|
|
|
|
||
|
Search Performance (Enable Stop Words in Search) |
|
|
|
|
|
|
|
||
|
Search Performance (Exclude Index Entries from Search) |
|
|
|
|
|
|
|
||
|
Search Performance (Exclude Non-words from Search) |
|
|
|
|
|
|
|
||
|
Search Performance (Include SQL Search Database) |
|
|
|
|
|
|
|
||
|
Search Performance (Pre-merge Search Database) |
|
|
|
|
|
|
|
||
|
Search Performance (Set N-Gram Size for Chinese, Japanese, and Korean Projects) |
|
|
|
|
|
|
|
||
|
Search Toolbar (Include and Customize a Quick Search Field and/or Select Search Button) |
|
|
|
|
|
|
|
||
|
Search Results (Customize Order of Search Filter Sets) |
|
|
|
|
|
|
|
||
|
Styles (Generated Search Results Pages) |
|
|
|
|
|
|
|
||
|
1HTML5 skin. 2Search cannot be disabled. 3Standard skin. 4Mobile skin. 5Stop words are always enabled. 6Index entries are always excluded. 7Non-words are always excluded. 8SQL Server Compact is required. 9These styles are supported only in HTML5 Top Navigation and skinless outputs. They are not supported in HTML5 Tripane output. |
|
|
|||||||
skins
Following are skin features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
HTML5 |
|
|
|
Std |
Std |
Std |
Mobile |
Std |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Elements Such as Tabs, Accordions (Specify Which to Include) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1This is available in the Tripane skin only. It is not available in the Top Navigation skin. 2This is handled through the org.eclipse.help.base plug-in. 3As an alternative to using language skins, you can use the UI Text tab in the Skin Editor to perform all of the localization tasks for HTML5 targets. Be aware that translations in the Skin Editor are prioritized over translations in a language skin, so you should try to perform your localization tasks in one place to avoid conflicts. 4This is available in the Top Navigation skin only. It is not available in the Tripane skin. 5Only some styles (e.g., Feedback, toolbar) are supported. 6Topic toolbar settings can be controlled in a Topic Toolbar skin component, as well as in a Topic Toolbar proxy. 7Limited settings are available. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Elements Such as Tabs, Accordions (Specify Which to Include) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Social Media (pulse and Feedback)
Following are the social media features supported in each output type (Pulse is the newer, and recommended solution; Feedback is a legacy method):
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1For HTML5, Feedback is supported only in Tripane output. It is not supported in Top Navigation or skinless outputs. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tables of contents and mini-tocs
Following are table of contents (TOC) and mini-TOC features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1Some ebook readers have a built-in TOC. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
target settings
Following are target features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Languages (Link to External Projects—Create Multilingual Output) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1We recommend disabling this option for non-English content. 2The standard mobile DOCTYPE is always used. |
|||||||||
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Languages (Link to External Projects—Create Multilingual Output) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
variables
Following are variable features supported in each output type:
|
ONLINE |
OTHER |
ONLINE (LEGACY) |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRINT (LEGACY) |
|||
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|