Publishing a Document as an HTML File

This method creates a flat HTML file. It has a table of contents, but does not have an index. Use this publishing method if you want to send a document to someone as a single HTML file. You do not get all of the additional files that go along with publishing to the Web.

If your document includes graphics, you must specify graphic width and depth attributes in pixels if you want these attributes set in the HTML output. Web browsers can't interpret graphic width and depth attributes that are specified in measurements other than pixels.

1. Choose File > Publish > HTML File. The Publish to HTML File Dialog Box opens.

2. Specify an output directory and file name in the Save As box, or accept the default. Click Browse to locate an existing file.

3. Select the View HTML option if you want the document to display in a web browser after it is published.

If you select the View HTML option and your document file name includes an ampersand (& symbol), Arbortext Editor will respond that it cannot launch the web browser. Select Yes to publish with the browser disabled, or No to cancel the publishing process.

4. Choose the stylesheet you wish to use when publishing your document from the Stylesheet list. Click Browse to locate an existing stylesheet that does not appear in the list.

If you are using Arbortext Publishing Engine, the list displays the stylesheets available from the Arbortext Publishing Engine server. The notation (pe) appears in the stylesheet name. Local stylesheets are ignored.

5. Choose the character encoding in which you want to publish your document from the Encoding list.

6. If you are publishing a DITA document that has an associated DITAVAL file, choose that file in the DITAVAL File list. Click Browse to locate an existing DITAVAL file that does not appear in the list.

7. If your document has change tracking, you can publish the document in any of the change tracking states. By default, the change tracking view from the Edit window is selected, except when publishing from a DITA map.

If you are publishing a DITA map, Changes Applied is selected by default. When publishing from a DITA Map, the Change Tracking view that's selected applies only to the topics referenced from the DITA maps. The DITA map itself, as well as other referenced maps, will always be published with Changes Applied, regardless of the Change Tracking view selected (even if a map has change tracking markup).

◦ Changes with Highlighting — Shows all proposed changes, highlighted with revision marks.

◦ Changes Applied — Shows all proposed changes incorporated into the document, without revision marks.

◦ Original — Shows the original document without proposed changes incorporated into the document.

8. If you choose to Queue Transaction, you will be prompted for the Save As file name and whether to View HTML when you retrieve the result from your list of Queued Transactions, available from the Tools menu. Choosing to Queue Transaction clears Save As and View HTML values from the dialog box. If you entered values in these fields, they will be displayed again if you clear the Queue Transaction check box.

9. Choose whether to enter a Transaction Name. The transaction name will be displayed when you retrieve the result from your list of Queued Transactions, available from the Tools menu.

You can enter transaction names to use by default or for specific output types by entering values in the Queued Transaction Names Dialog Box.

10. If you want to apply profiling to your document, click Set Profiles to access the Set Profiles dialog box. Click OK or Cancel to exit the Set Profiles dialog box. The Set Profiles button is only available if profiles have been configured for the selected document type.

11. If you want to create a publishing rule, click Create Rule to open Create New Publishing Rule, where you can create a new publishing rule or rule set to publish to HTML.

Arbortext Styler supports three different methods of including CSS information in HTML output. Refer to CSS files in HTML output for more information.

Arbortext Editor replaces some character entities during the publishing process because they do not display properly. The replacement character entities are defined in the Arbortext-path\composer\htmlEntSub.xml.