summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRalph Amissah <ralph@amissah.com>2011-07-27 00:37:49 +0000
committerRalph Amissah <ralph@amissah.com>2011-07-27 00:37:49 +0000
commit3c0b56d9b72b3fbc1a482b1da1dcca23b5676a24 (patch)
tree2dbd5540adba17b6d1b0da274b0b1d1eaddd76df
parentv2 v3: manpage (diff)
downloadsisu-sisu_3.0.14.zip
sisu-sisu_3.0.14.tar.xz
v2 v3: manpage html (man2html)sisu_3.0.14
* commands: --qrcode -Q; update shortcut options * markup.sst: indent update; publisher
-rw-r--r--data/doc/sisu/CHANGELOG_v32
-rw-r--r--data/doc/sisu/html/sisu.1.html515
2 files changed, 290 insertions, 227 deletions
diff --git a/data/doc/sisu/CHANGELOG_v3 b/data/doc/sisu/CHANGELOG_v3
index a27a707..7978dc0 100644
--- a/data/doc/sisu/CHANGELOG_v3
+++ b/data/doc/sisu/CHANGELOG_v3
@@ -43,7 +43,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_3.0.14.orig.tar.gz
* sql db, constants, cgi-sql, structure changed, creator editor field added
- * sisu_manual, manpage
+ * sisu_manual, manpage, manpage html (man2html)
* sisu_commands: --qrcode -Q; update shortcut options; line-breaks use \\
* sisu_markup.sst: indent update; publisher
diff --git a/data/doc/sisu/html/sisu.1.html b/data/doc/sisu/html/sisu.1.html
index fb74b10..33529bf 100644
--- a/data/doc/sisu/html/sisu.1.html
+++ b/data/doc/sisu/html/sisu.1.html
@@ -179,39 +179,39 @@ and the same document structure information. For more see: &lt;<a href='http://w
<dt><b>-a [filename/wildcard]</b> </dt>
<dd>produces plaintext
with Unix linefeeds and without markup, (object numbers are omitted), has
-footnotes at end of each paragraph that contains them [ &nbsp;-A &nbsp;for &nbsp;equivalent
-&nbsp;dos &nbsp;(linefeed) &nbsp;output &nbsp;file] [see &nbsp;-e &nbsp;for (Options include: --endnotes for endnotes
---footnotes for footnotes at the end of each paragraph --unix for unix linefeed
-(default) --msdos for msdos linefeed)
+footnotes at end of each paragraph that contains them [ &nbsp;-A for &nbsp;equivalent
+&nbsp;dos &nbsp;(linefeed) &nbsp;output &nbsp;file] [see &nbsp;-e &nbsp;for endnotes]. (Options include: --endnotes
+for endnotes --footnotes for footnotes at the end of each paragraph --unix
+for unix linefeed (default) --msdos for msdos linefeed)
<p> </dd>
<dt><b>-b [filename/wildcard]</b> </dt>
<dd>see --xhtml
<p> </dd>
-<dt><b>--color-toggle
-[filename/wildcard]</b> </dt>
-<dd>screen toggle ansi screen colour on or off depending
-on default set (unless -c flag is used: if sisurc colour default is set
-to &rsquo;true&rsquo;, output to screen will be with colour, if sisurc colour default
-is set to &rsquo;false&rsquo; or is undefined screen output will be without colour). Alias -c
+<dt><b>--color-toggle [filename/wildcard]</b> </dt>
+<dd>screen toggle ansi screen colour
+on or off depending on default set (unless -c flag is used: if sisurc colour
+default is set to &rsquo;true&rsquo;, output to screen will be with colour, if sisurc
+colour default is set to &rsquo;false&rsquo; or is undefined screen output will be without
+colour). Alias -c
<p> </dd>
<dt><b>--concordance [filename/wildcard]</b> </dt>
-<dd>produces concordance (wordmap) a rudimentary
-index of all the words in a document. (Concordance files are not generated
-for documents of over 260,000 words unless this limit is increased in the
-file sisurc.yml). Alias -w
+<dd>produces concordance (wordmap)
+a rudimentary index of all the words in a document. (Concordance files are
+not generated for documents of over 260,000 words unless this limit is
+increased in the file sisurc.yml). Alias -w
<p> </dd>
<dt><b>-C [--init-site]</b> </dt>
-<dd>configure/initialise shared output
-directory files initialize shared output directory (config files such as
-css and dtd files are not updated if they already exist unless modifier
-is used). -C --init-site configure/initialise site more extensive than -C on
-its own, shared output directory files/force update, existing shared output
-config files such as css and dtd files are updated if this modifier is
-used.
+<dd>configure/initialise
+shared output directory files initialize shared output directory (config
+files such as css and dtd files are not updated if they already exist unless
+modifier is used). -C --init-site configure/initialise site more extensive than
+-C on its own, shared output directory files/force update, existing shared
+output config files such as css and dtd files are updated if this modifier
+is used.
<p> </dd>
<dt><b>-CC</b> </dt>
@@ -271,6 +271,7 @@ language subdirectories). Alias -f, --glob, -G
<dt><b>-F [--webserv=webrick]</b> </dt>
<dd>see --sample-search-form
+
<p> </dd>
<dt><b>-f [optional &nbsp;string &nbsp;part &nbsp;of &nbsp;filename]</b> </dt>
@@ -339,8 +340,7 @@ file (scroll.html). Alias -h
<dt><b>--keep-processing-files [filename/wildcard/url]</b>
</dt>
-<dd>
-<p>see --maintenance
+<dd>see --maintenance
<p> </dd>
<dt><b>-L</b> </dt>
@@ -362,8 +362,7 @@ indicated. (also see -V). Aliases -M and --keep-processing-files
<p> </dd>
<dt><b>-M [filename/wildcard/url]</b> </dt>
-<dd>
-<p>see --maintenance
+<dd>see --maintenance
<p> </dd>
<dt><b>-m [filename/wildcard/url]</b> </dt>
@@ -440,26 +439,33 @@ directory structure to multilingual. v3, experimental
<dd>see --pdf
<p> </dd>
+<dt><b>--qrcode [filename/wildcard]</b>
+</dt>
+<dd>generate QR code image of metadata (used in manifest). v3 only.
+<p> </dd>
+
<dt><b>--quiet [filename/wildcard]</b>
</dt>
<dd>quiet less output to screen.
<p> </dd>
-<dt><b>-q [filename/wildcard]</b> </dt>
-<dd>see --quiet
+<dt><b>-Q [filename/wildcard]</b> </dt>
+<dd>see --qrcode
<p> </dd>
-<dt><b>--rsync [filename/wildcard]</b>
+<dt><b>-q [filename/wildcard]</b>
</dt>
-<dd>copies sisu output files to remote host using rsync. This requires that
-sisurc.yml has been provided with information on hostname and username,
-and that you have your "keys" and ssh agent in place. Note the behavior
-of rsync different if -R is used with other flags from if used alone. Alone
-the rsync --delete parameter is sent, useful for cleaning the remote directory
-(when -R is used together with other flags, it is not). Also see --scp. Alias
+<dd>see --quiet
+<p> </dd>
-<p>-
-<p>R
+<dt><b>--rsync [filename/wildcard]</b> </dt>
+<dd>copies sisu output files to remote
+host using rsync. This requires that sisurc.yml has been provided with information
+on hostname and username, and that you have your "keys" and ssh agent in
+place. Note the behavior of rsync different if -R is used with other flags
+from if used alone. Alone the rsync --delete parameter is sent, useful for
+cleaning the remote directory (when -R is used together with other flags,
+it is not). Also see --scp. Alias -R
<p> </dd>
<dt><b>-R [filename/wildcard]</b> </dt>
@@ -470,25 +476,22 @@ the rsync --delete parameter is sent, useful for cleaning the remote directory
<dd>see --scp
<p> </dd>
-<dt><b>--sample-search-form
-[--webserv=webrick]</b> </dt>
-<dd>generate examples of (naive) cgi search form for sqlite
-and pgsql depends on your already having used sisu to populate an sqlite
-and/or pgsql database, (the sqlite version scans the output directories
-for existing sisu_sqlite databases, so it is first necessary to create
-them, before generating the search form) see -d -D and the database section
-below. If the optional parameter --webserv=webrick is passed, the cgi examples
-created will be set up to use the default port set for use by the webrick
-server, (otherwise the port is left blank and the system setting used,
-usually 80). The samples are dumped in the present work directory which
-must be writable, (with screen instructions given that they be copied to
-the cgi-bin directory). -Fv (in addition to the above) provides some information
-on setting up hyperestraier for sisu. Alias -F
+<dt><b>--sample-search-form [--webserv=webrick]</b> </dt>
+<dd>generate examples of (naive)
+cgi search form for sqlite and pgsql depends on your already having used
+sisu to populate an sqlite and/or pgsql database, (the sqlite version scans
+the output directories for existing sisu_sqlite databases, so it is first
+necessary to create them, before generating the search form) see -d -D and
+the database section below. If the optional parameter --webserv=webrick is
+passed, the cgi examples created will be set up to use the default port
+set for use by the webrick server, (otherwise the port is left blank and
+the system setting used, usually 80). The samples are dumped in the present
+work directory which must be writable, (with screen instructions given
+that they be copied to the cgi-bin directory). Alias -F
<p> </dd>
<dt><b>--scp [filename/wildcard]</b> </dt>
-<dd>copies
-sisu output files to remote host using scp. This requires that sisurc.yml
+<dd>copies sisu output files to remote host using scp. This requires that sisurc.yml
has been provided with information on hostname and username, and that you
have your "keys" and ssh agent in place. Also see --rsync. Alias -r
<p> </dd>
@@ -511,8 +514,7 @@ option. Note: (this option is tested only with zsh). Alias -S
<p> </dd>
<dt><b>--sisupod [filename/wildcard]</b> </dt>
-<dd>produces
-a zipped file of the prepared document specified along with associated
+<dd>produces a zipped file of the prepared document specified along with associated
images, by default named sisupod.zip they may alternatively be named with
the filename extension .ssp This provides a quick way of gathering the relevant
parts of a sisu document which can then for example be emailed. A sisupod
@@ -541,8 +543,7 @@ file to output directory. Alias -s
<dt><b>-S [filename/wildcard]</b>
</dt>
-<dd>
-<p>see --sisupod
+<dd>see --sisupod
<p> </dd>
<dt><b>-s [filename/wildcard]</b> </dt>
@@ -563,56 +564,56 @@ are omitted), has footnotes at end of each paragraph that contains them
--unix for unix linefeed (default) --msdos for msdos linefeed). Alias -t
<p> </dd>
-<dt><b>-T [filename/wildcard
-&nbsp;(*.termsheet.rb)]</b> </dt>
+<dt><b>-T [filename/wildcard &nbsp;(*.termsheet.rb)]</b> </dt>
<dd>standard form document builder, preprocessing feature
-<p>
-</dd>
+<p> </dd>
<dt><b>-t [filename/wildcard]</b> </dt>
<dd>see --txt
<p> </dd>
<dt><b>--urls [filename/wildcard]</b> </dt>
-<dd>prints url output
-list/map for the available processing flags options and resulting files
-that could be requested, (can be used to get a list of processing options
-in relation to a file, together with information on the output that would
-be produced), -u provides url output mapping for those flags requested for
-processing. The default assumes sisu_webrick is running and provides webrick
-url mappings where appropriate, but these can be switched to file system
-paths in sisurc.yml. Alias -U
+<dd>prints url output list/map for the available processing flags options and
+resulting files that could be requested, (can be used to get a list of
+processing options in relation to a file, together with information on
+the output that would be produced), -u provides url output mapping for those
+flags requested for processing. The default assumes sisu_webrick is running
+and provides webrick url mappings where appropriate, but these can be switched
+to file system paths in sisurc.yml. Alias -U
<p> </dd>
<dt><b>-U [filename/wildcard]</b> </dt>
<dd>see --urls
+
<p> </dd>
<dt><b>-u [filename/wildcard]</b> </dt>
-<dd>provides url mapping of output files for the flags requested for processing,
-also see -U
+<dd>provides url mapping of output files for the flags
+requested for processing, also see -U
<p> </dd>
<dt><b>--v2 [filename/wildcard]</b> </dt>
-<dd>invokes the sisu v2 document parser/generator.
-This is the default and is normally omitted.
+<dd>invokes the
+sisu v2 document parser/generator. This is the default and is normally omitted.
+
<p> </dd>
<dt><b>--v3 [filename/wildcard]</b> </dt>
-<dd>invokes
-the sisu v3 document parser/generator. Currently under development and incomplete,
-v3 requires &gt;= ruby1.9.2p180. You may run sisu3 instead.
+<dd>invokes the sisu v3 document parser/generator. Currently
+under development and incomplete, v3 requires &gt;= ruby1.9.2p180. You may run
+sisu3 instead.
<p> </dd>
<dt><b>--verbose [filename/wildcard]</b> </dt>
-<dd>provides verbose output of what is being generated, where output is placed
-(and error messages if any), as with -u flag provides a url mapping of files
-created for each of the processing flag requests. Alias -v
+<dd>provides verbose output of what
+is being generated, where output is placed (and error messages if any),
+as with -u flag provides a url mapping of files created for each of the
+processing flag requests. Alias -v
<p> </dd>
<dt><b>-V</b> </dt>
-<dd>on its own,
-provides <b>SiSU</b> version and environment information (sisu --help env)
+<dd>on its own, provides <b>SiSU</b> version and
+environment information (sisu --help env)
<p> </dd>
<dt><b>-V [filename/wildcard]</b> </dt>
@@ -621,6 +622,7 @@ provides <b>SiSU</b> version and environment information (sisu --help env)
<dt><b>-v</b> </dt>
<dd>on its own, provides <b>SiSU</b> version information
+
<p> </dd>
<dt><b>-v [filename/wildcard]</b> </dt>
@@ -628,11 +630,11 @@ provides <b>SiSU</b> version and environment information (sisu --help env)
<p> </dd>
<dt><b>--webrick</b> </dt>
-<dd>starts ruby&rsquo;s webrick
-webserver points at sisu output directories, the default port is set to
-8081 and can be changed in the resource configuration files. [tip: &nbsp;the &nbsp;webrick
-&nbsp;server &nbsp;requires &nbsp;link &nbsp;suffixes, &nbsp;so &nbsp;html &nbsp;output &nbsp;should &nbsp;be &nbsp;created &nbsp;using &nbsp;the
-&nbsp;-h &nbsp;option &nbsp;rather &nbsp;than and search -H &nbsp;; &nbsp;also, &nbsp;note &nbsp;-F &nbsp;webrick &nbsp;]. Alias -W
+<dd>starts ruby&rsquo;s webrick webserver
+points at sisu output directories, the default port is set to 8081 and
+can be changed in the resource configuration files. [tip: &nbsp;the &nbsp;webrick &nbsp;server
+&nbsp;requires &nbsp;link &nbsp;suffixes, &nbsp;so &nbsp;html output &nbsp;should &nbsp;be &nbsp;created &nbsp;using &nbsp;the &nbsp;-h &nbsp;option
+&nbsp;rather &nbsp;than -H &nbsp;; &nbsp;also, &nbsp;note &nbsp;-F &nbsp;webrick &nbsp;]. Alias -W
<p> </dd>
<dt><b>-W</b> </dt>
@@ -645,16 +647,17 @@ webserver points at sisu output directories, the default port is set to
<dt><b>-w [filename/wildcard]</b> </dt>
<dd>see --concordance
+
<p> </dd>
<dt><b>--xhtml [filename/wildcard]</b> </dt>
-<dd>produces xhtml/XML output for
-browser viewing (sax parsing). Alias -b
+<dd>produces xhtml/XML output for browser viewing
+(sax parsing). Alias -b
<p> </dd>
<dt><b>--xml-dom [filename/wildcard]</b> </dt>
-<dd>produces
-XML output with deep document structure, in the nature of dom. Alias -X
+<dd>produces XML output with
+deep document structure, in the nature of dom. Alias -X
<p> </dd>
<dt><b>--xml-sax [filename/wildcard]</b> </dt>
@@ -670,23 +673,24 @@ XML output with deep document structure, in the nature of dom. Alias -X
<p> </dd>
<dt><b>-Y [filename/wildcard]</b> </dt>
-<dd>produces a short sitemap entry for the document,
-based on html output and the sisu_manifest. --sitemaps generates/updates the
-sitemap index of existing sitemaps. (Experimental, [g,y,m &nbsp;announcement &nbsp;this
-&nbsp;week])
+<dd>produces a short sitemap entry for the document, based on html output and the sisu_manifest.
+--sitemaps generates/updates the sitemap index of existing sitemaps. (Experimental,
+[g,y,m &nbsp;announcement &nbsp;this &nbsp;week])
<p> </dd>
<dt><b>-y [filename/wildcard]</b> </dt>
-<dd>produces an html summary of output generated
-(hyperlinked to content) and document specific metadata (sisu_manifest.html).
-This step is assumed for most processing flags.
+<dd>produces an html
+summary of output generated (hyperlinked to content) and document specific
+metadata (sisu_manifest.html). This step is assumed for most processing flags.
+
<p> </dd>
<dt><b>--zap [filename/wildcard]</b> </dt>
-<dd>Zap, if used with other processing flags deletes output files of the type
-about to be processed, prior to processing. If -Z is used as the lone processing
-related flag (or in conjunction with a combination of -[mMvVq]), will remove
-the related document output directory. Alias -Z
+<dd>Zap, if used with other processing flags deletes
+output files of the type about to be processed, prior to processing. If
+-Z is used as the lone processing related flag (or in conjunction with a
+combination of -[mMvVq]), will remove the related document output directory.
+Alias -Z
<p> </dd>
<dt><b>-Z [filename/wildcard]</b> </dt>
@@ -750,24 +754,23 @@ and underscores.
<dt><b>--pg -v --import</b> </dt>
<dd>[filename/wildcard] imports data specified
-to postgresql db (rb.dbi) [ &nbsp;-dv &nbsp;--import &nbsp;sqlite &nbsp;equivalent]
+to postgresql db (rb.dbi) [ &nbsp;-dv and search --import &nbsp;sqlite &nbsp;equivalent]
<p> </dd>
<dt><b>--pg -v --update</b> </dt>
-<dd>[filename/wildcard]
-updates/imports specified data to postgresql db (rb.dbi) [ &nbsp;-dv &nbsp;--update &nbsp;sqlite
-&nbsp;equivalent]
+<dd>[filename/wildcard] updates/imports specified data to postgresql
+db (rb.dbi) [ &nbsp;-dv &nbsp;--update &nbsp;sqlite &nbsp;equivalent]
<p> </dd>
<dt><b>--pg --remove</b> </dt>
<dd>[filename/wildcard] removes specified data to postgresql
-db (rb.dbi) [ &nbsp;-d &nbsp;--remove &nbsp;sqlite &nbsp;equivalent]
+db (rb.dbi) [ &nbsp;-d --remove &nbsp;sqlite &nbsp;equivalent]
+
<p> </dd>
<dt><b>--pg --dropall</b> </dt>
-<dd>kills data" and drops
-(postgresql or sqlite) db, tables &amp; indexes [ &nbsp;-d --dropall &nbsp;sqlite &nbsp;equivalent]
-
+<dd>kills data" and drops (postgresql or sqlite) db, tables &amp; indexes
+[ &nbsp;-d --dropall &nbsp;sqlite &nbsp;equivalent]
<p> <br>
The -v is for verbose output.
<p> </dd>
@@ -790,39 +793,37 @@ and just want to do the same again.
<dt><b>-0 to -5 [filename &nbsp;or &nbsp;wildcard]</b> </dt>
<dd>Default
-shorthand mappings (note that the defaults can be changed/configured in
-the sisurc.yml file):
+shorthand mappings (for v3, note that the defaults can be changed/configured
+in the sisurc.yml file):
<p> </dd>
<dt><b>-0</b> </dt>
-<dd>-mNhwpAobxXyYv [this &nbsp;is &nbsp;the &nbsp;default &nbsp;action &nbsp;run &nbsp;when
-&nbsp;no &nbsp;i.e. &nbsp;on &nbsp;&rsquo;sisu &nbsp;[filename]&rsquo;]
+<dd>-NQhewpotbxXyYv [this &nbsp;is &nbsp;the &nbsp;default &nbsp;action &nbsp;run
+&nbsp;when &nbsp;no options &nbsp;are &nbsp;give, &nbsp;i.e. &nbsp;on &nbsp;&rsquo;sisu &nbsp;[filename]&rsquo;]
<p> </dd>
<dt><b>-1</b> </dt>
-<dd>-mhewpy
+<dd>-Qhewpoty
<p> </dd>
<dt><b>-2</b> </dt>
-<dd>-mhewpaoy
+<dd>-NQhewpotbxXy
+
<p> </dd>
<dt><b>-3</b> </dt>
-<dd>-mhewpAobxXyY
+<dd>-NQhewpotbxXyY
<p> </dd>
<dt><b>-4</b> </dt>
-<dd>-mhewpAobxXDyY
-
-<p>-
-<p>-
-<p>import
+<dd>-NQhewpotbxXDyY --update
<p> </dd>
<dt><b>-5</b> </dt>
-<dd>-mhewpAobxXDyY --update
+<dd>-NQhewpotbxXDyYv --update
<p> <br>
-add -v for verbose mode and -c for color, e.g. sisu -2vc [filename &nbsp;or
+add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename
+&nbsp;or &nbsp;wildcard]
<p> <br>
<p>consider -u for appended url info or -v for verbose output
@@ -1058,7 +1059,9 @@ similar to this one:
<pre> % SiSU master 2.0
@title: SiSU
:subtitle: Manual
- @creator: :author: Amissah, Ralph
+ @creator:
+ :author: Amissah, Ralph
+ @publisher: &nbsp;[publisher &nbsp;name]
@rights: Copyright (C) Ralph Amissah 2007, License GPL 3
@classify:
:type: information
@@ -1209,7 +1212,8 @@ level 1 heading (used where a stand-alone document may be imported into
another)
<p> <br>
<b>:A~ [heading &nbsp;text]</b> Top level heading [this &nbsp;usually &nbsp;has &nbsp;similar &nbsp;content
-&nbsp;to &nbsp;the &nbsp;] NOTE: the heading levels described here are in 0.38 notation, see heading
+&nbsp;to &nbsp;the &nbsp;title &nbsp;@title: &nbsp;] NOTE: the heading levels described here are in 0.38
+notation, see heading
<p> <br>
<b>:B~ [heading &nbsp;text]</b> Second level heading [this &nbsp;is &nbsp;a &nbsp;heading &nbsp;level &nbsp;divider]
@@ -1225,7 +1229,7 @@ are given (a number), otherwise takes the form 1~my_filename_for_this_segment
<p> <br>
<b>2~ [heading &nbsp;text]</b> Second level heading preceding substantive text of document
-or sub-heading 3 , the heading level that would normally be marked 1.1 or
+or sub-heading 3, the heading level that would normally be marked 1.1 or
1.2 or 1.3 or 2.1 etc. in a document.
<p> <br>
<b>3~ [heading &nbsp;text]</b> Third level heading preceding substantive text of document,
@@ -1267,21 +1271,21 @@ html
+{inserted text}+
- \-{strikethrough}\-
+ -{strikethrough}-
#{monospace}#
</pre>
<p> <br>
<b>resulting output:</b>
<p> <br>
-normal text, <b>emphasis,</b> <b>bold text,</b> <i>italics,</i> <i>underscore</i> , "citation", ^superscript^,
+normal text, <b>emphasis,</b> <b>bold text,</b> <i>italics,</i> <i>underscore,</i> "citation", ^superscript^,
[subscript], ++inserted text++, --strikethrough--, monospace
<p> <br>
<p>normal text
<p> <br>
-<b>emphasis</b> [note: &nbsp;can &nbsp;be &nbsp;configured &nbsp;to &nbsp;be &nbsp;represented &nbsp;by &nbsp;bold, &nbsp;italics &nbsp;or
-&nbsp;underscore]
+<b>emphasis</b> [note: &nbsp;can &nbsp;be &nbsp;configured &nbsp;to &nbsp;be &nbsp;represented &nbsp;by &nbsp;bold, &nbsp;italics &nbsp;italics
+&nbsp;or &nbsp;underscore] or &nbsp;underscore]
<p> <br>
<p><b>bold text</b>
@@ -1362,7 +1366,29 @@ Numbered List (not to be confused with headings/titles, (document structure))
_# numbered list numbered list indented a., b., c., d., etc.
</pre>
<p>
-<h2><a name='sect28' href='#toc28'>9.4 Footnotes / Endnotes</a></h2>
+<h2><a name='sect28' href='#toc28'>9.4 Hanging Indents</a></h2>
+
+<p> <br>
+<b>markup example:</b>
+<p> <br>
+<pre> _0_1 first line no indent,
+ rest of paragraph indented one step
+ _1_0 first line indented,
+ rest of paragraph no indent
+ in each case level may be 0-9
+</pre>
+<p> <br>
+<b>resulting output:</b>
+<p> <br>
+ first line no indent, rest of paragraph indented one step<br>
+
+<p> <br>
+first line indented, rest of paragraph no indent
+<p> <br>
+
+<p>in each case level may be 0-9
+<p>
+<h2><a name='sect29' href='#toc29'>9.5 Footnotes / Endnotes</a></h2>
<p> <br>
Footnotes and endnotes are marked up at the location where they would be
@@ -1428,11 +1454,11 @@ normal text [^+2] continues
<p>the standard and pair notation cannot be mixed in the same document
<p>
-<h2><a name='sect29' href='#toc29'>9.5
+<h2><a name='sect30' href='#toc30'>9.6
Links</a></h2>
<p>
-<h2><a name='sect30' href='#toc30'>9.5.1 Naked Urls Within Text, Dealing with Urls</a></h2>
+<h2><a name='sect31' href='#toc31'>9.6.1 Naked Urls Within Text, Dealing with Urls</a></h2>
<p> <br>
urls found within text are marked up automatically. A url within text is
@@ -1479,7 +1505,7 @@ where a code block is used there is neither decoration nor hyperlinking,
deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
</pre>
<p>
-<h2><a name='sect31' href='#toc31'>9.5.2 Linking Text</a></h2>
+<h2><a name='sect32' href='#toc32'>9.6.2 Linking Text</a></h2>
<p> <br>
@@ -1509,9 +1535,6 @@ aboutSiSU &lt;<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a>
<p> <br>
about SiSU &lt;<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a>
&gt; [^14] markup
-<p>
-<h2><a name='sect32' href='#toc32'>9.5.3 Linking Images</a></h2>
-
<p> <br>
<b>markup example:</b>
<p> <br>
@@ -1561,10 +1584,10 @@ note at a heading level the same is automatically achieved by providing
names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of
auto-heading numbering, without further intervention.
<p>
-<h2><a name='sect33' href='#toc33'>9.6 Grouped Text</a></h2>
+<h2><a name='sect33' href='#toc33'>9.7 Grouped Text</a></h2>
<p>
-<h2><a name='sect34' href='#toc34'>9.6.1
+<h2><a name='sect34' href='#toc34'>9.7.1
Tables</a></h2>
<p> <br>
@@ -1609,7 +1632,7 @@ Tables</a></h2>
No. of articles, all languages | 25| 19,000| 138,000| 490,000|
862,000|1,600,000
\* Contributed at least ten times; \** at least 5 times in last month;
-\* more than 100 times in last month.
+\*\** more than 100 times in last month.
</pre>
<p> <br>
<b>resulting output:</b>
@@ -1622,7 +1645,7 @@ Tables</a></h2>
* Contributed at least ten times; ** at least 5 times in last month; ***
more than 100 times in last month.
<p>
-<h2><a name='sect35' href='#toc35'>9.6.2 Poem</a></h2>
+<h2><a name='sect35' href='#toc35'>9.7.2 Poem</a></h2>
<p> <br>
<b>basic markup:</b>
@@ -1774,7 +1797,7 @@ more than 100 times in last month.
<br>
<p>
-<h2><a name='sect36' href='#toc36'>9.6.3 Group</a></h2>
+<h2><a name='sect36' href='#toc36'>9.7.3 Group</a></h2>
<p> <br>
<b>basic markup:</b>
@@ -1930,7 +1953,7 @@ more than 100 times in last month.
<br>
<p>
-<h2><a name='sect37' href='#toc37'>9.6.4 Code</a></h2>
+<h2><a name='sect37' href='#toc37'>9.7.4 Code</a></h2>
<p> <br>
Code tags code{ ... }code (used as with other group tags described above)
@@ -2040,11 +2063,11 @@ opening code tag code{# as demonstrated here:
44 | death."&rsquo;
</pre>
<p>
-<h2><a name='sect38' href='#toc38'>9.7 Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></h2>
+<h2><a name='sect38' href='#toc38'>9.8 Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></h2>
<p>
-<h2><a name='sect39' href='#toc39'>9.7.1 Line-breaks</a></h2>
+<h2><a name='sect39' href='#toc39'>9.8.1 Line-breaks</a></h2>
<p> <br>
To break a line within a "paragraph object", two backslashes \\ with a space
@@ -2060,7 +2083,7 @@ The html break br enclosed in angle brackets (though undocumented) is available
in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being,
but is depreciated).
<p>
-<h2><a name='sect40' href='#toc40'>9.7.2 Page Breaks</a></h2>
+<h2><a name='sect40' href='#toc40'>9.8.2 Page Breaks</a></h2>
<p> <br>
Page breaks are only relevant and honored in some output formats. A page
@@ -2081,7 +2104,7 @@ page new &lt;:pn&gt; breaks the page, starts a new page.
page break &lt;:pb&gt; breaks a column, starts a new column, if using columns,
else breaks the page, starts a new page.
<p>
-<h2><a name='sect41' href='#toc41'>9.8 Book Index</a></h2>
+<h2><a name='sect41' href='#toc41'>9.9 Book Index</a></h2>
<p> <br>
To make an index append to paragraph the book index term relates to it,
@@ -2337,9 +2360,9 @@ text follows levels 1,2,3 and it is &rsquo;nice&rsquo; to do most work in those
<p> <br>
this is captured by the following file &rsquo;rename&rsquo; instruction:
<p> <br>
-<pre> rename &rsquo;s/.s[123]$/.sst/&rsquo; *.s{1,2,3}
- rename &rsquo;s/.r[123]$/.ssm/&rsquo; *.r{1,2,3}
- rename &rsquo;s/.si$/.ssi/&rsquo; *.si
+<pre> rename &rsquo;s/\.s[123]$/\.sst/&rsquo; *.s{1,2,3}
+ rename &rsquo;s/\.r[123]$/\.ssm/&rsquo; *.r{1,2,3}
+ rename &rsquo;s/\.si$/\.ssi/&rsquo; *.si
</pre>
<p> <br>
The internal document markup remains unchanged, from <b>SiSU</b> 0.16
@@ -2398,7 +2421,7 @@ be located locally or on a remote server for which a url is provided.
<h2><a name='sect47' href='#toc47'>12.1.1 Sisu Text - Regular Files (.sst)</a></h2>
<p> <br>
-The most common form of document in <b>SiSU</b> , see the section on <b>SiSU</b> markup.
+The most common form of document in <b>SiSU,</b> see the section on <b>SiSU</b> markup.
<p> <br>
&lt;<a href='http://www.sisudoc.org/sisu/sisu_markup'>http://www.sisudoc.org/sisu/sisu_markup</a>
@@ -2716,7 +2739,7 @@ list) may be found in:
<p> <br>
CSS files to modify the appearance of <b>SiSU</b> html, XHTML or XML may be placed
-in the configuration directory: ./_sisu/css ; ~/.sisu/css or; /etc/sisu/css
+in the configuration directory: ./_sisu/css; ~/.sisu/css or; /etc/sisu/css
and these will be copied to the output directories with the command sisu
-CC.
<p> <br>
@@ -2889,8 +2912,9 @@ streamed to four tables:
<p> <br>
* another the substantive texts by individual "paragraph" (or object)
-- along<br>
- with structural information, each paragraph being identifiable by its<br>
+-<br>
+ along with structural information, each paragraph being identifiable
+by its<br>
paragraph number (if it has one which almost all of them do), and the<br>
substantive text of each paragraph quite naturally being searchable
(both in<br>
@@ -2918,14 +2942,15 @@ so as to facilitate ease of searching.
<p> <br>
Being able to search a relational database at an object level with the
<b>SiSU</b> citation system is an effective way of locating content generated
-by <b>SiSU</b> object numbers, and all versions of the document have the same
-numbering, complex searches can be tailored to return just the locations
-of the search results relevant for all available output formats, with live
-links to the precise locations in the database or in html/xml documents;
-or, the structural information provided makes it possible to search the
-full contents of the database and have headings in which search content
-appears, or to search only headings etc. (as the Dublin Core is incorporated
-it is easy to make use of that as well).
+by <b>SiSU.</b> As individual text objects of a document stored (and indexed) together
+with object numbers, and all versions of the document have the same numbering,
+complex searches can be tailored to return just the locations of the search
+results relevant for all available output formats, with live links to the
+precise locations in the database or in html/xml documents; or, the structural
+information provided makes it possible to search the full contents of the
+database and have headings in which search content appears, or to search
+only headings etc. (as the Dublin Core is incorporated it is easy to make
+use of that as well).
<p>
<h2><a name='sect75' href='#toc75'>22. Postgresql</a></h2>
<br>
@@ -3050,7 +3075,8 @@ for <b>SiSU</b> to populate an sqlite database, this being part of <b>SiSU</b> -
sisu -d [instruction] [filename/wildcard &nbsp;if &nbsp;required]<br>
<p> <br>
- sisu -d --(sqlite|pg) --[instruction] [filename/wildcard &nbsp;if &nbsp;required]<br>
+ sisu -d --(sqlite|pg) --[instruction] [filename/wildcard &nbsp;if <br>
+ required]<br>
<p>
<h2><a name='sect86' href='#toc86'>23.4 Commands</a></h2>
@@ -3890,8 +3916,9 @@ the<br>
<p> <br>
NOTE:
<p> <br>
-[ &nbsp;.B &nbsp;SiSU &nbsp;parses &nbsp;files &nbsp;with &nbsp;long &nbsp;lines &nbsp;or &nbsp;line &nbsp;breaks, &nbsp;display &nbsp;linewrap
-&nbsp;(without &nbsp;line-breaks) &nbsp;is &nbsp;a &nbsp;convenient
+[ &nbsp;.B &nbsp;SiSU &nbsp;parses &nbsp;files &nbsp;with &nbsp;long &nbsp;lines &nbsp;or &nbsp;line &nbsp;breaks, but, &nbsp;display &nbsp;linewrap
+&nbsp;(without &nbsp;line-breaks) &nbsp;is &nbsp;a &nbsp;convenient editor &nbsp;feature &nbsp;to &nbsp;have &nbsp;for &nbsp;sisu &nbsp;markup]
+
<p>
<h2><a name='sect122' href='#toc122'>31. How Does Sisu Work?</a></h2>
<br>
@@ -3937,8 +3964,8 @@ beyond the Dublin core and easily further extended as required); the headers
may also contain processing instructions. <b>SiSU</b> markup is primarily an abstraction
of document structure and document metadata to permit taking advantage
of the basic strengths of existing alternative practical standard ways
-of representing documents [be &nbsp;that &nbsp;paper &nbsp;publication, &nbsp;sql &nbsp;search &nbsp;etc.] (html,
-epub, xml, odf, latex, pdf, sql)
+of representing documents [be &nbsp;that &nbsp;browser viewing, &nbsp;paper &nbsp;publication,
+&nbsp;sql &nbsp;search &nbsp;etc.] (html, epub, xml, odf, latex, pdf, sql)
<p> <br>
* for output produces reasonably elegant output of established industry
and institutionally accepted open standard formats.[3] takes advantage of
@@ -3969,8 +3996,7 @@ as<br>
<p> <br>
* sql - population of an sql database, (at the same object level that
-is used<br>
- to cite text within a document)<br>
+is used to cite text within a document)<br>
<p> <br>
Also produces: concordance files; document content certificates (md5 or
@@ -4029,7 +4055,7 @@ and images and sent as a zip file called a sisupod, if shared on the net
* generated document outputs may automatically be posted to remote sites.
<p> <br>
-* for basic document generation, the only software dependency is <b>Ruby</b> ,
+* for basic document generation, the only software dependency is <b>Ruby,</b>
and a few standard Unix tools (this covers plaintext, HTML, EPUB, XML,
ODF, LaTeX). To use a database you of course need that, and to convert the
LaTeX generated to pdf, a latex processor like tetex or texlive.
@@ -4191,108 +4217,143 @@ may be also be accessed via the html pages[^29]
&lt;<a href='http://www.jus.uio.no/sisu/man/sisu_webrick.1.html'>http://www.jus.uio.no/sisu/man/sisu_webrick.1.html</a>
&gt;<br>
-<p> 1. objects include: headings, paragraphs, verse, tables, images, but not
+<p>
+<ol>
+<b>.</b><li>objects include: headings, paragraphs, verse, tables, images, but not
footnotes/endnotes which are numbered separately and tied to the object
from which they are referenced.
<p> <br>
-2. i.e. the html, pdf, epub, odf outputs are each built individually and optimised
+</li><b>.</b><li>i.e. the html, pdf, epub, odf outputs are each built individually and optimised
for that form of presentation, rather than for example the html being a
saved version of the odf, or the pdf being a saved version of the html.
<p> <br>
-3. the different heading levels
+</li><b>.</b><li>
+<p>the different heading levels
<p> <br>
-4. units of text, primarily paragraphs and headings, also any tables, poems,
+</li><b>.</b><li>units of text, primarily paragraphs and headings, also any tables, poems,
<p>code-blocks
<p> <br>
-5. Specification submitted by Adobe to ISO to become a full open ISO specification
+</li><b>.</b><li>
+<p>Specification submitted by Adobe to ISO to become a full open ISO specification
+
+<p> <br>
&lt;<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a>
&gt;
<p> <br>
-6. ISO standard ISO/IEC 26300:2006
+</li><b>.</b><li>
+<p>ISO standard ISO/IEC 26300:2006
<p> <br>
-7. An open standard format for e-books
+</li><b>.</b><li>
+<p>An open standard format for e-books
<p> <br>
-*1. square brackets
+</dd>
+
+<dt><b>*1.</b> </dt>
+<dd>square brackets
<p> <br>
-*2. square brackets
+</dd>
+
+<dt><b>*2.</b> </dt>
+<dd>square brackets
<p> <br>
-+1. square brackets
+</dd>
+
+<dt><b>+1.</b> </dt>
+<dd>square brackets
<p> <br>
-8. &lt;<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a>
+</li><b>.</b><li>&lt;<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a>
&gt;
<p> <br>
-9. &lt;<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a>
+</li><b>.</b><li>&lt;<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a>
&gt;
<p> <br>
-10. From sometime after SiSU 0.58 it should be possible to describe SiSU
-markup using SiSU, which though not an original design goal is useful.
-<p>
-<br>
-11. files should be prepared using UTF-8 character encoding
+</li><b>.</b><li>From sometime after SiSU 0.58 it should be possible to describe SiSU markup
+using SiSU, which though not an original design goal is useful.
<p> <br>
-12. a footnote or endnote
+</li><b>.</b><li>
+<p>files should be prepared using UTF-8 character encoding
<p> <br>
-13. self contained endnote marker &amp; endnote in one
+</li><b>.</b><li>
+<p>a footnote or endnote
<p> <br>
-* unnumbered asterisk footnote/endnote, insert multiple asterisks if required
+</li><b>.</b><li>self contained endnote marker &amp; endnote in one
+<p> <br>
+</dd>
+
+<dt><b>*.</b> </dt>
+<dd>unnumbered asterisk footnote/endnote, insert multiple asterisks if required
<p> <br>
-** another unnumbered asterisk footnote/endnote
+</dd>
+
+<dt><b>**.</b> </dt>
+<dd>another unnumbered asterisk footnote/endnote
<p> <br>
-*3. editors notes, numbered asterisk footnote/endnote series
+</dd>
+
+<dt><b>*3.</b> </dt>
+<dd>editors notes, numbered asterisk footnote/endnote series
<p> <br>
-+2. editors notes, numbered asterisk footnote/endnote series
+</dd>
+
+<dt><b>+2.</b> </dt>
+<dd>editors notes, numbered asterisk footnote/endnote series
<p> <br>
-14 &lt;<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a>
+</li><b>.</b><li>&lt;<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a>
&gt;
<p> <br>
-15. &lt;<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a>
+</li><b>.</b><li>&lt;<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a>
&gt;
<p> <br>
-16. Table from the Wealth of Networks by Yochai Benkler &lt;<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a>
+</li><b>.</b><li>
+<p>Table from the Wealth of Networks by Yochai Benkler
+<p> <br>
+&lt;<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a>
&gt;
-
<p> <br>
-17. .ssc (for composite) is under consideration but ._sst makes clear that
-this is not a regular file to be worked on, and thus less likely that people
-will have subsequent processing. It may be however that when the resulting
-file is shared
+</li><b>.</b><li>.ssc (for composite) is under consideration but ._sst makes clear that this
+is not a regular file to be worked on, and thus less likely that people
+will have "accidents", working on a .ssc file that is overwritten by subsequent
+processing. It may be however that when the resulting file is shared .ssc
+is an appropriate suffix to use.
+<p> <br>
+</li><b>.</b><li>&lt;<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a>
+&gt;
<p> <br>
-19. &lt;<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a>
-&gt; <br>
&lt;<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a>
&gt; <br>
&lt;<a href='http://en.wikipedia.org/wiki/Postgresql'>http://en.wikipedia.org/wiki/Postgresql</a>
&gt; <br>
-20. &lt;<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a>
-&gt; <br>
+</li><b>.</b><li>&lt;<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a>
+&gt;
+<p> <br>
&lt;<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a>
&gt; <br>
-21. &lt;<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a>
+</li><b>.</b><li>&lt;<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a>
&gt;
<p> <br>
-22. (which could be extended further with current back-end). As regards scaling
+</li><b>.</b><li>(which could be extended further with current back-end). As regards scaling
of the database, it is as scalable as the database (here Postgresql) and
hardware allow.
<p> <br>
-23. of this feature when demonstrated to an IBM software innovations evaluator
+</li><b>.</b><li>of this feature when demonstrated to an IBM software innovations evaluator
in 2004 he said to paraphrase: this could be of interest to us. We have
large document management systems, you can search hundreds of thousands
of documents and we can tell you which documents meet your search criteria,
but there is no way we can tell you without opening each document where
within each your matches are found.
<p> <br>
-24. There is nothing to stop MySQL support being added in future.
+</li><b>.</b><li>There is nothing to stop MySQL support being added in future.
<p> <br>
-25. &lt;<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a>
+</li><b>.</b><li>&lt;<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a>
&gt;
<p> <br>
-26. &lt;<a href='http://www.jus.uio.no/sisu/man/sisu.8.html'>http://www.jus.uio.no/sisu/man/sisu.8.html</a>
+</li><b>.</b><li>&lt;<a href='http://www.jus.uio.no/sisu/man/sisu.8.html'>http://www.jus.uio.no/sisu/man/sisu.8.html</a>
&gt;
<p> <br>
-27. &lt;<a href='http://www.jus.uio.no/sisu/man'>http://www.jus.uio.no/sisu/man</a>
+</li><b>.</b><li>&lt;<a href='http://www.jus.uio.no/sisu/man'>http://www.jus.uio.no/sisu/man</a>
&gt;
<p> <br>
28. the <b>Debian</b> Free Software guidelines require that everything distributed
@@ -4301,7 +4362,9 @@ while freely distributable are not freely changeable.
<p> <br>
29. named index.html or more extensively through sisu_manifest.html <br>
-<p>
+<p> </li>
+</ol>
+
<h2><a name='sect131' href='#toc131'>See Also</a></h2>
<br>
<a href='http:~/bin/man2html?sisu:1'><i>sisu</i>(1)</a>
@@ -4366,20 +4429,20 @@ More information about <b>SiSU</b> can be found at &lt;<a href='http://www.sisud
<li><a name='toc25' href='#sect25'>9.1 Heading Levels</a></li>
<li><a name='toc26' href='#sect26'>9.2 Font Attributes</a></li>
<li><a name='toc27' href='#sect27'>9.3 Indentation and Bullets</a></li>
-<li><a name='toc28' href='#sect28'>9.4 Footnotes / Endnotes</a></li>
-<li><a name='toc29' href='#sect29'>9.5 Links</a></li>
-<li><a name='toc30' href='#sect30'>9.5.1 Naked Urls Within Text, Dealing with Urls</a></li>
-<li><a name='toc31' href='#sect31'>9.5.2 Linking Text</a></li>
-<li><a name='toc32' href='#sect32'>9.5.3 Linking Images</a></li>
-<li><a name='toc33' href='#sect33'>9.6 Grouped Text</a></li>
-<li><a name='toc34' href='#sect34'>9.6.1 Tables</a></li>
-<li><a name='toc35' href='#sect35'>9.6.2 Poem</a></li>
-<li><a name='toc36' href='#sect36'>9.6.3 Group</a></li>
-<li><a name='toc37' href='#sect37'>9.6.4 Code</a></li>
-<li><a name='toc38' href='#sect38'>9.7 Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></li>
-<li><a name='toc39' href='#sect39'>9.7.1 Line-breaks</a></li>
-<li><a name='toc40' href='#sect40'>9.7.2 Page Breaks</a></li>
-<li><a name='toc41' href='#sect41'>9.8 Book Index</a></li>
+<li><a name='toc28' href='#sect28'>9.4 Hanging Indents</a></li>
+<li><a name='toc29' href='#sect29'>9.5 Footnotes / Endnotes</a></li>
+<li><a name='toc30' href='#sect30'>9.6 Links</a></li>
+<li><a name='toc31' href='#sect31'>9.6.1 Naked Urls Within Text, Dealing with Urls</a></li>
+<li><a name='toc32' href='#sect32'>9.6.2 Linking Text</a></li>
+<li><a name='toc33' href='#sect33'>9.7 Grouped Text</a></li>
+<li><a name='toc34' href='#sect34'>9.7.1 Tables</a></li>
+<li><a name='toc35' href='#sect35'>9.7.2 Poem</a></li>
+<li><a name='toc36' href='#sect36'>9.7.3 Group</a></li>
+<li><a name='toc37' href='#sect37'>9.7.4 Code</a></li>
+<li><a name='toc38' href='#sect38'>9.8 Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></li>
+<li><a name='toc39' href='#sect39'>9.8.1 Line-breaks</a></li>
+<li><a name='toc40' href='#sect40'>9.8.2 Page Breaks</a></li>
+<li><a name='toc41' href='#sect41'>9.9 Book Index</a></li>
<li><a name='toc42' href='#sect42'>10. Composite Documents Markup</a></li>
<li><a name='toc43' href='#sect43'>Markup Syntax History</a></li>
<li><a name='toc44' href='#sect44'>11. Notes Related to Files-types and Markup Syntax</a></li>