Stylesheet Properties — HTML Chunk
The HTML Chunk tab of the Stylesheet Properties dialog box allows you to configure the way in which documents published to chunked HTML outputs are processed.
The HTML Chunk tab provides the following options:
• Create CSS rules for: Contains options by which you can specify the objects for which CSS information should be created. The options are:
◦ Contexts and conditions: Each context and condition generates its own CSS rule. This is the default for existing and new stylesheets.
With this option you will have more precise control over style. You can adjust formatting for an individual context or condition by making changes either to the .style file before publishing, or to the CSS file after publishing.
All property settings made in Arbortext Styler will be incorporated in the CSS rules, whether they were made in property sets referenced by the context or condition or set explicitly.
◦ Property sets: Each property set in the stylesheet generates a CSS rule. Elements in the HTML output will reference the CSS rules for the property sets that were referenced by the context and conditions that generated the element.
With this option you can generate a CSS file that will support HTML files of different document types, provided the stylesheets for those document types use the same property set names. You can maintain a consistent look for the HTML generated from different document types.
|
|
Properties specified explicitly for contexts and conditions will not be reflected in the HTML output or the CSS rules. A stylesheet validation invoked via the > menu option will warn you if any outputs are configured to use the Property Sets method to generate CSS and there are explicit properties that will not appear in the HTML/CSS as a result. Use the > menu option to locate the explicit property settings.
|
• Generate XHTML: Specifies whether the publishing processing creates HTML or XHTML files.
This checkbox does not apply for EPUB output, which always consists of XHTML data.
• Generate HTML5: Specifies whether the publishing processing creates HTML or HTML5 files.
Selecting both Generate XHTML and Generate HTML5 will output HTML in XHTML5 format.
HTML5 output may not display correctly in pre-HTML5 browsers, for example Internet Explorer 7 and 8.
The setting for this option has no effect in EPUB output. Arbortext Styler generates output that conforms to the EPUB 2.0 standard as a default.
• Shrink graphics to fit: Specifies whether graphics that are too large horizontally for the available space should be scaled down to fit that space. If the option is not selected, graphics will extend out of the available space if they are too large.
Shrink-to-fit scaling maintains the height-width ratio of the graphic.
This handling is independent of all other scaling and size related controls already in place for a graphic. The existing controls will continue to have the same effect The shrink-to-fit capability is applied after the existing graphics settings if the graphic is still too large for the available space.
|
|
For graphics inside table cells, it is recommended that you use a traditional scale-to-fit sizing mechanism for the individual graphic. With just Shrink graphics to fit set to manage these graphics, you may find that the table column grows to accommodate the graphic in HTML outputs.
|
The default setting is No.
This checkbox does not apply for EPUB output. Graphics are always scaled in this way.
• Generate semantic HTML/XHTML: configure HTML output for accessibility by providing context for paragraph and title elements.
An element styled as Title will be tagged as one of <h1> — <h6> (depending on its level in the hierarchy) instead of <div>. <p> tags will be generated for elements styled as Paragraph.
• Format list items as tables: specifies how list items are formatted in the HTML output, either as single row tables or as li elements.
This was previously controlled by the stylerhtmlcomposelistitemastable ACL set option, which applied to all outputs.
This option is checked as a default in existing and new stylesheets.
You should activate this setting if you wish to:
◦ Control the width of the list item marker field, the justification of the number or bullet, and any punctuation in the list item label. Such explicit control cannot be observed without presenting the list item in table format.
◦ Use specific number or bullet styles, labels and suffixes, or punctuation in the list item label. If list items are not formatted as tables, support for these settings varies widely.
With this option checked, the resulting HTML files will be larger and will be less clearly presented when the HTML is processed by a screen reader such as JAWS.
• Chunk boundaries: Contains options with which you can define the places at which a document should be broken when publishing output made up of chunked HTML data:
◦ Element HTML chunking properties - Obey the chunk boundary settings defined for each element in the document in the HTML Chunking dialog box that is accessed from the Breaks tab. This option is checked by default when you create a new stylesheet.
◦ DITA topic file boundaries - Use the boundaries of the input files of a DITA document as chunk boundaries, and derive the filename of those chunks from the filename of the input files. This option is only enabled in stylesheets for DITA documents.
Note that it is possible to select both options for a single document - in this case both boundary types will be used, with an element's HTML chunking properties taking precedence if a setting of both types exists for the same element.
• Limit table of contents levels (does not apply to EPUB): Sets the maximum level to which table of contents entries generated by a table of contents format object should be extracted and displayed in an online TOC in chunked HTML output (except EPUB). Select the option to activate the limit and add a level number to the field, by either typing manually or using the spinner control. When you check this option, the levels control defaults to a value of 3.
• Associated JavaScript Libraries: Lists the JavaScript libraries that are associated with the stylesheet
Use Add to open the Add JavaScript Library dialog box, and specify the path to the required library
You can add references either to common libraries, such as jQuery or AngularJS, or to custom libraries developed by your organization.
Use Edit to edit the path of an existing library reference
Use Delete to remove an association with a library
|
|
JavaScript libraries cannot be managed from stylesheet modules — they must be present in the root stylesheet.
|
A reference to each library listed here will be included in chunked HTML output generated from the stylesheet. Libraries are added to output in the order they are declared in this field.
