Script Templates 7-43
■
Generating Bullets and Numbers for Lists on page 7-43
7.7.1 Changing the Format Used for Converted Graphics
If you want to change the format to be used for converted graphics, edit the following option:
SCCOPT_GRAPHIC_TYPE Determines what graphic format will be used for exported graphics.
Setting this to none disables graphic output. graphictype gif
graphictype jpeg graphictype png
graphictype none
Lines that begin with have been commented out. So the above example shows the default setting, with the gif format selected. To use the jpeg format, instead, you
would simply comment the first line and uncomment the second line, thus:
graphictype gif graphictype jpeg
graphictype png graphictype none
7.7.2 Generating Bullets and Numbers for Lists
If you want to generate bullets and numbers for lists instead of HTML list tags, you would edit the following option:
SCCOPT_GENBULLETSANDNUMS Generate Bullets and Numbers. Bullets and numbers will be generated for
lists instead of using HTML list tags ol, ul, li, etc. when rendering lists in a document.
genbulletsandnums no genbulletsandnums yes
Again, comment one line and uncomment another, thus: genbulletsandnums no
genbulletsandnums yes
7.8 Breaking Documents by Structure
One of the most powerful features of the template architecture is the ability to break long word processor documents up into logical pieces and create powerful navigation
aids to access them.
To understand how this is done, you must first understand the document tree as it relates to word processing documents. The somewhat complex graphic below
attempts to show how the elements in the tree relate to a real-world document see figure below.
The following are some examples of elements and the data they would produce if run against the document shown in the preceding image. Note the omission of the default
nodes body and contents in the second two examples:
7-44 Administrators Guide for Dynamic Converter
body.contents.headings.2.body.title would produce Present Day.
body.contents.headings.2.body.contents.headings.1.body.title would produce Commercial.
body.contents.preface would produce The History of Flight and the text below it, up to but not including
Introduction. headings.2.headings.1.headings.3.title
would produce McDonnell-Douglas. headings.2.headings.1.headings.3.contents
would produce the text below McDonnell-Douglas but above Military.
Script Templates 7-45
Figure 7–5 Breaking up documents by structure
Breaking documents requires that Dynamic Converter understands the logical divisions in the structure of a document. Currently the only formats that can give
Dynamic Converter this information in an unambiguous manner are Microsoft Word 95 and higher and WordPerfect 6.0 and higher. In these formats, the breaking
information is available if the author placed table-of-contents information in the document. Refer to the appropriate software manual for information on the necessary
procedure for including this information. That is not to say that the document must have a table of contents, only that the information to build one must be present.
It should be noted that some word processing formats, including Microsoft Word 2002 XP, allow users to specify TOC entries in multiple ways. Dynamic Converter only
supports two of these methods:
7-46 Administrators Guide for Dynamic Converter
Additionally, if a heading style is applied to text inside a table in the original document, Dynamic Converter will not break on that heading. This is because
Dynamic Converter will not break within tables.
Indexes and Structure-Based Breaking All repeatable nodes have an associated index variable that has a current value at any
given time in the conversion process. For elements that contain repeatable nodes as part of their path, the instance of the repeatable element must be specified by using a
number or one of several index variable keywords. See
Index Variable Keywords on
page 7-9 for more information on the possible values for the index variables.
7.9 Breaking Documents by Content Size