Build Table of Contents – Should the resultant web pages have an automatically
generated table of contents for navigation purposes?
Build Table of Contents in HTML frame – Builds the table of contents in a separate
HTML page and places this next to each web page in the document in an HTML
frame. This is very useful if you want the table of contents to be visible from
anywhere in the document.
Use page numbers – Should the table of contents consist of simple page number
links? E.g. page 1, page 2…
Use prefix characters – If specified, Purepage Server will scan the original document
for text that is prefixed with the specified prefix characters and turn this text into
heading links in the table of contents. For example, turn all text that is prefixed with
the characters ^& into heading links in the table of contents.
Use MS Office advanced mode – Uses advanced printing for all Microsoft Office
documents. Also specifies that any MS Word documents that are converted should be
scanned for additional information. This additional information includes links,
bookmarks and tables of contents. NOTE: This is a more reliable form of printing but
in conjunction with the next option it can slow down the rate of conversion of
Purepage Server.
Extract heading information from MS Word documents – Should the headings in
MS Word documents be used to create the table of contents links in the HTML
document? You can also specify a heading from MS Word documents to be
considered more important e.g. if you have used Heading 3 as the main heading in
your document, you can choose to display Heading 3’s as a category heading in the
 |
 |
 |
 |