Merge lp:~sschaefer/leo-editor/leo-manualUpdate into lp:leo-editor/old-trunk

[Stephen P. Schaefer]

Work on documentation.

Also changes the version number in setup.py from 4.6 to 4.7.1.

[lp:~sschaefer/leo-editor/leo-manualUpdate]

3069. By Stephen P. Schaefer <email address hidden> on 2010-05-04

Commit merge from EKR trunk.

3070. By Stephen P. Schaefer <email address hidden> on 2010-05-04

Merge trunk.

3071. By Stephen P. Schaefer <email address hidden> on 2010-05-06

Merge from trunk.

3072. By Stephen P. Schaefer <email address hidden> on 2010-05-06

Partial update of User Guide Chapter 4.

3073. By Stephen P. Schaefer <email address hidden> on 2010-05-06

Fetch changes from trunk.

3074. By Stephen P. Schaefer <email address hidden> on 2010-05-10

Revision of Chapter 4, Writing Programs in Leo.
Added LeoDoc.pdf as demo of eventual result from fixup.pl.

3075. By Stephen P. Schaefer <email address hidden> on 2010-05-11

Merge from trunk.
Chapter 4, more cleanup.

Unmerged revisions

3075. By Stephen P. Schaefer <email address hidden> on 2010-05-11

Merge from trunk.
Chapter 4, more cleanup.

3074. By Stephen P. Schaefer <email address hidden> on 2010-05-10

Revision of Chapter 4, Writing Programs in Leo.
Added LeoDoc.pdf as demo of eventual result from fixup.pl.

3073. By Stephen P. Schaefer <email address hidden> on 2010-05-06

Fetch changes from trunk.

3072. By Stephen P. Schaefer <email address hidden> on 2010-05-06

Partial update of User Guide Chapter 4.

3071. By Stephen P. Schaefer <email address hidden> on 2010-05-06

Merge from trunk.

3070. By Stephen P. Schaefer <email address hidden> on 2010-05-04

Merge trunk.

3069. By Stephen P. Schaefer <email address hidden> on 2010-05-04

Commit merge from EKR trunk.

3068. By Stephen P. Schaefer <email address hidden> on 2010-04-28

Get documentation generation working in Fedora 12 environment.
Proposed clarifications in Chapter 3.
Minor typo fixes.
Update version number in setup.py

=== modified file 'leo/doc/LeoDocs.leo'
--- leo/doc/LeoDocs.leo	2010-05-06 15:19:03 +0000
+++ leo/doc/LeoDocs.leo	2010-05-11 20:36:27 +0000
@@ -34,6 +34,10 @@
 <v t="ville.20090705225609.5736"><vh>&lt;&lt; html manual &gt;&gt;</vh></v>
 <v t="ville.20090705225609.5738"><vh>&lt;&lt; pdf manual &gt;&gt;</vh></v>
 </v>
+<v t="sps.20100504170836.13118"><vh>@button generate-full-userguide</vh>
+<v t="sps.20100504170836.13120"><vh>&lt;&lt; html manual &gt;&gt;</vh></v>
+<v t="sps.20100504170836.13122"><vh>&lt;&lt; pdf manual &gt;&gt;</vh></v>
+</v>
 <v t="ekr.20091006063434.13802"><vh>@button rst3</vh></v>
 <v t="ville.20090520232034.6345"><vh>@button rst-preview</vh></v>
 </v>
@@ -129,9 +133,9 @@
 <v t="ekr.20060111192108"><vh>When is deleting a node dangerous?</vh></v>
 </v>
 </v>
-<v t="ekr.20050830115714.12"><vh>How should I use Leo with bzr/git/hg/svn/cvs?</vh></v>
-<v t="ekr.20090706042206.14718"><vh>How can I use Leo cooperatively without sentinels?</vh></v>
-<v t="ekr.20050830115714.13"><vh>Using external files</vh>
+<v t="ekr.20050830115714.12"><vh>How Should I Use Leo With bzr/git/hg/svn/cvs?</vh></v>
+<v t="ekr.20090706042206.14718"><vh>How Can I Use Leo Cooperatively Without Sentinels?</vh></v>
+<v t="ekr.20050830115714.13"><vh>Using External Files</vh>
 <v t="ekr.20090501093330.3"><vh>@rst-option show-sections = False</vh>
 <v t="ekr.20050830115714.14"><vh>How do I inhibit sentinels in external files?</vh></v>
 <v t="ekr.20050830115714.16"><vh>How do I prevent Leo from expanding sections?</vh></v>
@@ -156,7 +160,7 @@
 <v t="ekr.20091105080104.9031"><vh>How do I specify qt fonts?</vh></v>
 </v>
 </v>
-<v t="ekr.20050830115714.118"><vh>Tips and techniques</vh>
+<v t="ekr.20050830115714.118"><vh>Tips and Techniques</vh>
 <v t="ekr.20090501093330.5"><vh>@rst-option show-sections = False</vh>
 <v t="ekr.20080527063511.1"><vh>What is an easy way to profile code?</vh></v>
 <v t="ekr.20070622185234"><vh>How can I do a simple find and replace?</vh></v>
@@ -169,7 +173,7 @@
 <v t="ekr.20060822111759"><vh>How can I reuse @button nodes in multiple files?</vh></v>
 </v>
 </v>
-<v t="ekr.20050830115714.76"><vh>Trouble shooting</vh>
+<v t="ekr.20050830115714.76"><vh>Trouble Shooting</vh>
 <v t="ekr.20090501093330.6"><vh>@rst-option show-sections = False</vh>
 <v t="ekr.20090130144433.1"><vh>How do I get help?</vh></v>
 <v t="ekr.20090130144433.2"><vh>How do I report bugs?</vh></v>
@@ -192,7 +196,7 @@
 <v t="ekr.20091105080104.11492"><vh>Why don't @font nodes work with the Qt gui?</vh></v>
 </v>
 </v>
-<v t="ekr.20071026055929"><vh>Unicode issues</vh>
+<v t="ekr.20071026055929"><vh>Unicode Issues</vh>
 <v t="ekr.20090501093330.7"><vh>@rst-option show-sections = False</vh>
 <v t="ekr.20061021164213"><vh>I can not enter non-ascii characters.  What can I do?</vh></v>
 <v t="ekr.20050830115714.9"><vh>Some characters in external files look funny. What can I do?</vh></v>
@@ -241,77 +245,105 @@
 <v t="EKR.20040524104904.26"><vh>Chapter 3: Using Outlines</vh>
 <v t="ekr.20050901101608"><vh>@rst html\outlines.html</vh>
 <v t="ekr.20050901101608.1"><vh>@rst-no-head links</vh></v>
+<v t="sps.20100504170836.13115"><vh>Outline Related</vh>
 <v t="EKR.20040524104904.27"><vh>Cloning nodes</vh></v>
 <v t="EKR.20040524104904.36"><vh>Creating and destroying nodes</vh></v>
-<v t="ekr.20060920145745"><vh>Creating and destroying multiple body editors</vh></v>
 <v t="EKR.20040524104904.37"><vh>Cutting, pasting and deleting nodes</vh></v>
 <v t="EKR.20040524104904.38"><vh>Dragging nodes</vh></v>
-<v t="EKR.20040524104904.39"><vh>Editing body text</vh></v>
 <v t="EKR.20040524104904.40"><vh>Expanding &amp; contracting nodes</vh></v>
-<v t="EKR.20040524104904.41"><vh>Indenting body text automatically</vh></v>
 <v t="EKR.20040524104904.43"><vh>Marking nodes</vh></v>
 <v t="EKR.20040524104904.44"><vh>Moving &amp; Reorganizing nodes</vh></v>
 <v t="ekr.20060929040750"><vh>Navigating through the outline</vh></v>
+</v>
+<v t="sps.20100504170836.13116"><vh>Body Related</vh>
+<v t="ekr.20060920145745"><vh>Creating and destroying multiple body editors</vh></v>
+<v t="EKR.20040524104904.39"><vh>Editing body text</vh></v>
+<v t="EKR.20040524104904.41"><vh>Indenting body text automatically</vh></v>
+</v>
+<v t="sps.20100504170836.13117"><vh>Miscellaneous</vh>
 <v t="EKR.20040524104904.45"><vh>Opening URL's automatically</vh></v>
 <v t="EKR.20040524104904.47"><vh>Resizing panes</vh></v>
 <v t="EKR.20040524104904.48"><vh>Undoing operations</vh></v>
 <v t="ekr.20070623145346.2"><vh>Using chapters</vh></v>
 </v>
 </v>
-<v t="ekr.20050831184021.5"><vh>Chapter 4: Programming with Leo</vh>
-<v t="ekr.20050828061213"><vh>@rst html\directives.html</vh>
+</v>
+<v t="ekr.20050831184021.5" a="E"><vh>Chapter 4: Programming with Leo</vh>
+<v t="ekr.20050828061213" a="E"><vh>@rst html\directives.html</vh>
 <v t="ekr.20050828160132"><vh>@rst-no-head links</vh></v>
 <v t="ekr.20050828061501.1"><vh>@rst-no-head Intro.</vh></v>
-<v t="ekr.20050828163557"><vh>Overview: creating and using external files</vh></v>
-<v t="ekr.20050828211507"><vh>Overview: summary of directives</vh></v>
-<v t="ekr.20050828061501.30"><vh>Reference: all about directives</vh>
+<v t="sps.20100506030816.13127"><vh>A Brief and Inaccurate History of Leo for Programming</vh>
+<v t="sps.20100507011942.17790"><vh>@rst-ignore-node \@root</vh></v>
+</v>
+<v t="ekr.20050828163557"><vh>Creating and using external files: recommendations</vh>
+<v t="sps.20100507011942.17791"><vh>@rst-ignore-node \@root</vh></v>
+</v>
+<v t="ekr.20050828211507"><vh>Overview: summary of directives</vh>
+<v t="sps.20100507011942.13175"><vh>Body pane modifiers</vh></v>
+<v t="sps.20100507011942.13176"><vh>Headline Family Directives</vh>
+<v t="sps.20100507011942.13177"><vh>External File Directives</vh></v>
+<v t="sps.20100507011942.13178"><vh>Body Text Generation Modifiers</vh></v>
+<v t="sps.20100507011942.13179"><vh>Tree Walk Modifiers</vh></v>
+</v>
+<v t="sps.20100507011942.13180"><vh>@rst-ignore-node @root Family Directives</vh></v>
+</v>
+<v t="ekr.20050828061501.30" a="E"><vh>Reference: all about directives</vh>
+<v t="sps.20100506153234.13367" a="E"><vh>Body pane modifiers</vh>
+<v t="ekr.20050828061501.32"><vh>@color, @nocolor, @nocolor-node and @killcolor</vh></v>
+<v t="ekr.20050828061501.42"><vh>@wrap and @nowrap</vh></v>
+</v>
+<v t="sps.20100507011942.13181" a="E"><vh>Headline Directive Family</vh>
+<v t="sps.20100506153234.13364" a="E"><vh>External file directives</vh>
+<v t="ekr.20050828174453.2"><vh>\@asis</vh></v>
+<v t="ekr.20080730212711.47" a="E"><vh>\@auto</vh>
+<v t="sps.20100507011942.17787"><vh>Perfect import checks</vh></v>
+<v t="sps.20100507011942.17789"><vh>@rst-ignore-node Commands related to @auto</vh></v>
+</v>
+<v t="ekr.20090307063422.4"><vh>\@edit</vh></v>
+<v t="ekr.20050828061501.51"><vh>\@file</vh></v>
+<v t="ekr.20050828174453.1"><vh>\@nosent</vh></v>
+<v t="ekr.20050828061501.39"><vh>\@path</vh></v>
+<v t="ekr.20080730212711.41"><vh>\@shadow</vh></v>
+<v t="ekr.20080730212711.44"><vh>\@thin</vh></v>
+</v>
+<v t="sps.20100506153234.13365" a="E"><vh>Text generation modifiers</vh>
 <v t="ekr.20050828173234"><vh>@ and @doc</vh></v>
-<v t="ekr.20050828061501.31"><vh>@all</vh></v>
-<v t="ekr.20050828174453.2"><vh>\@asis</vh></v>
-<v t="ekr.20080730212711.47"><vh>\@auto</vh></v>
 <v t="ekr.20050828173234.1"><vh>@c and @code</vh></v>
-<v t="ekr.20050828061501.32"><vh>@color, @nocolor, @nocolor-node and @killcolor</vh></v>
 <v t="ekr.20050828061501.33"><vh>@comment</vh></v>
 <v t="ekr.20050828061501.34"><vh>@delims</vh></v>
-<v t="ekr.20090307063422.4"><vh>@edit</vh></v>
 <v t="ekr.20050828061501.35"><vh>@encoding</vh></v>
-<v t="ekr.20050828061501.51"><vh>\@file</vh></v>
 <v t="ekr.20050828061501.36"><vh>@first</vh></v>
-<v t="ekr.20050828065955.3"><vh>@ignore</vh></v>
 <v t="ekr.20050828061501.37"><vh>@language</vh></v>
 <v t="ekr.20050828210721"><vh>@last</vh></v>
 <v t="ekr.20050828061501.38"><vh>@lineending</vh></v>
-<v t="ekr.20050828064254"><vh>@others</vh></v>
-<v t="ekr.20050828174453.1"><vh>\@nosent</vh></v>
-<v t="ekr.20050828061501.39"><vh>\@path</vh></v>
 <v t="ekr.20050828210721.1"><vh>@pagewidth</vh></v>
 <v t="ekr.20050828061501.40"><vh>@raw and @end_raw</vh></v>
+<v t="ekr.20050828210721.2"><vh>\@tabwidth</vh></v>
+<v t="sps.20100507011942.13198"><vh>\@verbatim</vh></v>
+</v>
+<v t="sps.20100506153234.13366" a="E"><vh>Tree walk modifiers</vh>
+<v t="sps.20100506153234.13369"><vh>\&lt;\&lt;section\&gt;\&gt;</vh></v>
+<v t="ekr.20050828061501.31"><vh>@all</vh></v>
+<v t="ekr.20050828065955.3"><vh>@ignore</vh></v>
+<v t="ekr.20050828064254"><vh>@others</vh></v>
+</v>
+</v>
+</v>
+<v t="sps.20100507011942.13182"><vh>@rst-ignore-tree \@root Directive Family</vh>
+<v t="sps.20100507011942.13200"><vh>\&lt;\&lt;section\&gt;\&gt;</vh></v>
+<v t="sps.20100507011942.13189"><vh>@ and @doc</vh></v>
+<v t="sps.20100507011942.13191"><vh>@c and @code</vh></v>
+<v t="sps.20100507011942.13193"><vh>@comment</vh></v>
+<v t="ekr.20050828061501.35"></v>
+<v t="sps.20100507011942.13195"><vh>@language</vh></v>
+<v t="ekr.20050828061501.38"></v>
+<v t="ekr.20050828210721.2"></v>
+<v t="sps.20100507011942.13185"><vh>\@path</vh></v>
 <v t="ekr.20080730212711.51"><vh>\@root</vh></v>
 <v t="ekr.20050828061501.41"><vh>\@root-code and @root-doc</vh></v>
-<v t="ekr.20080730212711.41"><vh>\@shadow</vh></v>
-<v t="ekr.20050828210721.2"><vh>\@tabwidth</vh></v>
-<v t="ekr.20080730212711.44"><vh>\@thin</vh></v>
-<v t="ekr.20080729064227.3"><vh>@unit</vh></v>
-<v t="ekr.20050828061501.50"><vh>@verbose, @terse, @quiet and @silent</vh></v>
-<v t="ekr.20050828061501.42"><vh>@wrap and @nowrap</vh></v>
-</v>
-<v t="ekr.20050828062751"><vh>Reference: creating and using external files</vh>
-<v t="ekr.20070814090306"><vh>\@auto</vh>
-<v t="ekr.20070814090306.2"><vh>Perfect import checks</vh></v>
-<v t="ekr.20070814090306.3"><vh>Commands related to @auto</vh></v>
-</v>
-<v t="ekr.20090307063422.7"><vh>\@edit</vh></v>
-<v t="ekr.20050828061501.51"></v>
-<v t="ekr.20050828174453.1"></v>
-<v t="ekr.20050828174453.2"></v>
-<v t="ekr.20050828061501.45"><vh>\@root reference</vh>
-<v t="ekr.20050828061501.47"><vh>Sections and section definitions</vh></v>
-<v t="ekr.20050828061501.48"><vh>Tangling @root trees with the Tangle commands</vh></v>
-<v t="ekr.20050828061501.49"><vh>Untangling @root trees with the Untangle commands</vh></v>
-</v>
-<v t="ekr.20080730212711.44"></v>
-<v t="ekr.20080730212711.41"></v>
-<v t="EKR.20040524104904.282"><vh>Converting @root trees to @file trees</vh></v>
+<v t="sps.20100507011942.13202"><vh>@unit</vh></v>
+<v t="sps.20100507011942.13197"><vh>@verbose, @terse, @quiet and @silent</vh></v>
+<v t="sps.20100507011942.13198"></v>
 </v>
 <v t="ekr.20050828061501.43"><vh>CWEB mode</vh></v>
 </v>
@@ -377,8 +409,8 @@
 <v t="EKR.20040524104904.181"><vh>How Leo Changes the Notion of Literate Programming</vh></v>
 </v>
 </v>
-<v t="ekr.20050831195331.4" a="E"><vh>Chapter 7: Scripting Leo with Python</vh>
-<v t="ekr.20040403171740" a="E"><vh>@rst html\scripting.html</vh>
+<v t="ekr.20050831195331.4"><vh>Chapter 7: Scripting Leo with Python</vh>
+<v t="ekr.20040403171740"><vh>@rst html\scripting.html</vh>
 <v t="ekr.20091104200540.6566"><vh>@rst-ignore</vh>
 <v t="ekr.20091107181442.26607"><vh>old, too complicated intro</vh></v>
 <v t="ekr.20091104200540.6567"><vh>details for later</vh></v>
@@ -465,7 +497,7 @@
 <v t="ekr.20100122073254.11655"><vh>Writing new importers</vh></v>
 </v>
 </v>
-<v t="EKR.20040524104904.245"><vh>Chapter 9: History of Leo</vh>
+<v t="EKR.20040524104904.245" a="E"><vh>Chapter 9: History of Leo</vh>
 <v t="ekr.20050901101608.5"><vh>@rst html\history.html</vh>
 <v t="ekr.20050901102147"><vh>@rst-no-head links</vh></v>
 <v t="ekr.20050902105852"><vh>Beginnings</vh></v>
@@ -4959,45 +4991,6 @@
 again when its penultimate clone is deleted. Clones are useful for making
 alternate views of a program. See `Clones and views`_ for full details.</t>
 <t tx="EKR.20040524104904.274">@language rest</t>
-<t tx="EKR.20040524104904.282">To convert an @root tree to an @file tree, choose the root of the tree to be
-converted, then do the following in the Python window::
-
-	import c2py
-	c2py.leo1to2()
-
-This script makes numerous changes throughout the tree. It does not, however,
-change @root to @file, or insert the needed @others directives. You must do that
-by hand.
-
-To convert @root trees to @file trees by hand:
-
-1. Change the @root node to an @file node. That is, delete the @root &lt;filename&gt;
-    from the body text and insert @file &lt;filename&gt; in the headline. Typically,
-    the root node contains a reference like &lt;&lt;methods of class x&gt;&gt; as the last
-    body text. Replace this reference with the @others directive. The expansion
-    of @others is all text that is not part of a section definition.
-
-2. Add @ to the start of all doc parts. Leo starts syntax coloring in code mode
-   rather than doc mode, so if a doc part starts body text it should start with
-   an '@' sign.
-   
-3. Replace all section definition lines (like &lt;&lt;name&gt;&gt;=) by @c. This results in
-   the node being added to the expansion of @others.
-
-4. Remove all unused code from the @file tree. Leo does not write external files
-   whose @file trees contain orphan or @ignore nodes.
-
-5. Make sure that all nodes defining a section have a headline that starts with
-   &lt;&lt;section&gt;&gt;. This will typically be true when converting @root trees that use
-   the @code directive.
-
-6. If a section is referenced in more than one node (a rare occurrence in my
-    code), clone the defining node and move one clone under each referencing
-    node.
-
-7. If a node contains the definitions of several sections, place each different
-   definition in a different node.
-</t>
 <t tx="EKR.20040524104904.307">The following error messages may be generated by the Tangle commands.
 
 Can not re-open temp file
@@ -5307,7 +5300,7 @@
 <t tx="EKR.20040524104904.36">The Insert Node command inserts a new node into the outline. The
 Delete Node command deletes a node and all its children.
 </t>
-<t tx="EKR.20040524104904.37">The Cut Outline, Paste Outline, Copy Outline and Delete Outline commands work on
+<t tx="EKR.20040524104904.37">The Cut Node, Paste Node, Copy Node and Delete Node commands work on
 nodes rather than text. For example, to delete a node, select the node and
 choose the Cut Outline or Delete Outline command. The Cut Outline and Copy
 Outline commands copy a text representation of the outline to the clipboard.
@@ -5315,20 +5308,21 @@
 deleted. You may copy this text representation into a body pane (or into any
 other text editor) using the Edit:Paste command.
 
-**Warning**: In practice, it is almost always wiser to move clones rather than
-cutting or pasting them. Cutting and pasting outlines preserves clones, but the
-links between clones only exist within the part of the outline that was pasted.
-Therefore, if you are cutting and pasting an outline containing clones it is
-best to cut and paste the *entire* outline. Alternatively, you can paste part of
-an outline, then delete all clones.</t>
-<t tx="EKR.20040524104904.38">You may drag an node (including all its descendants) from one place to another
+**Warning**: If you want to preserve the "cloned" attribute of a node, or want to paste the node as a clone of the node you cut or copied, use the paste-retaining-clones command (in the Outline menu, called "Past Node as Clone").
+The paste-node command instead creates a new, distinct version of the node you previously cut or copied, though if there were descendants nodes which were clones of each other, the new version will have parallel, distinct nodes that are also clones of each other (just not to the originals).  You may paste a node between .leo files, but there can be no clone relationship between them.
+
+There are places to which you are prevented from paste-retaining-clones, because it would cause a node to become a parent of itself, and thus cuase outline traversals like \@thin expansion to loop until they consumed all memory and crashed the program.  The leo outline is thus mathematically a *directed acyclic graph*: clones make it more flexible than a tree, but not a generalized graph.
+</t>
+<t tx="EKR.20040524104904.38">If you are using the Tk GUI ( by starting Leo with the argument --gui=tk ) you may drag a node (including all its descendants) from one place to another
 in an outline. To start a drag, press the main (left) mouse button while the
 cursor is over the icon for a node. The cursor will change to a hand icon. If
 you release the mouse button while the hand cursor is above the icon for another
 node, Leo will move the dragged node after that node. If you release the mouse
 button when the hand cursor is not over an icon, Leo will leave the outline pane
-as it is. Leo scrolls the outline pane as the result of mouse-moved events, so
-to continue scrolling you must keep moving the mouse.</t>
+as it is. Leo scrolls the outline pane as the result of mouse-moved events so near the top and bottom boundaries of the outline pane, so to continue scrolling you must keep moving the mouse.
+to continue scrolling you must keep moving the mouse.
+
+In both GUIs, you can use the move-outline-down and move-outline-up commands (bound to Ctrl-D and Ctrl-U by default) to move a node within the outline.  It may be easier to move within a large outline by cutting the node and pasting it.</t>
 <t tx="EKR.20040524104904.380">@language rest</t>
 <t tx="EKR.20040524104904.39">Leo auto indents unless @nocolor is in effect. Typing a newline
 automatically inserts the same leading whitespace present on the previous line.
@@ -5440,7 +5434,10 @@
 <t tx="EKR.20040524104904.40">You can expand or contract a node by clicking in the standard Windows Tree
 View icon to the left of the status icon. Expanding a node shows its immediate
 children; contracting a node hides all its children. The Expand All Subheads
-command expands all of a nodes offspring (children, grandchildren, etc.)</t>
+command expands all of a nodes offspring (children, grandchildren, etc.)
+
+Alt-Leftarrow on an expanded node will contract the node; Alt-RightArrow on a contracted node will expand the node.
+</t>
 <t tx="EKR.20040524104904.41">Leo auto indents body text following colons when @language Python is in
 effect. When the smart_auto_indent setting is True, Leo uses Emacs-style
 auto-indentation instead. This style of auto-indent aligns newly created lines
@@ -5467,13 +5464,7 @@
 selecting another location in the outline and pasting the node in the new
 location.
 
-**Warning**: In practice, it is almost always wiser to move clones rather than
-cutting or pasting them. Cutting and pasting outlines preserves clones, but the
-links between clones only exist within the part of the outline that was pasted.
-Therefore, if you are cutting and pasting an outline containing clones it is
-best to cut and paste the _entire_ outline. Alternatively, you can paste part of
-an outline, then delete all clones. 
-</t>
+See the **Warning** above in `Cutting, pasting and deleting nodes`_.</t>
 <t tx="EKR.20040524104904.45">Double-clicking the icon box of a node whose headline has the form::
 
     @url &lt;any url&gt;
@@ -8140,7 +8131,7 @@
 Naud Olivier, Joe Orr,
 Marc-Antoine Parent, Paul Paterson, Sean Shaleh Perry, Tim Peters, David Priest, Gary Poster, Scott Powell,
 Bruce Rafnel, Walter H. Rauser, Olivier Ravard, David Speed Ream, Rich Ries, Aharon Robbins, Guido van Rossum, David Rowe,
-Davide Salomoni, Steven Schaefer,Johannes Schöön, Wolfram Schwenzer, Casey Wong Kam Shun,
+Davide Salomoni, Stephen Schaefer,Johannes Schöön, Wolfram Schwenzer, Casey Wong Kam Shun,
 Gil Shwartz, Jim Sizelove, Paul Snively, Jurjen Stellingwerff, Phil Straus, David Szent-Györgyi,
 Kent Tenney, Jeffrey Thompson,
 Gabriel Valiente, Jim Vickroy, Tony Vignaux, Tom van Vleck,
@@ -8201,7 +8192,7 @@
 François Pinard wrote pymacs.
 Norman Ramsey created noweb and gave permission to quote from the noweb web documentation.
 Rich Ries has contributed a huge number of suggestions.
-Steven P. Schaefer pointed out major security problems lurking in hooks.
+Stephen P. Schaefer pointed out major security problems lurking in hooks.
 Gil Shwartz helped with unicode support.
 Phil Straus has been a great friend and constant support.
 Guido van Rossum created Python, Tkinter and the Python License.
@@ -10233,7 +10224,7 @@
 widget. This allows users to set Tk options.</t>
 <t tx="ekr.20050812090111">import leo.core.leoPlugins as leoPlugins
 
-rst3 = leoPlugins.getPluginModule('rst3')
+rst3 = c.rstCommands.rst3
 
 if rst3:
     controller = rst3.controllers.get(c)
@@ -10899,130 +10890,132 @@
 for that you should read `Leo's tutorial`_.
 This chapter assumes you are thoroughly familiar with the terminology introduced in the tutorial.
 **Note**: Are you *sure* you want to read this chapter?
-It contains many details that are no interest to the average user of Leo.
+It contains many details that are of no interest to the average user of Leo.
 I recommend using Leo for two weeks, or longer, before attempting this chapter.
 
 .. .. contents::</t>
-<t tx="ekr.20050828061501.30">The following sections give full details about each directive.
-The directives listed here may appear in headlines or body text.
+<t tx="ekr.20050828061501.30">The following sections give full details about each directive.  The `Headline Directive Family`_ directives will be supplemented by the `\@root Directive Family`_ once the latter has settled in its semantics; the same directive may have different effects depending on whether it is governed by a headline directive or an ``@root`` directive; at this point, just don't use ``@root``.
+
 </t>
-<t tx="ekr.20050828061501.31">The @all directive is valid only in @thin trees.
-The @all directive is similar to @others, but it is less restrictive:
-it dumps *all* nodes to the external file, including @ignore nodes and nodes that
-in an @others tree would be considered to be orphan nodes.
+<t tx="ekr.20050828061501.31">The ``@all`` directive is valid only in ``@thin`` style trees.
+The ``@all`` directive is similar to ``@others``, but it is less fastidious:
+it dumps the current node and *all* child nodes to the external file,
+including ``@ignore`` nodes and nodes that
+in an ``@others`` tree would be considered to be orphan nodes, generally ceasing to
+interpret any
+further tree walk or text generation modifying directives.
 
-The @all directive is required for files such as @thin leoProjects.txt in LeoPy.leo.
+The ``@all`` directive is required for files such as ``@thin`` leoProjects.txt in LeoPy.leo.
 leoProjects.txt contains so-called project nodes.
 It doesn't have any meaning as a program file: it is simply a collection of unrelated data.
-@others would not work at all: it would complain about lots of orphan nodes.</t>
+``@others`` would not work at all: it would complain about lots of orphan nodes.</t>
 <t tx="ekr.20050828061501.32">Syntax coloring is on by default in all body text.
 Leo formats comments and documentation parts in red,
 directives and C keywords in blue,
-strings and character constants in gray and all other text in code parts in black.
-The @nocolor directive disables syntax coloring for the body text in which it appears.
-No syntax coloring is done until an @color directive re-enables syntax coloring.
+strings and character constants in green and all other text in code parts in black.
+The color directives are recognized only in the first column of the body text.
+The ``@nocolor`` directive disables syntax coloring for the lines of body text after which it appears.
+No syntax coloring is done until an ``@color`` directive re-enables syntax coloring.
 
-If a node contains neither the @color nor the @nocolor directive
+If a node contains neither the ``@color`` nor the ``@nocolor`` directive
 it may inherit the syntax coloring attribute from an ancestor.
-The nearest ancestor that contains exactly one of the @color or @nocolor directives
+The nearest ancestor that contains exactly one of the ``@color`` or ``@nocolor`` directives
 will control the syntax coloring.
-**Ambiguous nodes**, nodes containing both the @color and @nocolor directives,
-never affect the coloring of their offspring.
+**Ambiguous nodes**, nodes containing both the ``@color`` and ``@nocolor`` directives,
+never affect the coloring of their children.
 
-The @nocolor-node directive completely disables coloring for that node only.
+The ``@nocolor-node`` directive completely disables coloring for that node only, taking precedence over other color directives that may be present.
 Descedant nodes are not affected.
 
-The @killcolor directive completely disables the colorizer for that node.
+The ``@killcolor`` directive completely disables the colorizer for that node.
 The result is much faster syntax coloring of large body text.
-As usual @killcolor may itself be overridden in descendant nodes.
-The differences between @killcolor and @nocolor:
-
-- @nocolor suppresses coloring only until the next @color directive.
-
-- @killcolor overrides @nocolor and @color directives.
-  Any node containing @killcolor is unambiguously a @killcolor node regardless of
-  whether that node also contains @color or @nocolor directives.
-
-**Note**:
-These directives do not affect the Tangle commands in any way.
-In particular, the Tangle commands will recognize section definitions as usual even
-after an @nocolor directive is seen.</t>
-<t tx="ekr.20050828061501.33">**Note**: the @comment directive is deprecated: you should use the @language
-directive whenever possible. However, sometimes using both @language and
-@comment is useful. For this to be effective the @comment directive should
-appear after the @language directive (in outline order).
-
-The Untangle command will not process an @root or @unit node if an @comment
-directive is in effect because Untangle can't be sure of properly parsing an
-external file if the language of the external file isn't known. It might be
-possible to assume some defaults in this case, but that is not done at present
-and is not a high priority. By default, the Tangle commands produces C-language
-comments. Single-line comments generated during tangling start with ///, while
-documentation parts are surrounded by \* and \*. The @comment directive allows
-you to use Tangle to produce shell and make files, as well as source code for
-other programming languages.
-
-The @comment directive may be followed by zero to three delimiters, separated by
+``@killcolor`` may itself be overridden in descendant nodes.
+The differences between ``@killcolor`` and ``@nocolor``:
+
+- ``@nocolor`` suppresses coloring only until the next ``@color`` directive.
+
+- ``@killcolor`` overrides ``@nocolor`` and ``@color`` directives.
+  Any node containing ``@killcolor`` is unambiguously a ``@killcolor`` node regardless of
+  whether that node also contains ``@color`` or ``@nocolor`` directives.
+
+``@killcolor`` and ``@nocolor-node`` differ in that the influence of ``@nocolor-node`` does not extend to descendant nodes, whereas ``@killcolor`` does influence descendant nodes.
+
+Leo recognizes the color directives only in the first column of body text, not in headlines.
+They have no effect on the "tangle" processes.
+</t>
+<t tx="ekr.20050828061501.33">**Note**: the ``@comment`` directive is deprecated: you should use the ``@language``
+directive whenever possible. However, sometimes using both ``@language`` and
+``@comment`` is useful. For this to be effective the ``@comment`` directive should
+appear after the ``@language`` directive (in outline order).  In such cases ``@comment``
+overrides the comment delimiters normally used by ``@language``.  Even in this case, you will generally
+do better combining ``@language`` and ``@delims``.  See `\@delims`_.  **DO NOT** combine ``@comment``
+with ``@delims``: the result is undefined and often generates a file which Leo cannot read and from
+which **data will be lost** after any subsequent ''save''.
+
+``@comment`` controls the text used to designate comment strings in the external file.
+By default, saving an ``@thin`` style tree produces C-language
+comments.  Single-line comments generated during generation start with ``//``, while
+documentation parts are surrounded by ``/*`` and ``*/``. The ``@comment`` directive allows
+you to work with source code for almost any programming languages.
+
+The ``@comment`` directive may be followed by zero to three delimiters, separated by
 whitespace. This directive sets the single-line comment delimiter and the
 opening and closing block comment delimiters as follows:
 
-====================== =====================================================================
-\@comment              no args\: restores the defaults to ///, /\* and \*/
----------------------- ---------------------------------------------------------------------
-\@comment ///          \1 arg\: sets the single-line comment and clears the other delims.
----------------------- ---------------------------------------------------------------------
-\@comment /\* \*/      \2 args\: sets the block comment delims; clears the single-line delim.
----------------------- ---------------------------------------------------------------------
-\@comment /// /\* \*/  \3 args\: sets all three delimiters.
-====================== =====================================================================
-
-If only one delimiter is given, Leo does not write any documentation parts while tangling.
-If two delimiters are given, block-style comments are used instead of single-line comments.
-For example, the @comment { } directive could be used to tangle Pascal files.
-
-The @comment directive is only recognized in @root, @unit, @file and @thin nodes,
-and the @comment directive must precede the first section name or @code directive.
-An @comment directive in the body text of an @unit directive specifies the current global defaults.
-An @comment directive in the body text of an @root directive affects comments generated for one root only.
-Comments in all other roots are governed by the global defaults.
-
-Leo will convert underscores in the @comment directives to significant spaces.  For example::
+========================  =====================================================================
+``@comment``              no args\: restores the defaults to ``//``, ``/*`` and ``*/``
+------------------------  ---------------------------------------------------------------------
+``@comment //``           \1 arg\: sets the single-line comment and clears the other delims.
+------------------------  ---------------------------------------------------------------------
+``@comment /* */``        \2 args\: sets the block comment delims; clears the single-line delim.
+------------------------  ---------------------------------------------------------------------
+``@comment // /* */``     \3 args\: sets all three delimiters.
+========================  =====================================================================
+
+If only one delimiter is given, Leo uses it to begin each line of a
+recognized documentation part (that is, one ungoverned by something like ``@all``).
+
+If two delimiters are given, Leo uses block-style comments instead of single-line comments.
+For example, ``@comment { }`` could be used with Pascal files.
+
+The ``@comment`` directive must precede the first section name or ``@c`` directive.
+
+Leo will convert underscores in the ``@comment`` directives to significant spaces.  For example::
 
     @comment REM_
 
-causes the comment delimiter to be "REM " (Note the trailing space).</t>
-<t tx="ekr.20050828061501.34">The @delims directive changes the comment strings used to mark sentinel lines.
+causes the comment delimiter to be "REM " (Note the trailing space).
+</t>
+<t tx="ekr.20050828061501.34">The ``@delims`` directive changes the comment strings used to mark sentinel lines from that point forward in the body text.
 This directive is often used to place Javascript text inside XML or HTML files.
-The delims directive is not valid in @root or @unit trees.
 
-The @delims directive contains one or two delimiters, separated by whitespace.
+The ``@delims`` directive contains one or two delimiters, separated by whitespace.
 If only one delim is present it delimits single-line comments.
 If two delims are present they delimit block comments.
-The @delims directive can not be used to change the comment strings at the start of the external file,
-that is, the comment strings for the @+leo sentinel and the initial @+body and @+node sentinels.
+The ``@delims`` directive can not be used to change the comment strings at the start of the external file,
+that is, the comment strings for the ``@+leo`` sentinel and the initial ``@+body`` and ``@+node`` sentinels.
 
-The @delims directive inserts @@delims sentinels into the external file.
-The new delimiter strings continue in effect until the next @@delims sentinel in the external file or
+The ``@delims`` directive inserts ``@@delims`` sentinels into the external file.
+The new delimiter strings continue in effect until the next ``@@delims`` sentinel in the external file or
 the end of the external file.
 
 **Note**: Leo can not revert to previous delimiters automatically;
-you must change back to previous delimiters using another @delims directive. For example::
+you must change back to previous delimiters using another ``@delims`` directive. For example::
 
     @delims /* */
     Javascript stuff
     @delims &lt;-- --&gt;
     HTML stuff
 
-Adding, deleting or changing @@delims sentinels will destroy Leo's ability to read the external file.
-Mistakes using the @delims directive have no effect on Leo,
-though such mistakes will thoroughly mess up a external file as far as compilers,
-HTML renderers, etc. are concerned.</t>
-<t tx="ekr.20050828061501.35">You may use the @encoding directive to specify the encoding used in an external file.
+Adding, deleting or changing ``@@delims`` sentinels will destroy Leo's ability to read the external file.
+``@delims`` affects only external files, having no effect on Leo's colorizer or internal data representation.
+Incorrect use will thoroughly corrupt the external file as far as compilers, HTML renderers, etc. are concerned.</t>
+<t tx="ekr.20050828061501.35">You may use the ``@encoding`` directive to specify the encoding used in an external file.
 You can't mix encodings in a single external file.  For example::
 
     @encoding iso-8859-1
 
-If the encoding used in an external file is not "utf-8" it is represented in the @+leo sentinel line, like this::
+If the encoding used in an external file is not "utf-8" it is represented in the ``@+leo`` sentinel line, like this::
 
     #@+leo-encoding=iso-8859-1.
 
@@ -11031,56 +11024,72 @@
 so encoding and decoding to and from utf-8 plain strings will never cause a problem.
 When reading or writing a character not in a "lossy" encoding (such as iso-8859-1),
 Leo converts such characters to '?' and issues a warning. </t>
-<t tx="ekr.20050828061501.36">The @first directive allows you to place lines at the very start of external files created
-by @thin and @file nodes.
-For example, the body text of @file spam.py
-might be::
+<t tx="ekr.20050828061501.36">The ``@first`` directive allows you to place lines at the very start of external files. 
+For example, the first line of body text of ``@file spam.py`` might be::
 
 	@first #! /usr/bin/env python
 
-The body text of @file foo.perl might be::
+The first line of body text of ``@file foo.pl`` might be::
 
 	@first #/usr/bin/perl
 
-@first directives are recognized only at the start of the body text of @file and @thin nodes.
-No text may precede @first directives.
-More than one @first directive may exist, like this::
+``@first`` directives are recognized only at the start of the body text of external
+file directive headline nodes, such as ``@file`` or ``@thin``.
+No text may precede ``@first`` directives.
+More than one ``@first`` directive may exist, like this::
 
 	@first #! /usr/bin/env python
 	@first # more comments.
-
-The @first directive is not valid in @root or @unit trees.</t>
-<t tx="ekr.20050828061501.37">The @language directive specifies the comment delimiters and string types used by the
+</t>
+<t tx="ekr.20050828061501.37">The ``@language`` directive specifies the comment delimiters and string types used by the
 Tangle and Untangle commands.
 This directive over-rides the default specified in the settings dialog.
 
-When the threading_colorizer plugin is enabled, the valid @language directives are::
-
-    @language x
-
-where the leo/modes folder contains the file x.py.  When the threading_colorizier plugin is not enabled,
-the 'old' colorizer is used and the valid @language directives are::
+The valid @language directives are::
 
     @language actionscript
+    @language ada
+    @language autohotkey
+    @language batch
     @language c
-    @language c++
+    @language cpp
+    @language css
     @language cweb
     @language elisp
+    @language forth
+    @language fortran
+    @language fortran90
+    @language haskell
+    @language haxe
     @language html
+    @language ini
     @language java
+    @language kshell
     @language latex
-    @language objective-c
+    @language lua
+    @language noweb
     @language pascal
     @language perl
     @language perlpod
+    @language php
     @language plain
+    @language plsql
     @language python
+    @language rapidq
     @language rebol
+    @language rest
+    @language rst
+    @language ruby
     @language shell
+    @language tex
     @language tcltk
+    @language vim
+    @language vimoutline
+    @language xml
+    @language xslt
 
 Shell files have comments that start with `#`.
-Case is ignored in the language specifiers, but not in the @language itself.
+Case is ignored in the language specifiers, but not in the ``@language`` itself.
 Thus, the following are equivalent::
 
     @language html
@@ -11090,462 +11099,164 @@
 but the following is invalid::
 
     @LANGUAGE html</t>
-<t tx="ekr.20050828061501.38">The @lineending directive sets the line endings for individual external files.
-This directive will override the output_newline setting.
-The @lineending *never* affects the line endings in .leo files themselves:
+<t tx="ekr.20050828061501.38">The ``@lineending`` directive sets the line endings for individual external files.
+This directive will override the ``@string output_newline`` setting.
+The ``@lineending`` *never* affects the line endings in .leo files themselves:
 .leo files must have consistent line endings!
 
 The valid forms of the @lineending directive are:
 
-======================= ======================================================
-\@lineending nl         The default, Linux.
------------------------ ------------------------------------------------------
-\@lineending cr         Mac
------------------------ ------------------------------------------------------
-\@lineending crlf       Windows
------------------------ ------------------------------------------------------
-\@lineending lf         Same as 'nl', not recommended
------------------------ ------------------------------------------------------
-\@lineending platform   Same as platform value for output_newline setting.
-======================= ======================================================</t>
-<t tx="ekr.20050828061501.39">The @path directives override the deprecated default_tangle_directory setting.
-
-The form of the \@path directive is @path *filename*,
-where *filename* is taken to be everything following \@path to the end of the line.
-
-If *filename* is an absolute filename the location of the external file is specified only by the filename.
-Otherwise, if *filename* is a relative filename, the location of the external file is relative to:
-
-1. the directory specified the applicable @path directive, or
-2. the "Default Tangle Directory" in the Settings dialog if no @path directive is in effect, or
+========================   ======================================================
+``@lineending nl``         The default, Linux.
+------------------------   ------------------------------------------------------
+``@lineending cr``         Mac
+------------------------   ------------------------------------------------------
+``@lineending crlf``       Windows
+------------------------   ------------------------------------------------------
+``@lineending lf``         Same as 'nl', not recommended
+------------------------   ------------------------------------------------------
+``@lineending platform``   Same as platform value for output_newline setting.
+========================   ======================================================</t>
+<t tx="ekr.20050828061501.39">The ``@path`` directives override the deprecated ``@directory default_tangle_directory`` setting.
+
+The form is:
+
+ ``@path`` *directory*
+
+where *directory* is taken to be everything following ``@path`` to the end of the line.
+
+When an external file directive such as ``@thin`` specifies an absolute path,
+no ``@path`` or setting affects the external file name.
+When an external file directive specifies a relative name,
+Leo derives the directory to which that path is relative as follows:
+
+1. the directory specified by ``@path`` directives in parent nodes, or
+2. the "Default Tangle Directory" in the Settings dialog if no ``@path`` directive is in effect, or
 3. the directory in which the .leo file resides if the .leo file has ever been saved.
 
+As parent nodes are examined beginning with the closest, Leo prepends relative path components, and finishes when prepending an absolute path.  In other words, ``@path`` directives specifying relative directory names are relative to their parent nodes.  If no ``@path`` directive gives an absolute directory name, then the topmost ``@path`` is relative to either (2) or (3) in the list above.
+
 An error occurs if no absolute path can be computed according to these rules,
-or if *filename* does not exist.</t>
-<t tx="ekr.20050828061501.40">The @raw and @end_raw directives are valid only within @file and @thin trees.
-The @raw directive starts a section of "raw" text. The @end_raw directive ends
+or if the derived directory name does not exist.
+</t>
+<t tx="ekr.20050828061501.40">The ``@raw`` directive starts a section of "raw" text. The ``@end_raw`` directive ends
 such a section, as does the end of body text. No section references are
 recognized within raw text, and no additional leading whitespace is generated
 within raw text when writing the external file.</t>
 <t tx="ekr.20050828061501.41">Leo allows you to choose whether body text in @root trees will start in code
-mode or doc mode by default. The @root-doc *filename* and @root-code *filename*
+mode or doc mode by default. The \@root-doc *filename* and \@root-code *filename*
 directives specify that body text is assumed to start in doc mode or code mode
-respectively. The options (-doc and -code) must follow @root immediately with no
-intervening whitespace. In effect, @root-code and @root-doc are two new
+respectively. The options (-doc and -code) must follow \@root immediately with no
+intervening whitespace. In effect, \@root-code and \@root-doc are two new
 directives.
 
-These @root options override the at_root_bodies_start_in_doc_mode setting. This
-setting affects only @root trees without options. Such "plain" @root trees are
+These \@root options override the at_root_bodies_start_in_doc_mode setting. This
+setting affects only \@root trees without options. Such "plain" \@root trees are
 now deprecated, which only means that it is better style to use either the
-\@root-code or @root-doc directive. The reason is simple: the meaning of plain
+\@root-code or \@root-doc directive. The reason is simple: the meaning of plain
 \@root trees will depend on the at_root_bodies_start_in_doc_mode setting. It's
 better to be explicit. By default, at_root_bodies_start_in_doc_mode = 1 for
-compatibility for old @root trees. I actually don't think this option is good
-for much; I created it before I created @root-doc and @root-code settings, and I
+compatibility for old \@root trees. I actually don't think this option is good
+for much; I created it before I created \@root-doc and \@root-code settings, and I
 decided it wouldn't hurt to leave it in. Anyway, you now have complete
-flexibility about how @root works, and in particular you can make @root work
-just like @file.</t>
-<t tx="ekr.20050828061501.42">By default, the body_pane_wraps setting controls whether body text wraps.
-You may override this setting for a particular tree using the @wrap and @nowrap directives.
-Only the first @wrap or @nowrap directive in a node has any effect.</t>
+flexibility about how \@root works.
+</t>
+<t tx="ekr.20050828061501.42">@nowrap
+By default, the ``@bool body_pane_wraps`` setting controls whether body text wraps.  You may override this setting for a particular tree using the ``@wrap`` and ``@nowrap`` directives.  Only the first ``@wrap`` or ``@nowrap`` directive in a node has any effect.  ``@wrap`` and ``@nowrap`` are recognized in both headlines and the body.  In the body, these directives are recognized only in the first column of body text.
+
+</t>
 <t tx="ekr.20050828061501.43">See `CWEB`_ for a discussion of the CWEB language. CWEB mode refers to how Leo
-tangles an outline when @language cweb is in effect or the cweb setting is in
+tangles an outline when ``@language cweb`` is in effect or the cweb setting is in
 effect. Leo treats *all* cweb code in cweb mode as unevaluated text. That is,
-Leo treats cweb control codes, including @&lt;...@&gt;, @&lt;..@&gt;=, @c, @, @* and @** as
+Leo treats cweb control codes, including ``@&lt;`` ... ``@&gt;``, ``@&lt;`` ... ``@&gt;=``, ``@c``, ``@``, ``@*`` and ``@**`` as
 "raw" text within cweb mode. Leo does *not* expand *cweb* section references
 when writing external files in cweb mode. However, Leo *does* expand *noweb*
 section references, so you may use noweb sections to organize cweb files! You
-can create *noweb* code and doc sections using the @code and @doc directives in
-place of @c and @ directives.
+can create *noweb* code and doc sections using the ``@code`` and ``@doc`` directives in
+place of ``@c`` and ``@`` directives.
 
-By default, cweb colors @, @* and @** sections using the same syntax coloring as
-for LaTeX. In addition, cweb colors C // and /*..*/ comments using LaTeX
+By default, cweb colors ``@``, ``@*`` and ``@**`` sections using the same syntax coloring as
+for LaTeX. In addition, cweb colors C ``//`` and ``/*`` .. ``*/`` comments using LaTeX
 coloring by default. You may change these defaults using the
-color_cweb_doc_parts_with_latex and color_cweb_comments_with_latex settings.
-</t>
-<t tx="ekr.20050828061501.45">This section discusses all aspects of @root trees.
-\@root directives must appear in body text, not headlines.
-
-You should carefully consider whether the extra flexibility afforded by @root
-trees is worth the extra bother. Indeed, @file trees are much easier to use than
-\@root trees:
-
-- @file and @thin trees use less markup than @root trees.
-  In particular, the @others directive is valid only within @file and @thin trees.
-
-- You must explicitly tangle and untangle @root trees using the Tangle and
-  Untangle commands.
-
-However, @root trees are more flexible than @file and @thin trees:
-
-- Sections may be defined anywhere within @root trees. Moreover, the @unit
-  directive expands the scope of section definitions in @root trees so that a
-  section may be referenced in several @root trees.
-
-- The meaning of section definitions in @root trees are independent of their position within the tree.
-</t>
-<t tx="ekr.20050828061501.47">Just as with @file trees, @root trees may contain code parts and doc parts.
-Code parts start with section definition lines (see below) or the @c directive.
-Doc parts start with @ directive.
-Doc parts continue until the end of body text or until the next @c or @ directive.
-
-Body text in @root trees contain zero or more code and doc parts in any order.
-The @c directive starts a named code section if the node's headline starts with &lt;&lt;section name&gt;&gt;.
-Otherwise, the @c directive is invalid.
-
-**Section definition lines** are lines of the form::
-
-	&lt;&lt; section name&gt;&gt;=
-
-(note the equal sign).
-Such lines also start named code parts.
-Named code parts in @root trees may be defined in several places.
-The definition of a named code part is the concatenation of all code parts with the same name.
-Body text that defines no code part is ignored.
-At least one non-blank line must follow the section definition line;
-empty sections are not allowed. 
-
-As in @file trees, paired &lt;&lt; and &gt;&gt; characters on the same line always denote a section name,
-even within comments and strings.
-Thus, &lt;&lt; and &gt;&gt; characters that do not delimit a section name must be placed on separate lines.
-If &lt;&lt; and &gt;&gt; are not paired on a line, they are treated as ordinary &lt;&lt; and &gt;&gt; characters.
-
-Here is a typical example of body text within an @root tree::
-
-    @ This method puts an open node sentinel for node v.
-    &lt;&lt;atFile methods&gt;&gt;=
-    def putOpenNodeSentinel(self,v):
-        if v.isAtFileNode() and v != self.root:
-            &lt;&lt; issue an error message &gt;&gt;
-        else:
-            s = self.nodeSentinelText(v)
-            self.putSentinel("@+node:" + s)
-
-Provided that the node's headline starts with &lt;&lt;atFile methods&gt;&gt;,
-the example above is equivalent to::
-
-    @ This method puts an open node sentinel for node v.
-    @c
-    def putOpenNodeSentinel(self,v):
-        if v.isAtFileNode() and v != self.root:
-            &lt;&lt; issue an error message &gt;&gt;
-        else:
-            s = self.nodeSentinelText(v)
-            self.putSentinel("@+node:" + s)
-
-We may not eliminate @c directives in @root trees.
-If we convert the doc part to a comment we are left with::
-
-    @c
-    # This method puts an open node sentinel for node v.
-    def putOpenNodeSentinel(self,v):
-        if v.isAtFileNode() and v != self.root:
-            &lt;&lt; issue an error message &gt;&gt;
-        else:
-            s = self.nodeSentinelText(v)
-            self.putSentinel("@+node:" + s)
-
-The following escape convention applies only in @root trees.
-Within a code part @@ in the first column (and only in the first column) stands for a single @ sign.</t>
-<t tx="ekr.20050828061501.48">Each @root tree represents a single external file. **Tangling** is the process
-of creating external files from @file, @thin or @root trees. Leo tangles @file
-and @thin trees automatically whenever an outline is saved. The user must tangle
-@root trees explicitly using one of the Tangle commands.
-
-Leo creates external files by expanding all section references in an @root node.
-Leo expands a section reference by substituting the code section itself for the
-section reference. This is a recursive process: the substituted code section may
-contain other code references which are themselves expanded, and so on.
-
-The outline provides a natural way of organizing an sections as follows::
-
-	Place the definition of a section S in a child of
-	the node containing the reference to S.
-
-If a section is referenced in more than one node, I usually place its definition
-in a node containing all the nodes that refer to it. Using this rule of thumb
-creates an outline whose structure mirrors the intrinsic organization of a
-program.
-
-The Tangle command creates external files from @root node. The @root directive
-indicates which sections constitute an output file. The text following a @root
-directive forms the entire content of the file, that is, after section
-references are expanded. An outline can contain arbitrarily many @root
-directives: Leo's Tangle commands will create one output file for each. The
-process of creating external files is called "tangling" because the code from
-the outline is rearranged to create the external files.
-
-For example, the following @root section shows a typical way of specifying a
-header file xx.h::
-
-    @root xx.h
-    #ifndef xx_defined
-    #define xx_defined
-    &lt;&lt; declarations of public constants of the xx class &gt;&gt;
-    &lt;&lt; declarations of public types of the xx class &gt;&gt;
-    &lt;&lt; declarations of public variables of the xx class &gt;&gt;
-    &lt;&lt; public prototypes of the xx class &gt;&gt;
-    #endif
-
-The Tangle commands will create the file xx.h from this body text by expanding
-all the section references. Incidentally, the introductory documentation will be
-included in the header file: any text preceding the @root directive is treated
-just like the doc part of a section definition.
-
-As another example, the following shows a typical way of specifying the
-corresponding xx.c file::
-
-    @root xx.c
-    &lt;&lt; public variables of the xx class &gt;&gt;
-    &lt;&lt; private types of the xx class &gt;&gt;
-    &lt;&lt; private variables of the xx class &gt;&gt;
-    &lt;&lt; private function prototypes of the xx class &gt;&gt;
-    &lt;&lt; methods of the xx class &gt;&gt;
-
-There are three menu commands that tangle an outline: Tangle, Tangle All and
-Tangle Marked. These commands are identical except for how much of the outline
-is tangled. The Tangle command tangles only the selected portion of the outline,
-the Tangle All command tangles the entire outline, and the Tangle Marked command
-tangles only marked headlines.
-
-The @root directive has three forms. All three forms mean exactly the same
-thing::
-
-    @root filename
-    @root "filename"
-    @root &lt;filename&gt;
-
-If *filename* is an absolute filename the location of the external file is specified only by the filename.
-Otherwise, if the @root node contains a relative filename, the location of the external file is relative to:
-
-1. the directory specified by an @path directive, or
-
-2. the default_tangle_directory setting if no @path directive is in effect, or
-
-3. the directory in which the .leo resides if the .leo file has ever been saved.
-
-An error occurs if no absolute path can be computed according to these rules,
-or if the filename or directory does not exist.
-
-The scope of a definition is the tree in which the definition is known. By
-default, Tangle commands look for section definitions only in the suboutline of
-the @root node being tangled. That is, all sections are assumed to be defined
-either in the body text of the headline, say h, containing the @root directive,
-or in the body texts of the descendants of h. The @unit directive explicitly
-indicates the scope of section definitions. When a Tangle command encounters the
-@unit directive it treats the suboutline containing the @unit command as the
-scope for all enclosed roots. This ensures that the group of roots in the
-subtree use the same section definitions.
-
-For example, suppose we have a tree organized as follows::
-
-	+ @unit
-		+ @root A
-		    sections in A
-		+ @root B
-		    sections in B
-
-The @unit directive insures that only sections defined in the unit can affect
-files A and B and that all sections definitions in A and B are compatible with
-each other.
-
-The Tangle commands ignore any tree containing an @ignore directive. This
-ensures that trees that contain cloned nodes or other subsidiary information do
-not cause the tangle commands to issue spurious error messages. It also ensures
-that a tree can never contribute a section definition to another part of the
-outline by mistake.</t>
-<t tx="ekr.20050828061501.49">The Untangle, Untangle All and Untangle Marked commands are the reverse of the
-corresponding Tangle commands. They update one or more @root nodes based on
-changes made to the corresponding external files.
-
-For example, suppose you create a new part of the outline and tangle it for the
-first time. When you compile external files for the first you are likely to get
-many syntax errors. You could fix those errors in the outline and tangle the
-outline again, but there is a much easier way: you fix the errors in the
-external files using the compiler's editor, then run the untangle command on the
-part of the outline that created the external file. The Untangle command updates
-the selected outline to match the changes in the external files. It's as simple
-as that. By the way, the Untangle command marks all the nodes in the outline
-that it updates, and you can examine all such nodes with the Go To Next Marked
-command in the Outline menu.
-
-You cannot use Untangle to update doc parts, or leading comments in code parts
-or "trivial" whitespace in code parts. This is a limitation of the Untangle
-command that cannot be fixed; Untangle has no way of knowing whether leading
-comments came from doc parts or are just leading comments.
-
-Untangle never changes the structure of an outline; it never inserts, deletes or
-moves nodes. Don't attempt to change the structure of an outline by modifying
-external files; it won't work. Also, never delete, move or alter the sentinel
-lines in external files written by the Tangle command. Such lines start with the
-comment delimiter followed by a section name.
-
-If you change the section name in a sentinel line Untangle will not update the
-code in the outline (with the old name) that generated the renamed section.
-Untangle warns about sections that appear in an external file but not in the
-outline. Untangle has no trouble with changed section references in external
-files; it is only changed sentinel lines that cause problems.
-
-Cloned nodes that generate code in several files may cause problems for
-Untangle. If Untangle is run separately on these external files, Untangle will
-update all cloned nodes each time it is run, so only the code in the last
-Untangle run will take effect. Therefore, the safe way to update text in cloned
-nodes is to make the change in the .leo file rather than the external files.
-</t>
-<t tx="ekr.20050828061501.50">The @verbose, @terse, @quiet and @silent directives determine
-how the Tangle command outputs comments in @root trees.
-Comments written by the user in code sections are always output.
-These directives control only:
-a) the comments containing doc sections and
-b) sentinel comments that delimit the beginning and end of code sections.
-
-When @verbose is in effect Tangle outputs all comments.
-When @terse is in effect, Tangle outputs only those comments necessary for Untangle to work.
-When @silent is in effect Tangle adds no additional comments.
-The @quiet directive is like @silent except that it does output leading sentinels as comments.
-Like @silent, @quiet inhibits untangling. 
-@verbose is the default.
-If more than one of these directives appear in the same body text the "most verbose" of these options will be in effect.</t>
-<t tx="ekr.20050828061501.51">The @file is a synonym for @thin. The @file directive creates an external file
-containing sentinels.</t>
-<t tx="ekr.20050828062751">In the following table all terms in each row are equivalent.
-The spelling in the first column is preferred:
-
-=========== =============== =================
-\@asis      \@file-asis     \@silent
------------ --------------- -----------------
-\@nosent    \@file-nosent   \@nosentinelsfile
-=========== =============== =================
-
-The following table summarizes the differences between
-the various kinds of @&lt;file&gt; trees.
-
-+---------+------------+-------------------+
-|         |            | Sections and      |
-| Type    | Sentinels? | @others expanded? |
-+---------+------------+-------------------+
-| @asis   | no         | no                |
-+---------+------------+-------------------+
-| @auto   | no         | no                |
-+---------+------------+-------------------+
-| @edit   | no         | yes               |
-+---------+------------+-------------------+
-| @file   | yes        | yes               |
-+---------+------------+-------------------+
-| @nosent | no         | yes               |
-+---------+------------+-------------------+
-| @root   | yes        | yes               |
-+---------+------------+-------------------+
-| @shadow | yes and no | yes               |
-+---------+------------+-------------------+
-| @thin   | yes        | yes               |
-+---------+------------+-------------------+
-
-Leo can not update the outline from changes made from external files unless
-those files contain sentinels. The primary source for @nosent and @asis trees
-are the outlines from which those files were created.
-
-For @shadow trees, Leo creates *two* files, a **public** file without sentinels,
-and a **private** file (by default in the .leo_shadow subfolder) containing
-sentinels. The primary sources for @shadow trees are the private files, updated
-by changes to the public file.
-</t>
-<t tx="ekr.20050828064254">The @others directive refers to the body text of all nodes *except* section
-definition nodes. The @others directive places the body text of section
+``@bool color_cweb_doc_parts_with_latex`` and ``@bool color_cweb_comments_with_latex`` settings.
+</t>
+<t tx="ekr.20050828061501.51">The ``@file`` is a synonym for ``@thin``. The ``@file`` directive creates an external file
+containing sentinels.
+
+This was not always so; if you work on the same .leo file with Leo 4.6
+or earlier as well as with Leo 4.7 and later, the two interpretations will corrupt
+each other: the workaround is to change all ``@file`` directives to ``@thin``, then save the
+leo file and its generated files.  ``@thin`` works regardless of Leo version, since all
+versions of Leo which support ``@thin``, support ``@thin`` in the
+same way.  If you work only with versions of Leo 4.7 or later, you avoid this issue entirely.
+</t>
+<t tx="ekr.20050828064254">The ``@others`` directive refers to the body text of all nodes *except* section
+definition nodes. The ``@others`` directive places the body text of section
 definition nodes in the external file in outline order.
 
-An @file or @thin tree may contain more than one @others directive. @others
-directives that descend from other @others directives refer only to unnamed
-nodes that descend from them. The @others directive that occurs highest in the
-@file tree refers to all other unnamed nodes.
-
-**Notes**:
-
-- No node may contain more than one @others directive.
-
-- No section definition node may intervene between an non-section definition
-  node containing body text and an @others node. In practice this is never a
-  problem.
-
-- The @others directive is not valid in @root or @unit trees.</t>
-<t tx="ekr.20050828065955.3">Generally speaking, @ignore directive prevents nodes from being processed.
-
-1. In the root node of any @auto, @edit, @file, @nosent, @root, @thin or @shadow tree, 
-   the @ignore directive prevents Leo from writing the external file. 
-
-2. @auto trees are an exception.  Everything, including @ignore directives, are written.
-   However, you can disable the writing of an @auto tree by putting an @ignore directive in an
-   ancestor of the @auto tree.
-
-3. At present, @ignore can be used to prevent the inclusion of a node that descends from @others.
-   This may be dubious behavior, but that's how Leo works.
-
-4. @ignore can be used by scripts and plugins as they like, but should preserve the behavior in item 1 above.</t>
+An external file directive tree may contain more than one ``@others`` directive. ``@others``
+directives that descend from other ``@others`` directives refer only to non-section
+nodes (i.e., nodes with headlines that do not contain the patter ``&lt;&lt;`` *section* ``&gt;&gt;``)
+that descend from them.  The ``@others`` directive that occurs highest in the
+``@file`` tree refers to all other unnamed nodes.  If ``@others`` occurs multiple in the same node, all non-section nodes appear at the location of the first instance of the ``@others`` directive; the remainder
+are remembered as sentinels but have no other content.
+</t>
+<t tx="ekr.20050828065955.3">Generally speaking, ``@ignore`` directive prevents nodes from being processed.
+
+#. In the root node of any ``@auto``, ``@edit``, ``@file``, ``@nosent``, ``@thin`` or ``@shadow`` tree, 
+   the ``@ignore`` directive prevents Leo from writing the external file. 
+
+#. ``@auto`` trees are an exception.  Everything, including ``@ignore`` directives occuring outside the root node, are written.
+   However, you can disable the writing of an ``@auto`` tree by putting an ``@ignore`` directive in the root node or in an
+   ancestor of the ``@auto`` tree.
+
+#. ``@ignore`` can be used by scripts and plugins as they like, but should preserve the behavior in item 1 above.</t>
 <t tx="ekr.20050828160132">.. External links...
 .. _`CWEB`:     http://www-cs-faculty.stanford.edu/~knuth/cweb.html
 .. _`noweb`:    http://www.eecs.harvard.edu/~nr/noweb/
 
 .. Relative links...
-.. _`@root reference`:      directives.html#id5 
+.. _`\@root reference`:      directives.html#id5 
 .. _front:                  front.html
 .. _`Leo's tutorial`:       intro.html
 .. _`@auto reference`:      directives#id1
-</t>
-<t tx="ekr.20050828163557">You create and use external files using @&lt;file&gt; directives.
-Most of these directives may only appear in headlines.
-Here are all the ways of creating external files:
+.. _ `History of Leo`:      history.html</t>
+<t tx="ekr.20050828163557">Differing external file directives are appropriate in different situations:
 
 \@asis
-  This directive copies body text verbatim, without even ensuring that
-  newlines terminate each node. Use this directive only when you must have
-  complete control over every character of the external file.
+  Use this directive only when you must have complete control over
+  every character of the external file: it copies body text verbatim,
+  without even ensuring that newlines terminate each node.  
 
 \@auto
-  Imports the external file when Leo reads an outline. See the `@auto
-  reference`_ for full details.
+  Use this when you don't want sentinels and Leo's parser for your language
+  works well.  It can be tricky: see the `\@auto reference`_ for full details.
 
 \@edit
-  Reads the external file into a single node.
+  Use for small files which can't have sentinels and it's ok for them to occupy a single node.
 
 \@file
-  As of Leo 4.7 b2, @file works exactly like @thin.  See below.
+  As of Leo 4.7 b2, ``@file`` works exactly like ``@thin``.  See `\@file`_
 
 \@thin
-  Creates external files containing sentinels that minimize conflicts
-  in source code control systems such as bzr.
-  Use @thin unless you have a good reason not to.
+  Use ``@thin`` unless you have a good reason not to.
 
 \@nosent
-  Creates external files without sentinels.
-  Use @nosent only as a last resort:
-  @auto or @shadow are usually a better choice.
-  Leo can not update @nosent trees from changes made to the external files.
-
-  The @bool force_newlines_in_at_nosent_bodies setting
-  controls whether Leo writes a trailing newline if non-empty body text does not
-  end in a newline. The default is True. In effect, the default value of this
-  setting was False in previous versions of Leo.
-
-\@root
-  This directive is the most flexible, and the most difficult to use.
-  **Note**: @root is a true directive: you must put @root in body text.
-  Historically, this was the first directive that created external files.
-  It comes closest in spirit to traditional literate programming tools.
-  However, it is seldom necessary to suffer the drawbacks of using @root.
-  My advice is to avoid using @root unless you have a compelling reason.
+  Use ``@nosent`` only as a last resort:
+  ``@auto`` or ``@shadow`` are usually a better choice.
+  Leo can not update ``@nosent`` trees from changes made to external files.
 
 \@shadow
-   This directive writes *two* external files, a **public** file without sentinels,
-   and a **private** file (by default in the .leo_shadow subfolder) containing sentinels.
-   This allows Leo to get the benefits of @thin trees,
-   without having sentinels in the public files that people care about.
-
+  Use this directive when you can't have sentinels in the **public** version
+  of the file, but want all the features of ``@thin`` trees.  This directive writes
+  *two* external files, a **public** file without sentinels, and a **private**
+  file (by default in the ``.leo_shadow`` subfolder) containing sentinels.
 To complicate matters further,
 you can use `CWEB`_ markup instead of `noweb`_ markup.
 See the section called `CWEB mode`_ for the details.
 The choice between CWEB and noweb is independent of the directive is used to create external files.</t>
-<t tx="ekr.20050828173234">The @ directive starts a doc part.
-Doc parts continue until an @c directive or the end of the body text.
+<t tx="ekr.20050828173234">The ``@`` directive starts a doc part.
+Doc parts continue until an ``@c`` directive or the end of the body text.
 For example::
 
     @ This is a comment in a doc part.
@@ -11553,49 +11264,66 @@
     The next line ends the doc part
     @c
 
-@doc is a synonym for @, but @ is preferred.</t>
-<t tx="ekr.20050828173234.1">The @c directive ends a doc part and begins a code part.
-@code is a synonym for @c, but @c is preferred.
-
-In @root and @unit trees, the headline must contain a valid section name.</t>
-<t tx="ekr.20050828174453.1">Leo writes @nosent trees just as for @thin trees,
-but Leo writes no sentinels at all.
-
-The @bool force_newlines_in_at_nosent_bodies setting
+``@doc`` is a synonym for ``@``, but ``@`` is preferred.
+
+The directive is only recognized in the first column.
+
+In ``@thin`` style external files, such documentation sections appear as comments, using comment
+characters appropriate to the language, or as specified by the prevailing ``@comment`` or ``@delims``
+directive.  
+
+A governing ``@asis``, ``@all``, ``@raw`` or ``@verbatim`` directive causes the directive
+to be uninterpreted and simply copied to the external file.
+</t>
+<t tx="ekr.20050828173234.1">The ``@c`` directive ends a doc part and begins a code part.
+``@code`` is a synonym for ``@c``, but ``@c`` is preferred.
+
+The directive is only recognized in the first column.
+
+A governing ``@asis``, ``@all``, ``@raw`` or ``@verbatim`` directive causes the directive
+to be uninterpreted and simply copied to the external file.
+</t>
+<t tx="ekr.20050828174453.1">Leo writes ``@nosent`` trees just as for ``@thin`` trees, except it writes no sentinels at all.
+All the information for the ``@nosent`` tree is kept in the .leo file,
+and Leo incorporates no changes from the external file.
+
+The ``@bool force_newlines_in_at_nosent_bodies`` setting
 controls whether Leo writes a trailing newline if non-empty body text does not
 end in a newline. The default is True. In effect, the default value of this
-setting was False in previous versions of Leo.</t>
-<t tx="ekr.20050828174453.2">Leo creates files from @asis trees by writing the body text of all nodes of the
-tree in outline order. Leo writes the body text *as is*, without recognizing
+setting was False in previous versions of Leo.
+</t>
+<t tx="ekr.20050828174453.2">Leo creates files from ``@asis`` trees by writing the body text of all nodes of the
+``@asis`` tree in outline order. Leo writes the body text *as is*, without recognizing
 section definitions, without expanding section references, and without treating
 directives specially in any way. In particular, Leo copies all directives,
-including @ or @c directives, to the external file as text.
+including ``@`` or ``@c`` directives, to the external file as text.
 
-Leo does recognize the @ignore directive in the *ancestors* of @asis nodes, so
-you may use the @ignore directive as usual to prevent Leo from writing @asis
+Leo does recognize the ``@ignore`` directive in the *ancestors* of ``@asis`` nodes, so
+you may use the ``@ignore`` directive as usual to prevent Leo from writing ``@asis``
 trees.
 
 **Notes**:
 
-- Within @asis trees only, if a headline starts with @@, Leo writes
-  everything in the headline following the @@ just before the corresponding
+- Within ``@asis`` trees only, if a headline starts with ``@@``, Leo writes
+  everything in the headline following the ``@@`` just before the corresponding
   body text.
 
-- Files created from @asis trees contain *nothing* not contained in body
-  text (or @@ headlines). In particular, if body text does not end in a
+- Files created from ``@asis`` trees contain *nothing* not contained in body
+  text (or ``@@`` headlines). In particular, if body text does not end in a
   newline, the first line from the next node will concatenated to the last line
-  of the preceding node.</t>
-<t tx="ekr.20050828210721">The @last directive allows you to place lines at the very end of external files
-created from @file and @thin nodes. The @last directive is recognized only at
-the end of body text of @file and @thin nodes. No text may follow @last
-directives. More than one @last directive may exist. For example, here is how a
+  of the preceding node.
+</t>
+<t tx="ekr.20050828210721">The ``@last`` directive allows you to place lines at the very end of external files (except those
+specified with ``@asis``).  The ``@last`` directive is recognized only at
+the end of body text of the external file directive (e.g., the ``@thin`` node).  No text may follow ``@last``
+directives. More than one ``@last`` directive may exist.  For example, here is how a
 PHP file might be set up::
 
 	@first &lt;?php
 	...
 	@last ?&gt;</t>
-<t tx="ekr.20050828210721.1">The @pagewidth directive overrides the page_width setting.
-The form of the @pagewidth directive is @pagewidth *n*,
+<t tx="ekr.20050828210721.1">The ``@pagewidth`` directive overrides the ``@int page_width`` setting.
+The form of the ``@pagewidth`` directive is ``@pagewidth`` *n*,
 where n is a positive integer that indicates the width of tangled pages in columns.
 For example::
 
@@ -11604,8 +11332,8 @@
 This setting only affects how Leo reformats doc parts, and how the Tangle command outputs block comments.
 
 </t>
-<t tx="ekr.20050828210721.2">The @tabwidth directive overrides the tab_width setting.
-The form of the @tabwidth directive is @tabwidth *n*,
+<t tx="ekr.20050828210721.2">The ``@tabwidth`` directive overrides the ``@int tab_width`` setting.
+The form of the ``@tabwidth`` directive is ``@tabwidth`` *n*,
 where n is a positive integer that indicates the width of tabs in spaces.
 For example::
 
@@ -11613,101 +11341,7 @@
 
 Negative values cause Leo to convert tabs to blanks.</t>
 <t tx="ekr.20050828211507">Here is a brief summary of each directive:
-
-- **\@**
-  Starts a doc part. @doc is a deprecated synonym.
-
-- **\@all**
-  Copies *all* descendant nodes to the external file.
-  Not valid in @root trees.
-
-- **\@asis**
-  Creates an external file without sentinels,
-  containing exactly the data in the @asis tree,
-  without expanding section references or @others directives.
-
-- **\@auto**
-  Imports the external file every time Leo reads the outline.
-  The read-at-auto-nodes and write-at-auto-nodes commands can
-  be used to read and write and @auto nodes.
-
-- **\@c**
-  Starts a code part. @code is a deprecated synonym.
-
-- **\@color**, **\@nocolor**, **\@nocolor-node** and **\@killcolor**
-  Control syntax coloring.
-
-- **\@comment**
-  Sets comment delimiters in @root and @unit trees.
-
-- **\@delims**
-  Sets comment delimiters in @thin and @file trees.
-
-- **\@edit**
-  Reads an external file into a single node.
-
-- **\@encoding**
-  Sets the Unicode encoding used in external files.
-
-- **\@file**
-  A synonym for @thin.
-
-- **\@first**
-  Forces lines to appear before the first sentinel of an external file.
-
-- **\@ignore**
-  Causes Leo to ignore all or part of an external file.
-
-- **\@language**
-  Sets the language used for syntax coloring **and**
-  sets the comment delimiters used in sentinel lines and in doc parts.
-
-- **\@last**
-  Forces lines to appear after the last sentinel of an external file.
-
-- **\@lineending**
-  Sets the line ending to be used in external files.
-
-- **\@others**
-  Copies all nodes *except* section definition nodes to the external file.
-
-- **\@nosent**
-  Same as @thin, but the external file contains no sentinels.
-
-- **\@pagewidth**
-  Sets the page width used to break doc parts into lines.
-
-- **\@path**
-  Set the path to be appended to filenames.
-
-- **\@raw** and **\@end_raw**
-  Delimit a section of 'raw' text.
-  Not valid in @root or @unit trees.
-
-- **\@root**, **\@root-code** and **\@root-code**
-  Start an @root tree.
-  The last two forms set the starting mode for body text.
-  These directives must appear in body text.
-
-- **\@shadow**
-  Creates two external files, a **public** file without sentinels,
-  and a **private** file containing sentinels.
-  Imports the file just as @auto does if the private file does not exist.
-
-- **\@tabwidth**
-  Sets the width of tabs.
-  Negative tab widths cause Leo to convert tabs to spaces.
-
-- **\@thin**
-  Creates an external file containing sentinels.
-  Thin external files miminize cvs and bzr conflicts.
-  All essential information is stored in the thin external file.
-
-- **@verbose**, **@terse**, **@quiet** and **@silent**
-  Set the verbosity of sentinels in external files from @root.
-
-- **\@wrap** and **\@nowrap**
-  Enable or disable line wrapping the Leo's body pane.</t>
+</t>
 <t tx="ekr.20050830074716">###################################
 What People Are Saying About Leo
 ###################################
@@ -12199,7 +11833,7 @@
 layers simultaneously: data structures, object structure, entity-relationship
 structure, client-server structure, design pattern structure, temporal
 structure, project management structure, and any other structure relevant to the
-system." -- Steven P. Schaefer
+system." -- Stephen P. Schaefer
 
 "A funny observation with Leo is that when I 'Leo-ise' other people's code, Leo
 makes the code's structure so transparent that design faults become very quickly
@@ -12608,7 +12242,7 @@
 The C compiler is happy: the C preprocessor strips out the offending line before the C
 compiler gets it.</t>
 <t tx="ekr.20050830115714.26"></t>
-<t tx="ekr.20050830115714.29">See the instructions are in LeoPy.leo in::
+<t tx="ekr.20050830115714.29">The instructions are in LeoPy.leo in::
 
     Notes:How To:How to add support for a new language section.
 
@@ -24264,102 +23898,6 @@
 
 - Added @bool big_outline_pane setting. False (legacy): Top pane contains outline and log panes.
   True: Top pane contains only the outline pane.  Bottom pane contains body and log panes.</t>
-<t tx="ekr.20070814090306">@auto trees allow people to use Leo in collaborative environments without using
-sentinels in the files Leo generates. In contrast to @nosent, @auto trees can
-change when the corresponding file changes outside of Leo.
-
-Leo will automatically recreate (import) all @auto trees when reading a .leo
-file, and will write all dirty @auto trees when saving a .leo file. There are
-two exceptions to this statement:
-
-1. Leo will never read (import) or write an @auto tree if
-the root @auto tree is under the influence of an @ignore directive.
-
-2. Saving a .leo file does not save @auto nodes if:
-
-a) they haven't been changed or,
-
-b) they do not contain a **significant** amount of information. An @auto tree
-   contains a significant amount of information if it has  children or if the
-   root node contains more than 10 characters.
-
-Leo creates @auto trees by parsing the corresponding external file. Parsers
-create descendant nodes of the @auto tree: one node for each class, method and
-function in the external file.
-
-Parsers presently exist for C, elisp, Java, Javascript, Pascal, PHP, Python and xml. Leo
-determines the language using the file's extension.  Notes:
-
-- If no parser exists for a language, the entire body of the external file is
-  copied to the body of the @auto node.
-
-- Javascript regexps that look like section references cause problems, but that
-  can not be helped.
-
-- Use the @data import_xml_tags setting in leoSettings.leo to specify the xml
-  tags that create outline nodes. By default, the **organizer tags** are html,
-  body, head, and div.</t>
-<t tx="ekr.20070814090306.2">Leo performs several checks to ensure that the result of importing an external
-file will be equivalent to the file that writing the @auto tree would produce.
-
-These checks can produces **errors** or **warnings**. Errors indicate a
-potentially serious problem. Leo inserts an @ignore directive in the @auto tree
-if any error is found. This @ignore directive prevents the @auto tree from
-modifying the external file. If you @ignore directive, a later write of the
-@auto tree will attempt to fix the problems that gave rise to the errors. There
-are no guarantees however.
-
-Before importing a file, Leo **regularizes** the leading whitespace of all lines
-of the original source file. That is, Leo converts blanks to tabs or tabs to
-blanks depending on the value of the @tabwidth directive in effect for the @auto
-node. Leo also checks that the indentation of any non-blank line is not a
-multiple of the indentation specified by the @tabwidth directive in effect for
-the @auto node.
-
-Leo cannot guarantee to reproduce the original source file exactly if problems
-are discovered while regularizing leading whitespace. **Strict languages** are
-languages such as Python for which leading whitespace must be preserved exactly
-as it appears in the original source file. Problems during regularizing generate
-errors for strict languages and warnings for non-strict languages.
-
-After importing a file, Leo verifies that writing the @auto node would create
-*exactly* the same file as the original file. Such file comparison mismatches
-generate errors unless the problem involves only leading whitespace for
-non-strict languages. Whenever a mismatch occurs the first non-matching line is
-printed.
-
-File comparison mismatches can arise for several reasons:
-
-1. Bugs in the import parsers. Please report any suspected bugs immediately.
-
-2. Underindented lines in classes, methods or function. An **underindented
-   line** is a line that is indented less then the starting line of the class,
-   method or function in which it appears. Leo outlines can not represent such
-   lines exactly: every line of node implicitly has at least the indentation of
-   any unindented line of the node.
-
-Leo will issue a warning (not an error) for underindented Python comment lines.
-Such lines can not change the meaning of Python programs.</t>
-<t tx="ekr.20070814090306.3">Three commands in the File:Read/Write menu allow you to manually read and
-write @auto nodes from the presently selected outline. As always, an @ignore
-directive in the @auto node or its ancestors will suppress any of these
-commands:
-
-- The Read @auto Nodes (read-at-auto-nodes) command reads all @auto nodes in the
-  presently selected outline. An @ignore directive will suppress this import.
-
-- The Write @auto Nodes (write-at-auto-nodes) command writes all @auto nodes. An
-  @ignore directive will suppress this import. Caution: the write will occur even
-  if Leo has not previously read the @auto node.
-
-- The Write Dirty @auto Nodes (write-dirty-at-auto-nodes) is the same as the
-  write-at-auto-nodes command, except that only changed @auto trees are written.
-
-Most users will rarely use these explicit commands, because reading and writing
-.leo files handles @auto nodes well enough. However, you can use the
-read-at-auto-nodes command to update @auto nodes without having to reload the
-.leo file.
-</t>
 <t tx="ekr.20070814104719">You enable or disable plugins using @enabled-plugins nodes in leoSettings files (leoSettings.leo, myLeoSettings.leo or the .leo file being loaded).  See `Specifying settings`_ for full details of settings files.
 
 The body text of the @enabled-plugins node contains a list of enabled plugins.
@@ -27176,9 +26714,6 @@
 actually not visible lines, but the second time you drag something in
 it's ok, as if it has an accurate count on visible lines now.
 </t>
-<t tx="ekr.20080729064227.3">The @unit directive expands the scope of section definitions in @root trees
-so that a section may be referenced in several @root trees.
-The @unit directive is ignored outside of @root trees.</t>
 <t tx="ekr.20080729064227.6">The timit button in unitTest.leo allows you to apply Python's timeit module.
 See http://docs.python.org/lib/module-timeit.html.
 The contents of @button timer is::
@@ -27305,28 +26840,28 @@
 please study the x.propagate_changed_lines method in leoShadow.py. This code is
 heavily commented.
 </t>
-<t tx="ekr.20080730212711.41">When writing an @shadow tree, Leo writes *two* files, a **public** file without
-sentinels, and a **private** file (by default in the .leo_shadow subfolder)
-containing sentinels. The primary sources for @shadow trees are the private
+<t tx="ekr.20080730212711.41">When writing an ``@shadow`` tree, Leo writes *two* files, a **public** file without
+sentinels, and a **private** file (by default in the ``.leo_shadow`` subfolder)
+containing sentinels. The primary sources for ``@shadow`` trees are the private
 files, updated by changes to the public file.
 
-When reading an @shadow tree, Leo will import the tree from the public file if
-the private file does not exist. **Important**: just as for @auto, the following
+When reading an ``@shadow`` tree, Leo will import the tree from the public file if
+the private file does not exist. **Important**: just as for ``@auto``, the following
 exceptions apply:
 
-1. Leo will never read (import) or write an @shadow tree if the @shadow tree is
-   under the influence of an @ignore directive.
+1. Leo will never read (import) or write an ``@shadow`` tree if the ``@shadow`` tree is
+   under the influence of an ``@ignore`` directive.
 
-2. Saving a .leo file does not save @shadow nodes if:
+2. Saving a .leo file does not save ``@shadow`` nodes if:
 
   a) they haven't been changed or,
 
-  b) they do not contain a **significant** amount of information. An @auto tree
+  b) they do not contain a **significant** amount of information. An ``@auto`` tree
      contains a significant amount of information if it has children or if the
      root node contains more than 10 characters.
 
-Leo imports shadow trees by parsing the corresponding public file, exactly as is
-done for @auto node. See the discussion of @auto above for details.
+Leo can do an initial import of ``@shadow`` trees by parsing the corresponding public file, exactly as is
+done for ``@auto`` node. See the discussion of `\@auto`_ for details.
 </t>
 <t tx="ekr.20080730212711.42">The first step in creating an @shadow tree is to create a node whose headline is
 @shadow *&lt;filename&gt;*. This is always safe, even if *&lt;filename&gt;* already
@@ -27350,64 +26885,65 @@
 **Note**: just as for @auto, Leo will never read (import) or write an @shadow tree if
 the @shadow node is under the influence of an @ignore directive.
 </t>
-<t tx="ekr.20080730212711.44">Creates an external file containing sentinels. Thin exteral files contain all
-information needed to recreate the @thin tree in the outline. The @all directive
-is valid only in @thin trees, not @file trees. In a collaborative environment,
+<t tx="ekr.20080730212711.44">Create an external file containing sentinels. An ``@thin`` external file contains all the
+information needed to recreate the ``@thin`` tree in the outline.  In a collaborative environment,
 where a version control system is utilized and everyone can use Leo for editing,
-@thin is the recommended way to hold most of the content.
+``@thin`` is the recommended way to hold most of the content.
 </t>
-<t tx="ekr.20080730212711.47">@auto trees allow people to use Leo in collaborative environments without using
-sentinels in the files Leo generates. In contrast to @nosent, @auto trees can
+<t tx="ekr.20080730212711.47">``@auto`` trees allow people to use Leo in collaborative environments without using
+sentinels in the files Leo generates. In contrast to ``@nosent``, ``@auto`` trees can
 change when the corresponding file changes outside of Leo.
 
-Leo will automatically recreate (import) all @auto trees when reading a .leo
-file, and will write all dirty @auto trees when saving a .leo file. There are
+Leo automatically recreates (imports) all ``@auto`` trees when reading a .leo
+file, and writes all dirty ``@auto`` trees when saving a .leo file. There are
 two exceptions to this statement:
 
-1. Leo will never read (import) or write an @auto tree if
-the root @auto tree is under the influence of an @ignore directive.
-
-2. Saving a .leo file does not save @auto nodes if:
-
-a) they haven't been changed or,
-
-b) they do not contain a **significant** amount of information. An @auto tree
+1. Leo never reads (imports) or writes an ``@auto`` tree if
+the root ``@auto`` tree is under the influence of an ``@ignore`` directive.
+
+2. Saving a .leo file does not save ``@auto`` nodes if:
+
+a) they haven't changed or,
+
+b) they do not contain a **significant** amount of information. An ``@auto`` tree
    contains a significant amount of information if it has  children or if the
    root node contains more than 10 characters.
 
-Leo creates @auto trees by parsing the corresponding external file. Parsers
+Leo creates ``@auto`` trees by parsing the corresponding external file. Parsers
 create descendant nodes of the @auto tree: one node for each class, method and
-function in the external file.
+function in the external file, and sometimes nodes for declarations, docstrings
+or other recognized components.
 
 Parsers presently exist for C, elisp, Java, Javascript, Pascal, PHP, Python and xml. Leo
 determines the language using the file's extension.  Notes:
 
-- If no parser exists for a language, the entire body of the external file is
-  copied to the body of the @auto node.
-
-- Javascript regexps that look like section references cause problems, but that
-  can not be helped.
-
-- Use the @data import_xml_tags setting in leoSettings.leo to specify the xml
+- If no parser exists for a language, Leo copies the entire body of the external file into the ``@auto`` node.
+
+- Javascript regexps that look like section references are dealt with using the ``@verbatim`` directive
+  which suppresses all directive interpretation in the single immediately following line
+  (the colorizer may remain confused).
+
+- Use the ``@data import_xml_tags`` setting to specify the xml
   tags that create outline nodes. By default, the **organizer tags** are html,
-  body, head, and div.</t>
-<t tx="ekr.20080730212711.51">The @root directive creates external files that are more flexible than @file,
+  body, head, and div.
+</t>
+<t tx="ekr.20080730212711.51">The \@root directive creates external files that are more flexible than @file,
 @thin, @shadow, etc.  The @root directive must appear in body text, not the headline.
 
-- Sections may be defined anywhere within @root trees.
-  Moreover, the @unit directive expands the scope of section definitions in @root trees
-  so that a section may be referenced in several @root trees.
+- Sections may be defined anywhere within \@root trees.
+  Moreover, the @unit directive expands the scope of section definitions in \@root trees
+  so that a section may be referenced in by any \@root trees beneath the @unit directive.
 
 - The meaning of section definitions in @root trees are independent of their position within the tree.
 
 However, this flexibility comes at a cost:
 
 - @thin and @file trees use less markup than @root trees.
-  In particular, the @others directive is valid only within @file and @thin trees.
-
-- You must explicitly tangle and untangle @root trees using the Tangle and Untangle commands.
-
-See `@root reference`_ for more details.</t>
+  In particular, the \@others directive is valid only within @file and @thin trees.
+
+- You must explicitly tangle and untangle \@root trees using the Tangle and Untangle commands.
+
+See `\@root reference`_ for more details.</t>
 <t tx="ekr.20080730212711.52">There is one boundary case that the update algorithm can not resolve.
 If a line is inserted at the boundary between nodes,
 the updated algorithm can not determine whether the line should be inserted
@@ -28432,22 +27968,15 @@
 
 - color is a tk color name, even when using the qt gui plugin.
 </t>
-<t tx="ekr.20090307063422.4">Reads a file into a single node.
-@edit is similar to @auto; saving a .leo file does not save dirty @edit nodes
-if they do not contain a **significant** amount of information. An @edit tree
+<t tx="ekr.20090307063422.4">Read a file into a single node.
+``@edit`` is similar to ``@auto`` in that saving a .leo file does not save a dirty ``@edit`` node
+unless it contains a **significant** amount of information.  An ``@edit`` tree
 contains a significant amount of information if it has children or if the root
-node contains more than 10 characters.
+node contains more than 10 characters.  In and ``@edit`` tree, Leo interprets text generation and tree walk
+directives in the manner of an ``@file`` or ``@thin`` subtree, but any such structure is lost
+once you close the leo window.
+
 </t>
-<t tx="ekr.20090307063422.7">Initially, Leo's File:Open command creates such nodes when opening any
-non-.leo file.
-
-When writing @edit nodes, Leo uses Leo's @auto write logic.  That is,
-no sentinels are written.
-
-When reading @edit nodes, Leo just puts then entire text of the file
-into the node, along with @language or @nocolor directives as
-appropriate.  These added directives will not change the file when it
-gets written because no sentinels are written.</t>
 <t tx="ekr.20090324085713.2">Leo 4.6 beta 1                                       March 23, 2009
 
 Leo 4.6 b1 is now available at:
@@ -29247,6 +28776,8 @@
          python configure.py 
          make
          sudo make install
+
+    E: If you have a pre-packaged way to install these libraries, please contribute!
 </t>
 <t tx="ekr.20090705111443.10370">Leo sends more detailed error messages to stderr,
 the output stream that goes to the console window. In Linux and MacOS
@@ -31173,7 +30704,7 @@
 commands`_ that apply to the body pane.
 </t>
 <t tx="ekr.20091130111843.6817">A **clone** is a node that appears in more than one place in a Leo outline.
-Clones are marked with a small red arrow in the icon box. All clones of a node
+Clones are marked with a small red circular arrow in the icon box. All clones of a node
 are actually *the same node*, so any change to one clone affects all clones. For
 example, inserting, moving or deleting any child of a clone will change all
 other clones on the screen.
@@ -31366,7 +30897,7 @@
   outside of Leo, Leo will update the corresponding \@thin tree to reflect those
   changes when Leo next opens the outline.
 
-- When you save your outline, Leo writes all **dirty** \@thin nodes. An \@thin
+- When you save your outline, Leo writes all **dirty** \@thin nodes. An \@thin node
   is dirty if the node or any of its descendant nodes has changed.
   **Important**: When Leo writes an external file, Leo writes all the essential
   information in the \@thin tree to the external file, *not* to the .leo file.
@@ -34574,6 +34105,467 @@
 containing the body text's cursor, **fcol** shows the cursor coordinate
 relative to the external file, not to the curent node. The relation
 **fcol &gt;= col** is always true.</t>
+<t tx="sps.20100504170836.13115"></t>
+<t tx="sps.20100504170836.13116"></t>
+<t tx="sps.20100504170836.13117"></t>
+<t tx="sps.20100504170836.13118">@language python
+import os
+pos = c.find_h("Users Guide")[0]
+c.selectPosition(pos)
+c.k.simulateCommand('rst3')
+&lt;&lt; html manual &gt;&gt;
+&lt;&lt; pdf manual &gt;&gt;
+</t>
+<t tx="sps.20100504170836.13120">d = c.scanAllDirectives(p)
+mandir = d.get('path') + "/html"
+g.es(mandir)
+os.chdir(mandir)
+os.system('make html')</t>
+<t tx="sps.20100504170836.13122"># you probably need to install several packages 
+# to create pdf (e.g. jadetex)
+mandir = d.get('path') + "/html"
+g.es(mandir)
+os.chdir(mandir)
+os.system('make latex')
+os.chdir('_build/latex')
+os.system('make all-pdf')
+</t>
+<t tx="sps.20100506030816.13127">Leo has an initially bewildering array of ways to turn outlines into external files.  This history, simplified to the point of inaccuracy, may help you decide which of the varieties are appropriate to your project.  For a better and more detailed history, see `History of Leo`_.
+
+The original external file directive was ``@root``, which has gone through several sets of semantics, and
+is about to change again, so it will not be described here until those semantics are settled.
+
+Patterns in how ``@root`` trees were used suggested a different and easier way of deriving code from the outline: ``@file``.  This directive occurs in the headline.  Instead of explicitly naming each section, just put an ``@others`` directive where you want all the otherwise unplaced child sections collected; if you want a section put in a more specific place, specifying ``&lt;&lt;`` *section* ``&gt;&gt;`` will put it at that location in the body, and consequently require that ``&lt;&lt;`` *section* ``&gt;&gt;`` appear as a child headline defining that section.  The other innovation with ``@file`` is what happens when Leo starts: there is an immediate "untangle" of each ``@file``, thus incorporating changes from outside Leo into Leo's model of the file.  Correspondingly, when Leo exits, you're prompted to "save" (tangle) any altered ``@file`` (including alterations to child nodes).
+
+The next mutation was ``@thin``.  ``@file`` created source code with sentinels containing almost, but not all, of what was needed to recreate the outline for the ``@file``.  That same information was in the .leo file.  Situations could arise where that information was inconsistent, and create headaches.  ``@thin`` was like ``@file``, except that *everything* needed to create the ``@thin`` outline goes into the sentinels, and *does not* go into the Leo file, thus severely reducing opportunities for inconsistency.  This has been so successful that the old ``@file`` directive now forcibly converts ``@file`` derived source code to ``@thin`` style sentinels, and otherwise acts as a synonym for ``@thin``.  (Beware, however, if you use both pre-4.7 and 4.7 *et post* versions of Leo with ``@file``: change each ``@file`` headline to ``@thin`` immediately, else the incompatible sentinels for ``@file`` between the versions will be most painful.)
+
+If you look at source code managed with ``@thin``, the sentinels will stand silently in their commented multitudes - which may be reassuring to the Leo user, but appear to the non-Leo reader as a massive invasion.  The sentinels are almost necessary for pulling in changes from external files, but if those sentinels are banished, any number of compromise approaches can be imagined - and most of them seem to have been implemented.  All these directives can appear in a headline and create files without sentinels: 
+
+\@auto
+  parses the external file to put language apppropriate nodes (modules, classes, methods, functions...) into an @thin-like outline
+  
+\@asis
+  does a strict tree walk to generate the file, ignoring ``@others`` and ``&lt;&lt;`` *section* ``&gt;&gt;`` references, keeps everything in the .leo file and ignores changes from outside Leo
+
+\@edit
+  honors markup directives like ``@others`` when writing the external file, but when opening the .leo file, the contents of the external file all go into one node, which *might* have a language directive (e.g., ``@language python``), but never any children
+
+\@nosent
+  writes files honoring the directives in the manner of ``@thin``, keeps copies of everything in the Leo file, and ignores changes introduced into the external file
+
+\@shadow
+  reads and writes two versions of each file, one without sentinels, and a hidden one with sentinels as if it were ``@thin``, then uses the sentinels in the hidden file to make sense of externally introduced changes to the unsentineled file
+
+There are subtleties and crucial details to each of these external file generation directives: read the descriptive sections carefully.</t>
+<t tx="sps.20100506153234.13364">These file directives are valid only in headlines, with the exception of ``@path``, which may appear in both a headline or a body.
+
+In the following table all terms in each row are equivalent.
+The spelling in the first column is preferred:
+
+=========== =============== =================
+\@asis      \@file-asis     \@silent
+----------- --------------- -----------------
+\@nosent    \@file-nosent   \@nosentinelsfile
+=========== =============== =================
+
+The following table summarizes the differences between
+the various kinds of external file directives.
+
++---------+------------+-------------------+
+|         |            | Sections and      |
+| Type    | Sentinels? | @others expanded? |
++---------+------------+-------------------+
+| @asis   | no         | no                |
++---------+------------+-------------------+
+| @auto   | no         | no                |
++---------+------------+-------------------+
+| @edit   | no         | yes               |
++---------+------------+-------------------+
+| @file   | yes        | yes               |
++---------+------------+-------------------+
+| @nosent | no         | yes               |
++---------+------------+-------------------+
+| @shadow | yes and no | yes               |
++---------+------------+-------------------+
+| @thin   | yes        | yes               |
++---------+------------+-------------------+
+
+The ``@all`` directive in any environment supercedes ``@others`` and section expansion.
+
+Leo can not update the outline from changes made from external files unless
+those files contain sentinels. The primary source for ``@nosent`` and ``@asis`` trees
+are the outlines from which those files were created.
+
+For ``@shadow`` trees, Leo creates *two* files, a **public** file without sentinels,
+and a **private** file (by default in the ``.leo_shadow`` subfolder) containing
+sentinels. The primary sources for ``@shadow`` trees are the private files, updated
+by changes to the public file.
+</t>
+<t tx="sps.20100506153234.13365"></t>
+<t tx="sps.20100506153234.13366"></t>
+<t tx="sps.20100506153234.13367"></t>
+<t tx="sps.20100506153234.13369">In the ``@auto``, ``@edit``, ``@file``, ``@nosent``, ``@shadow`` and ``@thin`` trees, ``&lt;&lt;`` *section* ``&gt;&gt;`` in the headline specifies that this node and its descendants define a named section; in the body of a node, it specifies the location at which the text of a named section (defined in a child node) is to be interpolated.
+
+As with nearly all other directives, sections are ignored in ``@asis`` trees or when governed by ``@all``.
+</t>
+<t tx="sps.20100507011942.13175">- **\@color**, **\@nocolor**, **\@nocolor-node** and **\@killcolor**
+  Control syntax coloring.
+
+- **\@wrap** and **\@nowrap**
+  Enable or disable line wrapping the Leo's body pane.
+</t>
+<t tx="sps.20100507011942.13176"></t>
+<t tx="sps.20100507011942.13177">- **\@asis**
+  Creates an external file without sentinels,
+  containing exactly the data in the ``@asis`` tree,
+  without expanding section references or ``@others`` directives.
+
+- **\@auto**
+  Imports the external file every time Leo reads the outline.
+  The ``read-at-auto-nodes`` and ``write-at-auto-nodes`` commands can
+  be used to read and write and ``@auto`` nodes.
+
+- **\@edit**
+  Reads an external file into a single node.
+
+- **\@file**
+  A synonym for ``@thin``.
+
+- **\@nosent**
+  Same as ``@thin``, but the external file contains no sentinels.
+
+- **\@path**
+  Set the path to be appended to filenames (influences all child external file directives).
+
+- **\@shadow**
+  Creates two external files, a **public** file without sentinels,
+  and a **private** file containing sentinels.
+  Imports the file just as ``@auto`` does if the private file does not exist.
+
+- **\@thin**
+  Creates an external file containing sentinels.
+  Thin external files miminize cvs and bzr conflicts.
+  All essential information is stored in the thin external file.
+</t>
+<t tx="sps.20100507011942.13178">- **\@**
+  Starts a doc part. ``@doc`` is a deprecated synonym.
+
+- **\@c**
+  Starts a code part. ``@code`` is a deprecated synonym.
+
+- **\@comment**
+  Sets comment delimiters.
+
+- **\@delims**
+  Sets comment delimiters in ``@thin`` and ``@file`` trees.
+
+- **\@encoding**
+  Sets the Unicode encoding used in external files.
+
+- **\@first**
+  Forces lines to appear before the first sentinel of an external file.
+
+- **\@last**
+  Forces lines to appear after the last sentinel of an external file.
+
+- **\@language**
+  Sets the language used for syntax coloring **and**
+  sets the comment delimiters used in sentinel lines and in doc parts.
+
+- **\@lineending**
+  Sets the line ending to be used in external files.
+
+- **\@pagewidth**
+  Sets the page width used to break doc parts into lines.
+
+- **\@raw** and **\@end_raw**
+  Delimit a section of 'raw' text.
+
+- **\@tabwidth**
+  Sets the width of tabs.
+  Negative tab widths cause Leo to convert tabs to spaces.
+
+- **\@verbatim**
+  Causes directives on the immediately following line to be uninterpreted.
+</t>
+<t tx="sps.20100507011942.13179">- **\&lt;\&lt;** *section* **\&gt;\&gt;**
+  In body, interpolates a named section; in headline, defines a named section.
+
+- **\@all**
+  Copies *all* descendant nodes to the external file, with node sentinels.
+  No further directives honored.
+ 
+- **\@ignore**
+  Causes Leo to skip processing all or part of an external file.
+
+- **\@others**
+  Copies all nodes *except* section definition nodes to the external file.</t>
+<t tx="sps.20100507011942.13180">- **\&lt;\&lt;** *section* **\&gt;\&gt;** and **\&lt;\&lt;** *section* **\&gt;\&gt;=**
+  Interpolate or define a named section of code.
+
+- **\@root**, **\@root-code** and **\@root-code**
+  Start an ``\@root`` tree.
+  The last two forms set the starting mode for body text.
+  These directives must appear in body text.
+
+- **\@**
+  Start a doc part. ``@doc`` is a deprecated synonym.
+
+- **\@c**
+  Start a code part. ``@code`` is a deprecated synonym.
+
+- **\@comment**
+  Set comment delimiters.
+
+- **\@language**
+  Set the language used for syntax coloring **and**
+  set the comment delimiters used in sentinel lines.
+
+- **\@lineending**
+  Set the line ending to be used in external files.
+
+- **\@tabwidth**
+  Set the width of tabs.
+  Negative tab widths cause Leo to convert tabs to spaces.
+
+- **\@unit**
+  Change the scope within which ``\@root`` section names are valid.
+
+- **@verbose**, **@terse**, **@quiet** and **@silent**
+  Set the verbosity of sentinels.</t>
+<t tx="sps.20100507011942.13181"></t>
+<t tx="sps.20100507011942.13182"></t>
+<t tx="sps.20100507011942.13185">The @path directives override the deprecated default_tangle_directory setting.
+
+The form of the \@path directive is ``\@path`` *directory*,
+where *directory* is taken to be everything following \@path to the end of the line.
+
+When an external file directive such as @thin or @root specifies an absolute path, no \@path or setting affects the external file name.  When the external file directive specifies a relative name, Leo derives the directory to which that path is relative as follows:
+
+1. the directory specified by @path directives in parent nodes, or
+2. the "Default Tangle Directory" in the Settings dialog if no @path directive is in effect, or
+3. the directory in which the .leo file resides if the .leo file has ever been saved.
+
+The closest parent with an absolute path takes precedence; \@path directives specifying relative directory names are relative to their parent nodes; if no \@path directive gives an absolute directory name, then the topmost @path is relative to either (2) or (3) in the list above.
+
+An error occurs if no absolute path can be computed according to these rules,
+or if the derived directory name does not exist.
+</t>
+<t tx="sps.20100507011942.13189">The @ directive starts a doc part.
+Doc parts continue until an @c directive or the end of the body text.
+For example::
+
+    @ This is a comment in a doc part.
+    Doc parts can span multiple lines.
+    The next line ends the doc part
+    @c
+
+\@doc is a synonym for @, but @ is preferred.
+
+In \@thin style external files, such documentation sections appear as comments, using comment
+characters appropriate to the language, or as specified by the prevailing @comment or @delims
+directive.  
+
+**NOTES**:
+
+- Following in the tradition of Literate Programming tangle,
+  content of the body of an \@root node or its subnodes  
+  which is not contained in the code part of a section definition
+  will not appear in the external file.
+
+- A governing @asis, @all, @raw or @verbatim directive causes the directive
+  to be uninterpreted and simply copied to the external file.
+</t>
+<t tx="sps.20100507011942.13191">The @c directive ends a doc part and begins a code part.
+@code is a synonym for @c, but @c is preferred.
+
+In @root and @unit trees, the headline must contain a valid section name.</t>
+<t tx="sps.20100507011942.13193">**Note**: the @comment directive is deprecated: you should use the @language
+directive whenever possible. However, sometimes using both @language and
+@comment is useful. For this to be effective the @comment directive should
+appear after the @language directive (in outline order).
+
+Untangle will not process an @root or @unit node if an @comment
+directive is in effect because @comment make parsing an
+external file ambiguous.  It might be
+possible to assume some defaults in this case, but that is not done at present
+and is not a high priority.
+(If you donate code and proper unit tests, it will be happily considered.)
+By default, tangle of an @root node or saving an @thin style tree produces C-language
+comments.  Single-line comments generated during tangling start with ``//``, while
+documentation parts are surrounded by ``/*`` and ``*/``. The @comment directive allows
+you to use Tangle to produce shell and make files, as well as source code for
+other programming languages.
+
+The @comment directive may be followed by zero to three delimiters, separated by
+whitespace. This directive sets the single-line comment delimiter and the
+opening and closing block comment delimiters as follows:
+
+========================  =====================================================================
+``@comment``              no args\: restores the defaults to ``//``, ``/*`` and ``*/``
+------------------------  ---------------------------------------------------------------------
+``@comment //``           \1 arg\: sets the single-line comment and clears the other delims.
+------------------------  ---------------------------------------------------------------------
+``@comment /* */``        \2 args\: sets the block comment delims; clears the single-line delim.
+------------------------  ---------------------------------------------------------------------
+``@comment // /\* \*/``   \3 args\: sets all three delimiters.
+========================  =====================================================================
+
+If only one delimiter is given and the external file is generated by \@root, tangle does not write
+any documentation parts; @thin style external files precede each line of a
+recognized (that is, ungoverned by something like @all) documentation part with the delimiter.
+
+If two delimiters are given, block-style comments are used instead of single-line comments.
+For example, ``@comment { }`` could be used to tangle Pascal files.
+
+The @comment directive is only recognized in \@root, \@unit, @file and @thin nodes,
+and the @comment directive must precede the first section name or @c directive.
+An @comment directive in the same body text as an @unit directive specifies the current global defaults.
+An @comment directive in the same body text as an @root directive affects comments generated for that root only.
+Comments in all other roots are governed by the global defaults.
+
+Leo will convert underscores in the @comment directives to significant spaces.  For example::
+
+    @comment REM_
+
+causes the comment delimiter to be "REM " (Note the trailing space).</t>
+<t tx="sps.20100507011942.13195">The @language directive specifies the comment delimiters and string types used by the
+Tangle and Untangle commands.
+This directive over-rides the default specified in the settings dialog.
+
+When the threading_colorizer plugin is enabled, the valid @language directives are::
+
+    @language x
+
+where the leo/modes folder contains the file x.py.  When the threading_colorizier plugin is not enabled,
+the 'old' colorizer is used and the valid @language directives are::
+
+    @language actionscript
+    @language c
+    @language c++
+    @language cweb
+    @language elisp
+    @language html
+    @language java
+    @language latex
+    @language objective-c
+    @language pascal
+    @language perl
+    @language perlpod
+    @language plain
+    @language python
+    @language rebol
+    @language shell
+    @language tcltk
+
+Shell files have comments that start with `#`.
+Case is ignored in the language specifiers, but not in the @language itself.
+Thus, the following are equivalent::
+
+    @language html
+    @language HTML
+    @language hTmL
+
+but the following is invalid::
+
+    @LANGUAGE html</t>
+<t tx="sps.20100507011942.13197">The @verbose, @terse, @quiet and @silent directives determine
+how the Tangle command outputs comments in @root trees.
+Comments written by the user in code sections are always output.
+These directives control only:
+a) the comments containing doc sections and
+b) sentinel comments that delimit the beginning and end of code sections.
+
+When @verbose is in effect Tangle outputs all comments.
+When @terse is in effect, Tangle outputs only those comments necessary for Untangle to work.
+When @silent is in effect Tangle adds no additional comments.
+The @quiet directive is like @silent except that it does output leading sentinels as comments.
+Like @silent, @quiet inhibits untangling. 
+@verbose is the default.
+If more than one of these directives appear in the same body text the "most verbose" of these options will be in effect.</t>
+<t tx="sps.20100507011942.13198">The ``@verbatime`` directive causes the immediately succeeding single line to be copied to the generated file;
+in this way, content that might otherwise be mistaken for a section definition or directive can be escaped.
+</t>
+<t tx="sps.20100507011942.13200">In the \@auto, \@edit, \@file, \@nosent, \@shadow and \@thin trees, ``\&lt;\&lt;``*section*``\&gt;\&gt;`` in the headline specifies that this node and its descendants defines a named section; in the body of a node, it specifies the location at which the text of a named section (defined in a child node) is to be interpolated
+
+In \@root nodes, ``\&lt;\&lt;``*section*``\&gt;\&gt;`` in a headline *adds* the text of its body and descendants to to the named section; in a body, ``\&lt;\&lt;``*section*``\&gt;\&gt;``  spcifies the point at which Leo should interpolated a named section.  In a body, ``\&lt;\&lt;``*section*``\&gt;\&gt;=`` appends the following text to the definition of *section*.  Surprises abound; study the `\@root reference`_ .
+
+As with nearly all other directives, sections are ignored in \@asis trees.
+</t>
+<t tx="sps.20100507011942.13202">The @unit directive expands the scope of section definitions in @root trees
+so that a section may be referenced in several @root trees.
+The @unit directive is ignored outside of @root trees.</t>
+<t tx="sps.20100507011942.17787">Leo performs several checks to ensure that the result of importing an external
+file will be equivalent to the file that writing the ``@auto ``tree would produce.
+
+These checks can produces **errors** or **warnings**. Errors indicate a
+potentially serious problem. Leo inserts an ``@ignore`` directive in the ``@auto`` tree
+if any error is found. This ``@ignore`` directive prevents the ``@auto`` tree from
+modifying the external file. If you remove or displace the ``@ignore`` directive, a later write of the
+``@auto`` tree will attempt to fix the problems that gave rise to the errors. There
+are no guarantees however.
+
+Before importing a file, Leo **regularizes** the leading whitespace of all lines
+of the original source file. That is, Leo converts blanks to tabs or tabs to
+blanks depending on the value of the @tabwidth directive in effect for the ``@auto``
+node. Leo also checks that the indentation of any non-blank line is not a
+multiple of the indentation specified by the ``@tabwidth`` directive in effect for
+the ``@auto`` node.
+
+Leo cannot guarantee to reproduce the original source file exactly if problems
+are discovered while regularizing leading whitespace. **Strict languages** are
+languages such as Python for which leading whitespace must be preserved exactly
+as it appears in the original source file. Problems during regularizing whitespace generate
+errors for strict languages and warnings for non-strict languages.
+
+After importing a file, Leo verifies that writing the ``@auto`` node would create
+*exactly* the same file as the original file. Such file comparison mismatches
+generate errors unless the problem involves only leading whitespace for
+non-strict languages. Whenever a mismatch occurs the first non-matching line is
+printed.
+
+File comparison mismatches can arise for several reasons:
+
+1. Bugs in the import parsers. Please report any suspected bugs immediately.
+
+2. Underindented lines in classes, methods or function. An **underindented
+   line** is a line that is indented less then the starting line of the class,
+   method or function in which it appears. Leo outlines can not represent such
+   lines exactly: every line of node implicitly has at least the indentation of
+   any unindented line of the node.
+
+Leo will issue a warning (not an error) for underindented Python comment lines.
+Such lines can not change the meaning of Python programs.</t>
+<t tx="sps.20100507011942.17789">FIXME: This section is probably relevant to Read @&lt;file&gt; Nodes; the former named menu entries are no longer present.
+
+Three commands in the File:Read/Write menu allow you to manually read and
+write ``@auto`` nodes from the presently selected outline. As always, an ``@ignore``
+directive in the ``@auto`` node or its ancestors will suppress any of these
+commands:
+
+- The **Read @auto Nodes** (read-at-auto-nodes) command reads all @auto nodes in the
+  presently selected outline. An @ignore directive will suppress this import.
+
+- The **Write @auto Nodes** (write-at-auto-nodes) command writes all @auto nodes. An
+  ``@ignore`` directive will suppress this import. Caution: the write will occur even
+  if Leo has not previously read the @auto node.
+
+- The **Write Dirty @auto Nodes** (write-dirty-at-auto-nodes) is the same as the
+  write-at-auto-nodes command, except that only changed ``@auto`` trees are written.
+
+Most users will rarely use these explicit commands, because reading and writing
+.leo files handles ``@auto`` nodes well enough. However, you can use the
+read-at-auto-nodes command to update @auto nodes without having to reload the
+.leo file.
+</t>
+<t tx="sps.20100507011942.17790">The earliest variety of file generation was the \@root directive, designed to work with either `CWEB`_ or `noweb`_ markup.  The model for CWEB and noweb were for the person to edit a text ("web") file containing code and markup, and then "tangle" the file into a source code file appropriate for the compiler or interpreter, and to "weave" the text file into a beautifully typeset narrative which explained all the inner workings of the code.  Leo's innovation was to realize that a lot of what the markup was doing was to expose the often hidden conceptual structure of the code, and that this could be done better with an outline.  Thus in Leo, "tangling" creates the source files from the outline, "weaving" is dropped, and "untangling" turns source files into outlines.  That last trick nearly always requires some assistance from the source file, in the form of special comments called "sentinels" which help Leo discover the names of outline headlines and the boundaries in the chunks of text (bodies) corresponding to those headlines - and which chunks are subheads to other subheads.  As with CWEB and noweb, the specifications for how to assemble the nodes into the program source code are explicit: ``\&lt;\&lt;`` *section* ``\&gt;\&gt;`` specifies the location where Leo emits the section, and ``\&lt;\&lt;`` *section* ``\&gt;\&gt;=`` *code* adds snippets of code to the end of the section.</t>
+<t tx="sps.20100507011942.17791">\@root
+  This directive is the most flexible, the most difficult to use, and behaves
+  very differently from every other file generating directive. It comes closest
+  in spirit to traditional literate programming tools.
+  However, it is seldom necessary to suffer the drawbacks of using ``@root``.
+  Avoid using ``@root`` unless you have a compelling reason.  Forget everything
+  you've read about headline family file generation as you carefully study the `\@root reference`_.</t>
 <t tx="tbrown.20091203211538.14165">Makes \@path nodes "active".
 
 With this plugin running, double clicking on \@path nodes
 
=== added directory 'leo/doc/html/_build'
=== added directory 'leo/doc/html/_build/latex'
=== added file 'leo/doc/html/_build/latex/LeoDoc.pdf'
--- leo/doc/html/_build/latex/LeoDoc.pdf	1970-01-01 00:00:00 +0000
+++ leo/doc/html/_build/latex/LeoDoc.pdf	2010-05-11 20:36:27 +0000
@@ -0,0 +1,24321 @@
+%PDF-1.4
+%ÐÔÅØ
+5 0 obj
+<< /S /GoTo /D (chapter*.1) >>
+endobj
+8 0 obj
+(Acknowledgements)
+endobj
+9 0 obj
+<< /S /GoTo /D (chapter*.1) >>
+endobj
+11 0 obj
+(Leo's MIT License)
+endobj
+12 0 obj
+<< /S /GoTo /D (chapter*.2) >>
+endobj
+15 0 obj
+(Preface)
+endobj
+16 0 obj
+<< /S /GoTo /D (chapter*.3) >>
+endobj
+19 0 obj
+(What People Are Saying About Leo)
+endobj
+20 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+23 0 obj
+(Leo is revolutionary)
+endobj
+24 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+26 0 obj
+(Leo is a showcase Python/Tkinter application)
+endobj
+27 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+29 0 obj
+(Leo is fun, even addicting)
+endobj
+30 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+32 0 obj
+(Leo is a flexible, powerful IDE)
+endobj
+33 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+35 0 obj
+(Leo is a superb outliner)
+endobj
+36 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+38 0 obj
+(Leo is an excellent PIM)
+endobj
+39 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+41 0 obj
+(Leo extends, completes and simplifies literate programming)
+endobj
+42 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+44 0 obj
+(Leo is a superb documentation tool)
+endobj
+45 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+47 0 obj
+(Leo simplifies the understanding of complex systems)
+endobj
+48 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+50 0 obj
+(Leo is stable, well designed and well supported)
+endobj
+51 0 obj
+<< /S /GoTo /D (section*.4) >>
+endobj
+53 0 obj
+(Longer quotes...)
+endobj
+54 0 obj
+<< /S /GoTo /D (chapter*.5) >>
+endobj
+57 0 obj
+(FAQ)
+endobj
+58 0 obj
+<< /S /GoTo /D (section*.6) >>
+endobj
+61 0 obj
+(Getting Leo)
+endobj
+62 0 obj
+<< /S /GoTo /D (Item.10) >>
+endobj
+65 0 obj
+(Installing Leo)
+endobj
+66 0 obj
+<< /S /GoTo /D (Item.10) >>
+endobj
+68 0 obj
+(Learning to use Leo)
+endobj
+69 0 obj
+<< /S /GoTo /D (Item.10) >>
+endobj
+71 0 obj
+(How Should I Use Leo With bzr/git/hg/svn/cvs?)
+endobj
+72 0 obj
+<< /S /GoTo /D (Item.10) >>
+endobj
+74 0 obj
+(How Can I Use Leo Cooperatively Without Sentinels?)
+endobj
+75 0 obj
+<< /S /GoTo /D (Item.10) >>
+endobj
+77 0 obj
+(Using External Files)
+endobj
+78 0 obj
+<< /S /GoTo /D (Item.10) >>
+endobj
+80 0 obj
+(Customizing Leo)
+endobj
+81 0 obj
+<< /S /GoTo /D (Item.15) >>
+endobj
+84 0 obj
+(Tips and Techniques)
+endobj
+85 0 obj
+<< /S /GoTo /D (Item.40) >>
+endobj
+88 0 obj
+(Trouble Shooting)
+endobj
+89 0 obj
+<< /S /GoTo /D (Item.45) >>
+endobj
+92 0 obj
+(Unicode Issues)
+endobj
+93 0 obj
+<< /S /GoTo /D (chapter.1) >>
+endobj
+96 0 obj
+(Installing Leo)
+endobj
+97 0 obj
+<< /S /GoTo /D (section.1.1) >>
+endobj
+100 0 obj
+(System requirements)
+endobj
+101 0 obj
+<< /S /GoTo /D (section.1.2) >>
+endobj
+104 0 obj
+(Leo's HOME directory)
+endobj
+105 0 obj
+<< /S /GoTo /D (section.1.3) >>
+endobj
+108 0 obj
+(How to install Leo on Linux)
+endobj
+109 0 obj
+<< /S /GoTo /D (section.1.4) >>
+endobj
+112 0 obj
+(Installing Leo on MacOS X)
+endobj
+113 0 obj
+<< /S /GoTo /D (section.1.5) >>
+endobj
+116 0 obj
+(Installing Leo on Windows)
+endobj
+117 0 obj
+<< /S /GoTo /D (section.1.6) >>
+endobj
+120 0 obj
+(Tracking the development version)
+endobj
+121 0 obj
+<< /S /GoTo /D (section.1.7) >>
+endobj
+124 0 obj
+(Running Leo)
+endobj
+125 0 obj
+<< /S /GoTo /D (section.1.8) >>
+endobj
+128 0 obj
+(Running Leo from a console window)
+endobj
+129 0 obj
+<< /S /GoTo /D (section.1.9) >>
+endobj
+132 0 obj
+(Running Leo in batch mode)
+endobj
+133 0 obj
+<< /S /GoTo /D (section.1.10) >>
+endobj
+136 0 obj
+(How to install the Aspell spell checker)
+endobj
+137 0 obj
+<< /S /GoTo /D (chapter.2) >>
+endobj
+140 0 obj
+(The Leo Tutorial)
+endobj
+141 0 obj
+<< /S /GoTo /D (section.2.1) >>
+endobj
+144 0 obj
+(Leo's main window)
+endobj
+145 0 obj
+<< /S /GoTo /D (section.2.2) >>
+endobj
+148 0 obj
+(Outline commands)
+endobj
+149 0 obj
+<< /S /GoTo /D (section.2.3) >>
+endobj
+152 0 obj
+(External files and @thin nodes)
+endobj
+153 0 obj
+<< /S /GoTo /D (section.2.4) >>
+endobj
+156 0 obj
+(Creating external files from outlines)
+endobj
+157 0 obj
+<< /S /GoTo /D (section.2.5) >>
+endobj
+160 0 obj
+(Clones \046 views)
+endobj
+161 0 obj
+<< /S /GoTo /D (section.2.6) >>
+endobj
+164 0 obj
+(More about directives)
+endobj
+165 0 obj
+<< /S /GoTo /D (section.2.7) >>
+endobj
+168 0 obj
+(Scripting, extending and customizing Leo)
+endobj
+169 0 obj
+<< /S /GoTo /D (section.2.8) >>
+endobj
+172 0 obj
+(Summary)
+endobj
+173 0 obj
+<< /S /GoTo /D (section.2.9) >>
+endobj
+176 0 obj
+(Further study)
+endobj
+177 0 obj
+<< /S /GoTo /D (chapter.3) >>
+endobj
+180 0 obj
+(Using Outlines)
+endobj
+181 0 obj
+<< /S /GoTo /D (section.3.1) >>
+endobj
+184 0 obj
+(Outline Related)
+endobj
+185 0 obj
+<< /S /GoTo /D (section.3.2) >>
+endobj
+188 0 obj
+(Body Related)
+endobj
+189 0 obj
+<< /S /GoTo /D (section.3.3) >>
+endobj
+192 0 obj
+(Miscellaneous)
+endobj
+193 0 obj
+<< /S /GoTo /D (chapter.4) >>
+endobj
+196 0 obj
+(Writing Programs in Leo)
+endobj
+197 0 obj
+<< /S /GoTo /D (section.4.1) >>
+endobj
+200 0 obj
+(A Brief and Inaccurate History of Leo for Programming)
+endobj
+201 0 obj
+<< /S /GoTo /D (section.4.2) >>
+endobj
+204 0 obj
+(Creating and using external files: recommendations)
+endobj
+205 0 obj
+<< /S /GoTo /D (section.4.3) >>
+endobj
+208 0 obj
+(Overview: summary of directives)
+endobj
+209 0 obj
+<< /S /GoTo /D (section.4.4) >>
+endobj
+212 0 obj
+(Reference: all about directives)
+endobj
+213 0 obj
+<< /S /GoTo /D (section.4.5) >>
+endobj
+216 0 obj
+(CWEB mode)
+endobj
+217 0 obj
+<< /S /GoTo /D (chapter.5) >>
+endobj
+220 0 obj
+(Using Leo's Commands)
+endobj
+221 0 obj
+<< /S /GoTo /D (section.5.1) >>
+endobj
+224 0 obj
+(Autocompletion)
+endobj
+225 0 obj
+<< /S /GoTo /D (section.5.2) >>
+endobj
+228 0 obj
+(Calltips)
+endobj
+229 0 obj
+<< /S /GoTo /D (section.5.3) >>
+endobj
+232 0 obj
+(The minibuffer)
+endobj
+233 0 obj
+<< /S /GoTo /D (section.5.4) >>
+endobj
+236 0 obj
+(The File Menu)
+endobj
+237 0 obj
+<< /S /GoTo /D (section.5.5) >>
+endobj
+240 0 obj
+(The Edit Menu)
+endobj
+241 0 obj
+<< /S /GoTo /D (section.5.6) >>
+endobj
+244 0 obj
+(The Outline Menu)
+endobj
+245 0 obj
+<< /S /GoTo /D (section.5.7) >>
+endobj
+248 0 obj
+(The Window Menu)
+endobj
+249 0 obj
+<< /S /GoTo /D (section.5.8) >>
+endobj
+252 0 obj
+(The Help Menu)
+endobj
+253 0 obj
+<< /S /GoTo /D (chapter.6) >>
+endobj
+256 0 obj
+(Leo and Literate Programming)
+endobj
+257 0 obj
+<< /S /GoTo /D (section.6.1) >>
+endobj
+260 0 obj
+(Why I like Literate Programming)
+endobj
+261 0 obj
+<< /S /GoTo /D (section.6.2) >>
+endobj
+264 0 obj
+(How Leo Improves Literate Programming)
+endobj
+265 0 obj
+<< /S /GoTo /D (section.6.3) >>
+endobj
+268 0 obj
+(How Leo Changes the Notion of Literate Programming)
+endobj
+269 0 obj
+<< /S /GoTo /D (chapter.7) >>
+endobj
+272 0 obj
+(Scripting Leo with Python)
+endobj
+273 0 obj
+<< /S /GoTo /D (section.7.1) >>
+endobj
+276 0 obj
+(Leo's most import objects)
+endobj
+277 0 obj
+<< /S /GoTo /D (section.7.2) >>
+endobj
+280 0 obj
+(Predefined objects)
+endobj
+281 0 obj
+<< /S /GoTo /D (section.7.3) >>
+endobj
+284 0 obj
+(g.es writes to the log pane)
+endobj
+285 0 obj
+<< /S /GoTo /D (section.7.4) >>
+endobj
+288 0 obj
+(app.windowList: the list of all open frames)
+endobj
+289 0 obj
+<< /S /GoTo /D (section.7.5) >>
+endobj
+292 0 obj
+(Getting and setting headline and body text)
+endobj
+293 0 obj
+<< /S /GoTo /D (section.7.6) >>
+endobj
+296 0 obj
+(Getting and setting body text directly)
+endobj
+297 0 obj
+<< /S /GoTo /D (section.7.7) >>
+endobj
+300 0 obj
+(Ensuring that positions are valid)
+endobj
+301 0 obj
+<< /S /GoTo /D (section.7.8) >>
+endobj
+304 0 obj
+(About copying positions)
+endobj
+305 0 obj
+<< /S /GoTo /D (section.7.9) >>
+endobj
+308 0 obj
+(Traversing outlines)
+endobj
+309 0 obj
+<< /S /GoTo /D (section.7.10) >>
+endobj
+312 0 obj
+(Updating the screen)
+endobj
+313 0 obj
+<< /S /GoTo /D (section.7.11) >>
+endobj
+316 0 obj
+(Invoking commands from scripts)
+endobj
+317 0 obj
+<< /S /GoTo /D (section.7.12) >>
+endobj
+320 0 obj
+(Getting settings from @settings trees)
+endobj
+321 0 obj
+<< /S /GoTo /D (section.7.13) >>
+endobj
+324 0 obj
+(Getting and setting preferences)
+endobj
+325 0 obj
+<< /S /GoTo /D (section.7.14) >>
+endobj
+328 0 obj
+(Functions for finding and changing text from scripts)
+endobj
+329 0 obj
+<< /S /GoTo /D (section.7.15) >>
+endobj
+332 0 obj
+(Functions defined in leoGlobals.py)
+endobj
+333 0 obj
+<< /S /GoTo /D (section.7.16) >>
+endobj
+336 0 obj
+(Event handlers)
+endobj
+337 0 obj
+<< /S /GoTo /D (section.7.17) >>
+endobj
+340 0 obj
+(How to make operations undoable)
+endobj
+341 0 obj
+<< /S /GoTo /D (section.7.18) >>
+endobj
+344 0 obj
+(Redirecting output from scripts)
+endobj
+345 0 obj
+<< /S /GoTo /D (section.7.19) >>
+endobj
+348 0 obj
+(Writing to different log tabs)
+endobj
+349 0 obj
+<< /S /GoTo /D (section.7.20) >>
+endobj
+352 0 obj
+(Invoking dialogs using the g.app.gui class)
+endobj
+353 0 obj
+<< /S /GoTo /D (section.7.21) >>
+endobj
+356 0 obj
+(Inserting and deleting icons)
+endobj
+357 0 obj
+<< /S /GoTo /D (section.7.22) >>
+endobj
+360 0 obj
+(Customizing panes with different widgets)
+endobj
+361 0 obj
+<< /S /GoTo /D (section.7.23) >>
+endobj
+364 0 obj
+(Working with directives and paths)
+endobj
+365 0 obj
+<< /S /GoTo /D (section.7.24) >>
+endobj
+368 0 obj
+(Summary of the vnode and position classes)
+endobj
+369 0 obj
+<< /S /GoTo /D (section.7.25) >>
+endobj
+372 0 obj
+(Creating script buttons)
+endobj
+373 0 obj
+<< /S /GoTo /D (section.7.26) >>
+endobj
+376 0 obj
+(Running Leo in batch mode)
+endobj
+377 0 obj
+<< /S /GoTo /D (section.7.27) >>
+endobj
+380 0 obj
+(Getting interactive input from scripts)
+endobj
+381 0 obj
+<< /S /GoTo /D (section.7.28) >>
+endobj
+384 0 obj
+(Creating Leo commands with the @g.command decorator)
+endobj
+385 0 obj
+<< /S /GoTo /D (section.7.29) >>
+endobj
+388 0 obj
+(Modifying plugins with @script scripts)
+endobj
+389 0 obj
+<< /S /GoTo /D (chapter.8) >>
+endobj
+392 0 obj
+(Customizing Leo)
+endobj
+393 0 obj
+<< /S /GoTo /D (section.8.1) >>
+endobj
+396 0 obj
+(Specifying settings)
+endobj
+397 0 obj
+<< /S /GoTo /D (section.8.2) >>
+endobj
+400 0 obj
+(Input modes)
+endobj
+401 0 obj
+<< /S /GoTo /D (section.8.3) >>
+endobj
+404 0 obj
+(Adding extensible attributes to nodes and .leo files)
+endobj
+405 0 obj
+<< /S /GoTo /D (section.8.4) >>
+endobj
+408 0 obj
+(Specifying Tk options using .leo\137xresources)
+endobj
+409 0 obj
+<< /S /GoTo /D (section.8.5) >>
+endobj
+412 0 obj
+(Translating Leo's menus and messages)
+endobj
+413 0 obj
+<< /S /GoTo /D (section.8.6) >>
+endobj
+416 0 obj
+(Writing new importers)
+endobj
+417 0 obj
+<< /S /GoTo /D (chapter.9) >>
+endobj
+420 0 obj
+(History of Leo)
+endobj
+421 0 obj
+<< /S /GoTo /D (section.9.1) >>
+endobj
+424 0 obj
+(Beginnings)
+endobj
+425 0 obj
+<< /S /GoTo /D (section.9.2) >>
+endobj
+428 0 obj
+(Breakthrough)
+endobj
+429 0 obj
+<< /S /GoTo /D (section.9.3) >>
+endobj
+432 0 obj
+(Apple and YellowBox)
+endobj
+433 0 obj
+<< /S /GoTo /D (section.9.4) >>
+endobj
+436 0 obj
+(Borland C++)
+endobj
+437 0 obj
+<< /S /GoTo /D (section.9.5) >>
+endobj
+440 0 obj
+(Discovering Python)
+endobj
+441 0 obj
+<< /S /GoTo /D (section.9.6) >>
+endobj
+444 0 obj
+(SourceForge)
+endobj
+445 0 obj
+<< /S /GoTo /D (section.9.7) >>
+endobj
+448 0 obj
+(Allowing sentinel lines in external files)
+endobj
+449 0 obj
+<< /S /GoTo /D (section.9.8) >>
+endobj
+452 0 obj
+(Untangling @file is easy!)
+endobj
+453 0 obj
+<< /S /GoTo /D (section.9.9) >>
+endobj
+456 0 obj
+(Leo 3.x: Continuous improvement)
+endobj
+457 0 obj
+<< /S /GoTo /D (section.9.10) >>
+endobj
+460 0 obj
+(Leo 4.0: Eliminating error `recovery')
+endobj
+461 0 obj
+<< /S /GoTo /D (section.9.11) >>
+endobj
+464 0 obj
+(Leo 4.1: The debut of gnx's)
+endobj
+465 0 obj
+<< /S /GoTo /D (section.9.12) >>
+endobj
+468 0 obj
+(Leo 4.2: Complete at last)
+endobj
+469 0 obj
+<< /S /GoTo /D (section.9.13) >>
+endobj
+472 0 obj
+(Leo 4.3 Settings)
+endobj
+473 0 obj
+<< /S /GoTo /D (section.9.14) >>
+endobj
+476 0 obj
+(Leo 4.4 The minibuffer and key bindings)
+endobj
+477 0 obj
+<< /S /GoTo /D (section.9.15) >>
+endobj
+480 0 obj
+(Leo 4.4.4 Improvements)
+endobj
+481 0 obj
+<< /S /GoTo /D (chapter.10) >>
+endobj
+484 0 obj
+(Theory of Operation)
+endobj
+485 0 obj
+<< /S /GoTo /D (section.10.1) >>
+endobj
+488 0 obj
+(Overview)
+endobj
+489 0 obj
+<< /S /GoTo /D (section.10.2) >>
+endobj
+492 0 obj
+(Nodes)
+endobj
+493 0 obj
+<< /S /GoTo /D (section.10.3) >>
+endobj
+496 0 obj
+(Drawing and events)
+endobj
+497 0 obj
+<< /S /GoTo /D (section.10.4) >>
+endobj
+500 0 obj
+(Clones)
+endobj
+501 0 obj
+<< /S /GoTo /D (section.10.5) >>
+endobj
+504 0 obj
+(Find and change commands)
+endobj
+505 0 obj
+<< /S /GoTo /D (section.10.6) >>
+endobj
+508 0 obj
+(Tangle and untangle commands)
+endobj
+509 0 obj
+<< /S /GoTo /D (section.10.7) >>
+endobj
+512 0 obj
+(Unicode)
+endobj
+513 0 obj
+<< /S /GoTo /D (section.10.8) >>
+endobj
+516 0 obj
+(Unlimited undo)
+endobj
+517 0 obj
+<< /S /GoTo /D (section.10.9) >>
+endobj
+520 0 obj
+(Key bindings)
+endobj
+521 0 obj
+<< /S /GoTo /D (chapter.11) >>
+endobj
+524 0 obj
+(White Papers)
+endobj
+525 0 obj
+<< /S /GoTo /D (section.11.1) >>
+endobj
+528 0 obj
+(Why I like Python)
+endobj
+529 0 obj
+<< /S /GoTo /D (chapter.12) >>
+endobj
+532 0 obj
+(Plugins)
+endobj
+533 0 obj
+<< /S /GoTo /D (section.12.1) >>
+endobj
+536 0 obj
+(Enabling plugins)
+endobj
+537 0 obj
+<< /S /GoTo /D (section.12.2) >>
+endobj
+540 0 obj
+(Body pane)
+endobj
+541 0 obj
+<< /S /GoTo /D (section.12.3) >>
+endobj
+544 0 obj
+(Commands \046 directives)
+endobj
+545 0 obj
+<< /S /GoTo /D (section.12.4) >>
+endobj
+548 0 obj
+(Dialogs)
+endobj
+549 0 obj
+<< /S /GoTo /D (section.12.5) >>
+endobj
+552 0 obj
+(Debugging \046 testing)
+endobj
+553 0 obj
+<< /S /GoTo /D (section.12.6) >>
+endobj
+556 0 obj
+(External editors \046 Open With)
+endobj
+557 0 obj
+<< /S /GoTo /D (section.12.7) >>
+endobj
+560 0 obj
+(Files)
+endobj
+561 0 obj
+<< /S /GoTo /D (section.12.8) >>
+endobj
+564 0 obj
+(Guis)
+endobj
+565 0 obj
+<< /S /GoTo /D (section.12.9) >>
+endobj
+568 0 obj
+(Icon and status areas)
+endobj
+569 0 obj
+<< /S /GoTo /D (section.12.10) >>
+endobj
+572 0 obj
+(LeoN)
+endobj
+573 0 obj
+<< /S /GoTo /D (section.12.11) >>
+endobj
+576 0 obj
+(Menus \046 translations)
+endobj
+577 0 obj
+<< /S /GoTo /D (section.12.12) >>
+endobj
+580 0 obj
+(Nodes)
+endobj
+581 0 obj
+<< /S /GoTo /D (section.12.13) >>
+endobj
+584 0 obj
+(Plugins manager \046 menu)
+endobj
+585 0 obj
+<< /S /GoTo /D (section.12.14) >>
+endobj
+588 0 obj
+(Scripting)
+endobj
+589 0 obj
+<< /S /GoTo /D (section.12.15) >>
+endobj
+592 0 obj
+(Servers)
+endobj
+593 0 obj
+<< /S /GoTo /D (section.12.16) >>
+endobj
+596 0 obj
+(Spell checking)
+endobj
+597 0 obj
+<< /S /GoTo /D (section.12.17) >>
+endobj
+600 0 obj
+(Text formatting)
+endobj
+601 0 obj
+<< /S /GoTo /D (section.12.18) >>
+endobj
+604 0 obj
+(Windows)
+endobj
+605 0 obj
+<< /S /GoTo /D (chapter.13) >>
+endobj
+608 0 obj
+(Writing Plugins)
+endobj
+609 0 obj
+<< /S /GoTo /D (section.13.1) >>
+endobj
+612 0 obj
+(Overview)
+endobj
+613 0 obj
+<< /S /GoTo /D (section.13.2) >>
+endobj
+616 0 obj
+(Support for unit testing)
+endobj
+617 0 obj
+<< /S /GoTo /D (section.13.3) >>
+endobj
+620 0 obj
+(Turning script buttons into plugins)
+endobj
+621 0 obj
+<< /S /GoTo /D (section.13.4) >>
+endobj
+624 0 obj
+(Important security warnings)
+endobj
+625 0 obj
+<< /S /GoTo /D (chapter.14) >>
+endobj
+628 0 obj
+(Leo and ReStructuredText)
+endobj
+629 0 obj
+<< /S /GoTo /D (section.14.1) >>
+endobj
+632 0 obj
+(Overview)
+endobj
+633 0 obj
+<< /S /GoTo /D (section.14.2) >>
+endobj
+636 0 obj
+(Power features of @rst trees)
+endobj
+637 0 obj
+<< /S /GoTo /D (section.14.3) >>
+endobj
+640 0 obj
+(Options)
+endobj
+641 0 obj
+<< /S /GoTo /D (section.14.4) >>
+endobj
+644 0 obj
+(Headline Commands)
+endobj
+645 0 obj
+<< /S /GoTo /D (section.14.5) >>
+endobj
+648 0 obj
+(Using doc parts)
+endobj
+649 0 obj
+<< /S /GoTo /D (section.14.6) >>
+endobj
+652 0 obj
+(Setting defaults)
+endobj
+653 0 obj
+<< /S /GoTo /D (section.14.7) >>
+endobj
+656 0 obj
+(The code-block directive)
+endobj
+657 0 obj
+<< /S /GoTo /D (section.14.8) >>
+endobj
+660 0 obj
+(Required cascading style sheets)
+endobj
+661 0 obj
+<< /S /GoTo /D (section.14.9) >>
+endobj
+664 0 obj
+(Notes about rST markup)
+endobj
+665 0 obj
+<< /S /GoTo /D (section.14.10) >>
+endobj
+668 0 obj
+(Examples)
+endobj
+669 0 obj
+<< /S /GoTo /D (section.14.11) >>
+endobj
+672 0 obj
+(Theory of operation)
+endobj
+673 0 obj
+<< /S /GoTo /D (section.14.12) >>
+endobj
+676 0 obj
+(Controlling the rst3 command from scripts)
+endobj
+677 0 obj
+<< /S /GoTo /D (section.14.13) >>
+endobj
+680 0 obj
+(Acknowledgements)
+endobj
+681 0 obj
+<< /S /GoTo /D (chapter.15) >>
+endobj
+684 0 obj
+(Controlling Syntax Coloring)
+endobj
+685 0 obj
+<< /S /GoTo /D (section.15.1) >>
+endobj
+688 0 obj
+(Files)
+endobj
+689 0 obj
+<< /S /GoTo /D (section.15.2) >>
+endobj
+692 0 obj
+(The colorizer's inner loop)
+endobj
+693 0 obj
+<< /S /GoTo /D (section.15.3) >>
+endobj
+696 0 obj
+(Format of colorizer control files)
+endobj
+697 0 obj
+<< /S /GoTo /D (section.15.4) >>
+endobj
+700 0 obj
+(Rule methods)
+endobj
+701 0 obj
+<< /S /GoTo /D (section.15.5) >>
+endobj
+704 0 obj
+(Syntax coloring settings)
+endobj
+705 0 obj
+<< /S /GoTo /D (section.15.6) >>
+endobj
+708 0 obj
+(The threading\137colorizer plugin)
+endobj
+709 0 obj
+<< /S /GoTo /D (chapter.16) >>
+endobj
+712 0 obj
+(Debugging with Leo)
+endobj
+713 0 obj
+<< /S /GoTo /D (section.16.1) >>
+endobj
+716 0 obj
+(Using g.trace and g.pdb)
+endobj
+717 0 obj
+<< /S /GoTo /D (section.16.2) >>
+endobj
+720 0 obj
+(Settings for winpdb)
+endobj
+721 0 obj
+<< /S /GoTo /D (section.16.3) >>
+endobj
+724 0 obj
+(Debugging scripts with winpdb)
+endobj
+725 0 obj
+<< /S /GoTo /D (chapter.17) >>
+endobj
+728 0 obj
+(Using ZODB with Leo)
+endobj
+729 0 obj
+<< /S /GoTo /D (section.17.1) >>
+endobj
+732 0 obj
+(Configuring Leo to use zodb)
+endobj
+733 0 obj
+<< /S /GoTo /D (section.17.2) >>
+endobj
+736 0 obj
+(Initing zodb)
+endobj
+737 0 obj
+<< /S /GoTo /D (section.17.3) >>
+endobj
+740 0 obj
+(Writing data to zodb)
+endobj
+741 0 obj
+<< /S /GoTo /D (section.17.4) >>
+endobj
+744 0 obj
+(Defining zodb keys)
+endobj
+745 0 obj
+<< /S /GoTo /D (section.17.5) >>
+endobj
+748 0 obj
+(Reading data from zodb)
+endobj
+749 0 obj
+<< /S /GoTo /D (section.17.6) >>
+endobj
+752 0 obj
+(About connections)
+endobj
+753 0 obj
+<< /S /GoTo /D (section.17.7) >>
+endobj
+756 0 obj
+(Convenience routines)
+endobj
+757 0 obj
+<< /S /GoTo /D (chapter.18) >>
+endobj
+760 0 obj
+(Leo and Emacs)
+endobj
+761 0 obj
+<< /S /GoTo /D (section.18.1) >>
+endobj
+764 0 obj
+(Controlling Leo from Emacs using Pymacs)
+endobj
+765 0 obj
+<< /S /GoTo /D (section.18.2) >>
+endobj
+768 0 obj
+(Functions in leoPymacs.py)
+endobj
+769 0 obj
+<< /S /GoTo /D (section.18.3) >>
+endobj
+772 0 obj
+(The minibuffer)
+endobj
+773 0 obj
+<< /S /GoTo /D (chapter.19) >>
+endobj
+776 0 obj
+(Embedding Leo with the leoBridge module)
+endobj
+777 0 obj
+<< /S /GoTo /D (section.19.1) >>
+endobj
+780 0 obj
+(The basics)
+endobj
+781 0 obj
+<< /S /GoTo /D (section.19.2) >>
+endobj
+784 0 obj
+(Running leoBridge from within Leo)
+endobj
+785 0 obj
+<< /S /GoTo /D (chapter.20) >>
+endobj
+788 0 obj
+(Unit testing with Leo)
+endobj
+789 0 obj
+<< /S /GoTo /D (section.20.1) >>
+endobj
+792 0 obj
+(Overview)
+endobj
+793 0 obj
+<< /S /GoTo /D (section.20.2) >>
+endobj
+796 0 obj
+(Using @test nodes)
+endobj
+797 0 obj
+<< /S /GoTo /D (section.20.3) >>
+endobj
+800 0 obj
+(Using @suite nodes)
+endobj
+801 0 obj
+<< /S /GoTo /D (section.20.4) >>
+endobj
+804 0 obj
+(How the unit test commands work)
+endobj
+805 0 obj
+<< /S /GoTo /D (section.20.5) >>
+endobj
+808 0 obj
+(@button timer)
+endobj
+809 0 obj
+<< /S /GoTo /D (section.20.6) >>
+endobj
+812 0 obj
+(@button profile)
+endobj
+813 0 obj
+<< /S /GoTo /D (chapter.21) >>
+endobj
+816 0 obj
+(IPython and Leo)
+endobj
+817 0 obj
+<< /S /GoTo /D (section.21.1) >>
+endobj
+820 0 obj
+(Introduction)
+endobj
+821 0 obj
+<< /S /GoTo /D (section.21.2) >>
+endobj
+824 0 obj
+(Installation and startup)
+endobj
+825 0 obj
+<< /S /GoTo /D (section.21.3) >>
+endobj
+828 0 obj
+(Accessing IPython from Leo)
+endobj
+829 0 obj
+<< /S /GoTo /D (section.21.4) >>
+endobj
+832 0 obj
+(Accessing Leo nodes from IPython)
+endobj
+833 0 obj
+<< /S /GoTo /D (section.21.5) >>
+endobj
+836 0 obj
+(@cl definitions)
+endobj
+837 0 obj
+<< /S /GoTo /D (section.21.6) >>
+endobj
+840 0 obj
+(Special node types)
+endobj
+841 0 obj
+<< /S /GoTo /D (section.21.7) >>
+endobj
+844 0 obj
+(Launching ILeo from IPython)
+endobj
+845 0 obj
+<< /S /GoTo /D (section.21.8) >>
+endobj
+848 0 obj
+(Declaring custom push-to-ipython handlers)
+endobj
+849 0 obj
+<< /S /GoTo /D (section.21.9) >>
+endobj
+852 0 obj
+(Example code snippets)
+endobj
+853 0 obj
+<< /S /GoTo /D (section.21.10) >>
+endobj
+856 0 obj
+(Example use case: pylab)
+endobj
+857 0 obj
+<< /S /GoTo /D (section.21.11) >>
+endobj
+860 0 obj
+(Magic functions)
+endobj
+861 0 obj
+<< /S /GoTo /D (section.21.12) >>
+endobj
+864 0 obj
+(Acknowledgements and history)
+endobj
+865 0 obj
+<< /S /GoTo /D (chapter.22) >>
+endobj
+868 0 obj
+(Using Vim Bindings with Leo)
+endobj
+869 0 obj
+<< /S /GoTo /D (section.22.1) >>
+endobj
+872 0 obj
+(Vim bindings)
+endobj
+873 0 obj
+<< /S /GoTo /D (section.22.2) >>
+endobj
+876 0 obj
+(Avoiding changes to `tag' files)
+endobj
+877 0 obj
+<< /S /GoTo /D (chapter.23) >>
+endobj
+880 0 obj
+(Eliminating sentinel lines with @shadow)
+endobj
+881 0 obj
+<< /S /GoTo /D (section.23.1) >>
+endobj
+884 0 obj
+(Overview)
+endobj
+885 0 obj
+<< /S /GoTo /D (section.23.2) >>
+endobj
+888 0 obj
+(Creating @shadow trees)
+endobj
+889 0 obj
+<< /S /GoTo /D (section.23.3) >>
+endobj
+892 0 obj
+(What the update algorithm does)
+endobj
+893 0 obj
+<< /S /GoTo /D (section.23.4) >>
+endobj
+896 0 obj
+(Aha: boundary cases don't matter)
+endobj
+897 0 obj
+<< /S /GoTo /D (chapter.24) >>
+endobj
+900 0 obj
+(Appendices)
+endobj
+901 0 obj
+<< /S /GoTo /D (section.24.1) >>
+endobj
+904 0 obj
+(Bugs)
+endobj
+905 0 obj
+<< /S /GoTo /D (section.24.2) >>
+endobj
+908 0 obj
+(Errors while tangling)
+endobj
+909 0 obj
+<< /S /GoTo /D (section.24.3) >>
+endobj
+912 0 obj
+(Errors while untangling)
+endobj
+913 0 obj
+<< /S /GoTo /D (section.24.4) >>
+endobj
+916 0 obj
+(Errors while reading @file nodes)
+endobj
+917 0 obj
+<< /S /GoTo /D (section.24.5) >>
+endobj
+920 0 obj
+(Errors while writing @file nodes)
+endobj
+921 0 obj
+<< /S /GoTo /D (section.24.6) >>
+endobj
+924 0 obj
+(Format of .leo files)
+endobj
+925 0 obj
+<< /S /GoTo /D (section.24.7) >>
+endobj
+928 0 obj
+(Format of external files)
+endobj
+929 0 obj
+<< /S /GoTo /D (section.24.8) >>
+endobj
+932 0 obj
+(Unicode reference)
+endobj
+933 0 obj
+<< /S /GoTo /D (chapter.25) >>
+endobj
+936 0 obj
+(What's New in Leo 4.7)
+endobj
+937 0 obj
+<< /S /GoTo /D (section.25.1) >>
+endobj
+940 0 obj
+(Leo supports Python 3.x)
+endobj
+941 0 obj
+<< /S /GoTo /D (section.25.2) >>
+endobj
+944 0 obj
+(Improved file handling)
+endobj
+945 0 obj
+<< /S /GoTo /D (section.25.3) >>
+endobj
+948 0 obj
+(New command-line options)
+endobj
+949 0 obj
+<< /S /GoTo /D (section.25.4) >>
+endobj
+952 0 obj
+(New commands)
+endobj
+953 0 obj
+<< /S /GoTo /D (section.25.5) >>
+endobj
+956 0 obj
+(New settings)
+endobj
+957 0 obj
+<< /S /GoTo /D (section.25.6) >>
+endobj
+960 0 obj
+(Improved plugins)
+endobj
+961 0 obj
+<< /S /GoTo /D (chapter.26) >>
+endobj
+964 0 obj
+(What's New in Leo 4.6)
+endobj
+965 0 obj
+<< /S /GoTo /D (section.26.1) >>
+endobj
+968 0 obj
+(Improved unit testing)
+endobj
+969 0 obj
+<< /S /GoTo /D (section.26.2) >>
+endobj
+972 0 obj
+(Improved file handling)
+endobj
+973 0 obj
+<< /S /GoTo /D (section.26.3) >>
+endobj
+976 0 obj
+(Improved handling of rST files)
+endobj
+977 0 obj
+<< /S /GoTo /D (section.26.4) >>
+endobj
+980 0 obj
+(New code features)
+endobj
+981 0 obj
+<< /S /GoTo /D (section.26.5) >>
+endobj
+984 0 obj
+(New command-line options)
+endobj
+985 0 obj
+<< /S /GoTo /D (section.26.6) >>
+endobj
+988 0 obj
+(New commands)
+endobj
+989 0 obj
+<< /S /GoTo /D (section.26.7) >>
+endobj
+992 0 obj
+(New and improved directives)
+endobj
+993 0 obj
+<< /S /GoTo /D (section.26.8) >>
+endobj
+996 0 obj
+(New settings)
+endobj
+997 0 obj
+<< /S /GoTo /D (section.26.9) >>
+endobj
+1000 0 obj
+(Plugins)
+endobj
+1001 0 obj
+<< /S /GoTo /D (chapter.27) >>
+endobj
+1004 0 obj
+(What's New in Leo 4.5)
+endobj
+1005 0 obj
+<< /S /GoTo /D (section.27.1) >>
+endobj
+1008 0 obj
+(Major new features)
+endobj
+1009 0 obj
+<< /S /GoTo /D (section.27.2) >>
+endobj
+1012 0 obj
+(Major code reorganizations)
+endobj
+1013 0 obj
+<< /S /GoTo /D (section.27.3) >>
+endobj
+1016 0 obj
+(Minor new features)
+endobj
+1017 0 obj
+<< /S /GoTo /D (section.27.4) >>
+endobj
+1020 0 obj
+(New settings)
+endobj
+1021 0 obj
+<< /S /GoTo /D (chapter.28) >>
+endobj
+1024 0 obj
+(What's New in Leo 4.4.7 and Leo 4.4.8)
+endobj
+1025 0 obj
+<< /S /GoTo /D (section.28.1) >>
+endobj
+1028 0 obj
+(New features)
+endobj
+1029 0 obj
+<< /S /GoTo /D (section.28.2) >>
+endobj
+1032 0 obj
+(New and improved plugins)
+endobj
+1033 0 obj
+<< /S /GoTo /D (section.28.3) >>
+endobj
+1036 0 obj
+(New settings)
+endobj
+1037 0 obj
+<< /S /GoTo /D (chapter.29) >>
+endobj
+1040 0 obj
+(What's New in Leo 4.4.6)
+endobj
+1041 0 obj
+<< /S /GoTo /D (section.29.1) >>
+endobj
+1044 0 obj
+(New commands)
+endobj
+1045 0 obj
+<< /S /GoTo /D (section.29.2) >>
+endobj
+1048 0 obj
+(New features)
+endobj
+1049 0 obj
+<< /S /GoTo /D (section.29.3) >>
+endobj
+1052 0 obj
+(New settings)
+endobj
+1053 0 obj
+<< /S /GoTo /D (chapter.30) >>
+endobj
+1056 0 obj
+(What's New in Leo 4.4.5)
+endobj
+1057 0 obj
+<< /S /GoTo /D (section.30.1) >>
+endobj
+1060 0 obj
+(Bug fixed)
+endobj
+1061 0 obj
+<< /S /GoTo /D (section.30.2) >>
+endobj
+1064 0 obj
+(New features)
+endobj
+1065 0 obj
+<< /S /GoTo /D (section.30.3) >>
+endobj
+1068 0 obj
+(New commands)
+endobj
+1069 0 obj
+<< /S /GoTo /D (section.30.4) >>
+endobj
+1072 0 obj
+(New settings)
+endobj
+1073 0 obj
+<< /S /GoTo /D (chapter.31) >>
+endobj
+1076 0 obj
+(What's New in Leo 4.4.4)
+endobj
+1077 0 obj
+<< /S /GoTo /D (section.31.1) >>
+endobj
+1080 0 obj
+(The Great Graph Aha)
+endobj
+1081 0 obj
+<< /S /GoTo /D (section.31.2) >>
+endobj
+1084 0 obj
+(Added support for @auto files)
+endobj
+1085 0 obj
+<< /S /GoTo /D (section.31.3) >>
+endobj
+1088 0 obj
+(New commands for resolving cvs conflicts)
+endobj
+1089 0 obj
+<< /S /GoTo /D (section.31.4) >>
+endobj
+1092 0 obj
+(New kinds of settings trees)
+endobj
+1093 0 obj
+<< /S /GoTo /D (section.31.5) >>
+endobj
+1096 0 obj
+(New plugins)
+endobj
+1097 0 obj
+<< /S /GoTo /D (section.31.6) >>
+endobj
+1100 0 obj
+(Leo's core is now compatible with jython)
+endobj
+1101 0 obj
+<< /S /GoTo /D (section.31.7) >>
+endobj
+1104 0 obj
+(Improved prototype for icons in headlines)
+endobj
+1105 0 obj
+<< /S /GoTo /D (section.31.8) >>
+endobj
+1108 0 obj
+(Minor improvements)
+endobj
+1109 0 obj
+<< /S /GoTo /D (section.31.9) >>
+endobj
+1112 0 obj
+(Summary of new commands)
+endobj
+1113 0 obj
+<< /S /GoTo /D (chapter.32) >>
+endobj
+1116 0 obj
+(What's New in Leo 4.4.3)
+endobj
+1117 0 obj
+<< /S /GoTo /D (section.32.1) >>
+endobj
+1120 0 obj
+(Important new features)
+endobj
+1121 0 obj
+<< /S /GoTo /D (section.32.2) >>
+endobj
+1124 0 obj
+(New commands)
+endobj
+1125 0 obj
+<< /S /GoTo /D (section.32.3) >>
+endobj
+1128 0 obj
+(New settings)
+endobj
+1129 0 obj
+<< /S /GoTo /D (section.32.4) >>
+endobj
+1132 0 obj
+(Plugins)
+endobj
+1133 0 obj
+<< /S /GoTo /D (section.32.5) >>
+endobj
+1136 0 obj
+(Minor improvements)
+endobj
+1137 0 obj
+<< /S /GoTo /D (chapter.33) >>
+endobj
+1140 0 obj
+(What's New in Leo 4.4.2)
+endobj
+1141 0 obj
+<< /S /GoTo /D (section.33.1) >>
+endobj
+1144 0 obj
+(A major code reorg)
+endobj
+1145 0 obj
+<< /S /GoTo /D (section.33.2) >>
+endobj
+1148 0 obj
+(New commands)
+endobj
+1149 0 obj
+<< /S /GoTo /D (section.33.3) >>
+endobj
+1152 0 obj
+(New features)
+endobj
+1153 0 obj
+<< /S /GoTo /D (section.33.4) >>
+endobj
+1156 0 obj
+(New and improved plugins)
+endobj
+1157 0 obj
+<< /S /GoTo /D (section.33.5) >>
+endobj
+1160 0 obj
+(Settings)
+endobj
+1161 0 obj
+<< /S /GoTo /D (section.33.6) >>
+endobj
+1164 0 obj
+(ZODB scripting)
+endobj
+1165 0 obj
+<< /S /GoTo /D (chapter.34) >>
+endobj
+1168 0 obj
+(What's New in Leo 4.4.1)
+endobj
+1169 0 obj
+<< /S /GoTo /D (section.34.1) >>
+endobj
+1172 0 obj
+(New commands)
+endobj
+1173 0 obj
+<< /S /GoTo /D (section.34.2) >>
+endobj
+1176 0 obj
+(New features)
+endobj
+1177 0 obj
+<< /S /GoTo /D (section.34.3) >>
+endobj
+1180 0 obj
+(New and improved plugins)
+endobj
+1181 0 obj
+<< /S /GoTo /D (section.34.4) >>
+endobj
+1184 0 obj
+(New settings)
+endobj
+1185 0 obj
+<< /S /GoTo /D (section.34.5) >>
+endobj
+1188 0 obj
+(Improved settings)
+endobj
+1189 0 obj
+<< /S /GoTo /D (section.34.6) >>
+endobj
+1192 0 obj
+(Minor improvements)
+endobj
+1193 0 obj
+<< /S /GoTo /D (chapter.35) >>
+endobj
+1196 0 obj
+(What's New in Leo 4.4)
+endobj
+1197 0 obj
+<< /S /GoTo /D (section.35.1) >>
+endobj
+1200 0 obj
+(New commands)
+endobj
+1201 0 obj
+<< /S /GoTo /D (section.35.2) >>
+endobj
+1204 0 obj
+(New features)
+endobj
+1205 0 obj
+<< /S /GoTo /D (section.35.3) >>
+endobj
+1208 0 obj
+(Added new convenience methods for scripts and plugins)
+endobj
+1209 0 obj
+<< /S /GoTo /D (section.35.4) >>
+endobj
+1212 0 obj
+(New and improved plugins)
+endobj
+1213 0 obj
+<< /S /GoTo /D (section.35.5) >>
+endobj
+1216 0 obj
+(New and improved settings)
+endobj
+1217 0 obj
+<< /S /GoTo /D (chapter.36) >>
+endobj
+1220 0 obj
+(Indices and tables)
+endobj
+1221 0 obj
+<< /S /GoTo /D [1222 0 R  /Fit ] >>
+endobj
+1224 0 obj <<
+/Length 267       
+/Filter /FlateDecode
+>>
+stream
+xÚ½�=OÄ0
 †÷ü
+�­DŒ�ï¬HÒ
G·»*Zn q
 'þ=.©(;CbçÕë'ÖKp‚+Ese¹	¢�2¦
 £¢Y|R„ÒÍçx€ïÏÍù×ë×â:£
 ~Ú{»'èDY‹=ç§OÏÎ3š¤à^Ý-ý
+AK
+z‰á¢Qç—&�qSdh
 ÁÅŒ†œÄå�‚�¦ƒmuÓ¿Ôûf-Þ
 
 Ñ°w“WgÂä
 hŠwÓ}ûÖ×"¦J¸zGdžÛa¤B+ŠæÈh­/€UW³¯Ní±6Tu…s�¥núv, ËÀŒÙ{3�BB—d)`"[@·í»Lyª˜ÏJcˆiÿ“ϪQWZu…
+endstream
+endobj
+1222 0 obj <<
+/Type /Page
+/Contents 1224 0 R
+/Resources 1223 0 R
+/MediaBox [0 0 595.276 841.89]
+/Parent 1230 0 R
+>> endobj
+1225 0 obj <<
+/D [1222 0 R /XYZ 72 794.796 null]
+>> endobj
+1226 0 obj <<
+/D [1222 0 R /XYZ 72 769.89 null]
+>> endobj
+1223 0 obj <<
+/Font << /F28 1227 0 R /F29 1228 0 R /F31 1229 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1233 0 obj <<
+/Length 19        
+/Filter /FlateDecode
+>>
+stream
+xÚ3PHW0Ppç2ÀAc(á
+endstream
+endobj
+1232 0 obj <<
+/Type /Page
+/Contents 1233 0 R
+/Resources 1231 0 R
+/MediaBox [0 0 595.276 841.89]
+/Parent 1230 0 R
+>> endobj
+1234 0 obj <<
+/D [1232 0 R /XYZ 72 794.796 null]
+>> endobj
+1231 0 obj <<
+/ProcSet [ /PDF ]
+>> endobj
+1278 0 obj <<
+/Length 1468      
+/Filter /FlateDecode
+>>
+stream
+xÚí›]SÛ8†ïó+|·öÌÆH²eËW;,K[:¥Ð¦;Óí…±E¢Á‘‚?J鯯Œd‡Ø�¥‹ÜnÁ7XQŒäñ£stΫ`Í-`½œ}ýs6Ùy�ˆ…|7$!´fç–G7ò‰à"X³Ôúhï
 ½�í¿��8Ÿf¯'²
 ¸^èË¿>	¬\ŽÖë|ÿRŽíA+r£ 
 çÜšz¸øÖ4‚n€õØ»ÉÂöUFÓ9]R^j
 ý�ÖÇ)&Èv�)à]ü(zü(�	±Ol¸Ñûpœòö)„n„±"÷†Šß
 Œí™"
 ìÙj¼a	åíÎM<<Büé¥M’Û6	}iîÒ$‘
 ‰{œ;�Øô<N:}?pQ$GS÷yßé¬i3ÀÆtq©VჀMÅ*£êó®zõá$¾f|®¿8•þ¹
+»/E˜`?Î[5/¦³âÕ¤L¯ùœÖžësýØ"«J&xœ_wǾÁ…�Íy¯M–±º
 µ%q¡Þñu¹|gvÁxIs}ój•±$®‰wŸ2
 Ã'‰fÁ
 0Î+þ»ji
 ƒØ¦\¿û4eIYû‚Î#y!
 Më¿`
 ¶©ðh�ð
 ;˨»RvFóó*S=í÷"¿ˆŒô~2½¢ZÑüLµå¶›1.½`—GÓû_2ä�­Í/¡Y&,½¯
 
 öB•Ž1Ê#0†¦1*l%åi¡Ýf"–2>.iË7ÕVÊd?“ž5_eL†+q©£˜U.æy¼\nÙ7e¼ü+Pø!/ü
 ß—Š¤ªå	õÝt•Bd=‚d´
 󠺑b½—
 ½Ô+žÒ¼(¥i´	£8¿m=7F¥‡¹.Jºì)N¡G~YÛ^?ÊNäk^‡tWr{ѶB
 6ç4í8©õ
 Ò°V"/å
 ]™�§eƒâ|Þ¤¤—•�»‚ëöfÄ>?ýÁdÀ6ȇÈp/œØ»Ž�íw]º
 ôz�Ôå}¸^m.­—´,[÷¹Ed
 "ülWÕ�Ë
 @-õz†¼Å
—Þ:Ë#Î�qúÆöâ8ç-ÌRoÌU#[n¡ë‡þÒ
 HSRô+¥„écŽ…¨2
 .
 ¨Ëém¤7�Ž/C°r¡>�}Íwæ¬ÜYÌwŠÏ|'ù\üÑ#O¼§
 UÝ	
 %@ö	åN{B¬êL›­¥êìzT{\u"HÆiÖGä
ôËB††6�Ó¢urû_JšóXç/XF{™
+ÉèãÌù8SË^U”bɾÞ|ÏÃ
 ã#CgŽ‡m¶êêŽ3'6Mœ]VÛ¬ÑYc‰ I–¹¨ÎšJ
 uˆmGª!G“4ŽÑ7§œr–ˆT#<(Š-A2frCq
 Dý	µªãÈIäÔÿš´wÔ UƒôJƒný<^í)nó¦üé²bùöšMŸøãªú®åä™òîÐEV§DóÕÑá¾Öç%¶¤ýb5ïÉIƒ™¿A^žæµ‘x6ŠS
  “t6G�o¯¾ô$ÿÀ
 lH`¾¶Í;oà9Œ“£Õü»\E£ÜB	£„JIÉ4<Uæ×Ïb
 ž"==^ž1^�æ¥Ò“8¹X«ÛÍÙ~z«
 4«e[ͤºòbKEn}P÷lH
 Ĭ
 C�è}Åù½IxL1
 Ú˜oÌÆÈ]UÝu.–P‰à…hT‚«ÖEö¶²àùù=sL¢{™0½I�Åe¢O|–uÖß+Yc¾-”°1J8Sò  ½Ý­v‹ÕºâiÝL4¹p °û…Ô‘>Ÿm	X=ƒ´~2[t�ëfN„ìJ&¿,Îî—RÂ!
+kP+¥t²óeÜXúÝ~6"pÜA¿o‘™ªµC­ªr¤~ÑV”.cžö³üÄ+i†Ö9°Ò×ýÙäreXÐ
+‘…}¡•,'?
+•Ý¯k‚±®nnZZ>†.
+Ùά“É»ö×îkŸ–/m"…™mÌ.gý€pŠ
+endstream
+endobj
+1277 0 obj <<
+/Type /Page
+/Contents 1278 0 R
+/Resources 1276 0 R
+/MediaBox [0 0 595.276 841.89]
+/Parent 1230 0 R
+/Annots [ 1235 0 R 1236 0 R 1237 0 R 1238 0 R 1239 0 R 1240 0 R 1241 0 R 1242 0 R 1243 0 R 1244 0 R 1245 0 R 1246 0 R 1247 0 R 1248 0 R 1249 0 R 1250 0 R 1251 0 R 1252 0 R 1253 0 R 1254 0 R 1255 0 R 1256 0 R 1257 0 R 1258 0 R 1259 0 R 1260 0 R 1261 0 R 1262 0 R 1263 0 R 1264 0 R 1265 0 R 1266 0 R 1267 0 R 1268 0 R 1269 0 R 1270 0 R 1271 0 R 1272 0 R 1273 0 R 1274 0 R ]
+>> endobj
+1235 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 585.417 166.824 596.321]
+/Subtype /Link
+/A << /S /GoTo /D (chapter*.1) >>
+>> endobj
+1236 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 575.519 164.303 584.365]
+/Subtype /Link
+/A << /S /GoTo /D (chapter*.1) >>
+>> endobj
+1237 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 553.581 104.896 562.557]
+/Subtype /Link
+/A << /S /GoTo /D (chapter*.2) >>
+>> endobj
+1238 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 529.76 224.547 540.639]
+/Subtype /Link
+/A << /S /GoTo /D (chapter*.3) >>
+>> endobj
+1239 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 517.671 168.288 528.575]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1240 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 505.716 269.487 516.619]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1241 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 493.76 191.302 504.664]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1242 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 481.805 211.496 492.709]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1243 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 469.85 182.016 480.754]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1244 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 459.952 182.973 468.799]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1245 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 445.94 326.592 456.844]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1246 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 433.984 228.233 444.888]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1247 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 422.029 299.764 432.933]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1248 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 410.074 276.651 420.978]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1249 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 398.119 152.687 409.023]
+/Subtype /Link
+/A << /S /GoTo /D (section*.4) >>
+>> endobj
+1250 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 376.625 92.682 387.215]
+/Subtype /Link
+/A << /S /GoTo /D (chapter*.5) >>
+>> endobj
+1251 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 364.246 135.81 375.15]
+/Subtype /Link
+/A << /S /GoTo /D (section*.6) >>
+>> endobj
+1252 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 352.291 143.561 363.195]
+/Subtype /Link
+/A << /S /GoTo /D (Item.10) >>
+>> endobj
+1253 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 340.336 167.9 351.24]
+/Subtype /Link
+/A << /S /GoTo /D (Item.10) >>
+>> endobj
+1254 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 328.381 279.889 339.284]
+/Subtype /Link
+/A << /S /GoTo /D (Item.10) >>
+>> endobj
+1255 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 316.425 304.108 327.329]
+/Subtype /Link
+/A << /S /GoTo /D (Item.10) >>
+>> endobj
+1256 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 304.47 169.852 315.374]
+/Subtype /Link
+/A << /S /GoTo /D (Item.10) >>
+>> endobj
+1257 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 292.515 156.851 303.419]
+/Subtype /Link
+/A << /S /GoTo /D (Item.10) >>
+>> endobj
+1258 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 280.56 169.902 291.464]
+/Subtype /Link
+/A << /S /GoTo /D (Item.15) >>
+>> endobj
+1259 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 268.605 157.608 279.509]
+/Subtype /Link
+/A << /S /GoTo /D (Item.40) >>
+>> endobj
+1260 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 258.707 148.532 267.553]
+/Subtype /Link
+/A << /S /GoTo /D (Item.45) >>
+>> endobj
+1261 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 234.866 146.898 245.745]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.1) >>
+>> endobj
+1262 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 222.777 197.688 233.68]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.1) >>
+>> endobj
+1263 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 210.821 206.256 221.725]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.2) >>
+>> endobj
+1264 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 200.923 226.779 209.77]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.3) >>
+>> endobj
+1265 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 186.911 224.527 197.815]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.4) >>
+>> endobj
+1266 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 174.956 221.947 185.86]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.5) >>
+>> endobj
+1267 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 163.001 249.354 173.905]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.6) >>
+>> endobj
+1268 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 151.046 166.147 161.949]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.7) >>
+>> endobj
+1269 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 139.09 262.186 149.994]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.8) >>
+>> endobj
+1270 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 127.135 225.085 138.039]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.9) >>
+>> endobj
+1271 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 115.18 267.893 126.084]
+/Subtype /Link
+/A << /S /GoTo /D (section.1.10) >>
+>> endobj
+1272 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 95.3 160.089 104.276]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.2) >>
+>> endobj
+1273 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 83.364 192.737 92.211]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.1) >>
+>> endobj
+1274 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 71.29 189.389 80.256]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.2) >>
+>> endobj
+6 0 obj <<
+/D [1277 0 R /XYZ 72 600.215 null]
+>> endobj
+1276 0 obj <<
+/Font << /F28 1227 0 R /F31 1229 0 R /F38 1279 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1336 0 obj <<
+/Length 1879      
+/Filter /FlateDecode
+>>
+stream
+xÚíœßw›6ÇßóWð´ÙçÌ
 �$ÄžÚä$iwÚµKÓ“‡®Ä(¶V@
 p²î¯Ÿ0’l#’懜&5/1ÇÆúè^Ýû½Wöœ™ã9Ç{žzt}�8ž„Pü…;¥¸`œ<9ÞÛ?Ýûõ(NäFØÇÎé…C°Aè„HœòCç4q>�|7O@€¼Ñá¿5-ó8
 O|ñì/ÏóSZµOâ<i^Ôs–·‡9OÄåϧ¿ë[s>MFîx‚<ï>À(zÀ¿wFx�Œ‚hãôíÙ‰—Op#„%()
 ”4®Y>k!Ð1@£ë¹]”<k�ø¢NYnƒ¡¿ˆúØ@Ϥؤ<WCÿSûpÉèØG£+cà}‚Ÿ¯¥<²iÝDÑ·FKŠoyI¥Û;fÓ
 &¬¤Óš5,/›3-)p€vKhÁC¡a-”Ð>LKV4~ñ—Mǘ'ÚWêElº¨jž±ÿô•7”~à
 p�КñÅa‘eqùµûq€
 òv[0£›("k#IñhQÖsZ¶ÖQÕ‹ÄDÂï�Pød-ÀŸ¸Œð'¾À
+H‹µ‰ï=ñÑ+íðÞõFƒ7�x²ü?¶—ïr3ëÙÆúØ
 p´9ÉÈI&o¢½£šÆ5MÌ|
 ÓÌÂü
+-¹ˆÀõ%½}.œÂMè O_o�`d� Ê÷ß²jJÓ4Î)_Ñ,	ƒ
Ûñ!o‹Ž
 JÇ~V²•"ð¾
 2â³2Îd&ª›ž(7ð=à�Pð0G¯îm}šAíæ_¶Ÿ¾_2zÑ	Ä_çñtº(…÷hŸ¿b"0/¥[á«ÛnÅ
 ^ª¯¸üzYó�;_(|¬8ó®3¦wr–lj¯¼©é�^TßVŒ~O1DšË³LäMâ}xnÊ!|FæÚ;êÐRò	µ'}×J¥{äPV2Ú˜ÎßB„wÇ…n‡�¶
 ¥šžÐ
 ZÒ|J%š8Mï!ñÀ é±É	Yã¤Ô³Ãý–FƺÛIç¶c¼Í¤™I§XÈ
 áH†%b™
 ”YBò1G8´“ UL²¨¹X抔6‹œ¡äëaËV¶‰Vq�pØ5+*Ó#��ÕI›²HSÅK§sð‹ž��} ^4Ë®X£»·€Á�‡Ú€H¬A„]ˆG,•Goi¾0¢Yo¨sZ†–²¤c-
 ð0aõõQ„rFÖ,w
n(é½Fˆý
Þ}¨‘Àµ°Kíl
 q.áKÍàzx
	j÷‚‡¬Á#]x¯hZÜ€
 �aÑûŽo“¡b™¡j}Y«¥oXMW¢ôš Þ§8ûoB¶�®b�®žÍÇh$uÄ×íCʾŒA£æöÞñõúxHv»#“ØÊf°ÎM_­;p=›^gEÉQi‰w€h`k0‚a
 Ìã|¦ÔʇÿÁ—êÏfµé¶€|=éÑï
 ïh‹þ4”þTwâu\±z.Gõk=7U· ˆG°ïHCíH—$BJ‚Ìx%–¼”Çüüo:­Í²L
 
 öu3Ka{pzj·ú¾¤	mj“9Mn
 áÕw‚¦
 L¹ß™«¼ìU)<©ò¸¼ãyS.½CçÔTŒÂ
ݵÌ|kÌ”�…{¥óÐ7¬ªe‘t…‹)?©–I]?åÍÕ^“83K¦øéí/±X
µHC©rÇ´îià¨ÖÏÎiœ¬ô
 ýšsÝ‘WË&£°õd7û؈n,ÂÀ·‡Ñ3êkÝ©Ñ8
 Âh×ú¢À%¢
 æÕ¢Ô
 êy,G½àkû–Zdj'ÏeãÛâ”™]ª
 ëŠF:€SZÙËUkÍ”�ZñU[qêVB<,þ�gOjÃÇé8@£2nJ±²—mÕ·qýÖQ0ÄÝ÷â­ñÞxB£�E²Ö÷©·jZRÚÓß2TƒîH
 Û#Zb¯ó¦üsÙX
 ÿ¢ÉMUSTgûvµUÌ=§
 `l�ñ[01Ÿ
 õ
 
 /6/ÔÂÌL]‚ �‹ô°µ(=8úCð¢Tݽ¦�`hÕmÀ„öì¶`Žùt-ÔÖ»3–’]ß®ëFƒ_-QÉÒ7
 
 ñгMK-=ê
 úŽLªöû¤”§ü<N+·�¾Í_,ØÙeƒØc‚[&‡mÜœË-&{’Š(ÚÐÃ"8t<-€a
 p£r¨ë,^/³ó¢©
 ®
 o‘'<>O
 b´³at€g¯²H‹ç„Êý9kii±¸õúñ,·³n
Œo/@‹Z0»O•Ý$L5tk�¨k>u|nÆÊ
 
 ÒÎ-ÐÒfä{7¥�	‹žÊØ,ª…„™ÛT‰f
 &c¹4®L=ÈC?t Ý"±§½ùZ	¨hÙ“ã$´Ùž¤N³i�ZJ~€>Ã-˜�EFR8èþdTS¸®º�-=^ïŠ%3j®GÁÁVîÂAª
gc"
 W¹ò\ëƒolßÝ´§"®ç&ˆg�Û„Ô‘läãáéÞ?{@
 zpBßAÐõqèL³½OŸ='§o¨EĹZ¾(s ®bqœ:öþl~Ô_oo}¿¥ÊØÆ'‹Oü¦õ‚
+endstream
+endobj
+1335 0 obj <<
+/Type /Page
+/Contents 1336 0 R
+/Resources 1334 0 R
+/MediaBox [0 0 595.276 841.89]
+/Parent 1230 0 R
+/Annots [ 1275 0 R 1280 0 R 1281 0 R 1282 0 R 1283 0 R 1284 0 R 1285 0 R 1286 0 R 1287 0 R 1288 0 R 1289 0 R 1290 0 R 1291 0 R 1292 0 R 1293 0 R 1294 0 R 1295 0 R 1296 0 R 1297 0 R 1298 0 R 1299 0 R 1300 0 R 1301 0 R 1302 0 R 1303 0 R 1304 0 R 1305 0 R 1306 0 R 1307 0 R 1308 0 R 1309 0 R 1310 0 R 1311 0 R 1312 0 R 1313 0 R 1314 0 R 1315 0 R 1316 0 R 1317 0 R 1318 0 R 1319 0 R 1320 0 R 1321 0 R 1322 0 R 1323 0 R 1324 0 R 1325 0 R 1326 0 R 1327 0 R 1328 0 R 1329 0 R 1330 0 R 1331 0 R 1332 0 R ]
+>> endobj
+1275 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 758.712 236.472 767.678]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.3) >>
+>> endobj
+1280 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 744.819 257.582 755.723]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.4) >>
+>> endobj
+1281 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 734.921 177.245 743.768]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.5) >>
+>> endobj
+1282 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 722.966 200.876 731.812]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.6) >>
+>> endobj
+1283 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 708.953 280.556 719.857]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.7) >>
+>> endobj
+1284 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 696.998 152.587 707.902]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.8) >>
+>> endobj
+1285 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 685.043 167.252 695.947]
+/Subtype /Link
+/A << /S /GoTo /D (section.2.9) >>
+>> endobj
+1286 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 663.26 150.774 674.139]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.3) >>
+>> endobj
+1287 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 653.227 176.657 662.074]
+/Subtype /Link
+/A << /S /GoTo /D (section.3.1) >>
+>> endobj
+1288 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 639.215 168.358 650.119]
+/Subtype /Link
+/A << /S /GoTo /D (section.3.2) >>
+>> endobj
+1289 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 629.317 171.396 638.164]
+/Subtype /Link
+/A << /S /GoTo /D (section.3.3) >>
+>> endobj
+1290 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 605.476 195.406 616.355]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.4) >>
+>> endobj
+1291 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 593.387 337.393 604.291]
+/Subtype /Link
+/A << /S /GoTo /D (section.4.1) >>
+>> endobj
+1292 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 581.432 319.33 592.336]
+/Subtype /Link
+/A << /S /GoTo /D (section.4.2) >>
+>> endobj
+1293 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 569.476 247.281 580.38]
+/Subtype /Link
+/A << /S /GoTo /D (section.4.3) >>
+>> endobj
+1294 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 559.579 235.495 568.425]
+/Subtype /Link
+/A << /S /GoTo /D (section.4.4) >>
+>> endobj
+1295 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 547.623 167.252 556.47]
+/Subtype /Link
+/A << /S /GoTo /D (section.4.5) >>
+>> endobj
+1296 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 523.783 188.861 534.662]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.5) >>
+>> endobj
+1297 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 511.693 178.6 522.597]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.1) >>
+>> endobj
+1298 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 499.738 144.846 510.642]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.2) >>
+>> endobj
+1299 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 489.84 173.987 498.687]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.3) >>
+>> endobj
+1300 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 477.885 173.06 486.732]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.4) >>
+>> endobj
+1301 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 465.81 174.166 474.776]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.5) >>
+>> endobj
+1302 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 453.975 187.446 462.821]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.6) >>
+>> endobj
+1303 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 442.019 191.223 450.866]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.7) >>
+>> endobj
+1304 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 428.007 176.926 438.911]
+/Subtype /Link
+/A << /S /GoTo /D (section.5.8) >>
+>> endobj
+1305 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 406.224 221.409 417.103]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.6) >>
+>> endobj
+1306 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 394.134 247.062 405.038]
+/Subtype /Link
+/A << /S /GoTo /D (section.6.1) >>
+>> endobj
+1307 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 382.179 281.523 393.083]
+/Subtype /Link
+/A << /S /GoTo /D (section.6.2) >>
+>> endobj
+1308 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 370.224 334.125 381.128]
+/Subtype /Link
+/A << /S /GoTo /D (section.6.3) >>
+>> endobj
+1309 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.004 348.44 200.029 359.319]
+/Subtype /Link
+/A << /S /GoTo /D (chapter.7) >>
+>> endobj
+1310 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 336.351 217.623 347.255]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.1) >>
+>> endobj
+1311 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 324.395 187.167 335.299]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.2) >>
+>> endobj
+1312 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 312.44 217.882 323.344]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.3) >>
+>> endobj
+1313 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 300.485 285.477 311.389]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.4) >>
+>> endobj
+1314 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 288.53 282.489 299.434]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.5) >>
+>> endobj
+1315 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 276.575 262.295 287.479]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.6) >>
+>> endobj
+1316 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 264.62 242.549 275.524]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.7) >>
+>> endobj
+1317 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 252.664 211.715 263.568]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.8) >>
+>> endobj
+1318 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 240.709 190.345 251.613]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.9) >>
+>> endobj
+1319 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 228.754 193.524 239.658]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.10) >>
+>> endobj
+1320 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 216.799 245.239 227.703]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.11) >>
+>> endobj
+1321 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 204.844 261.936 215.748]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.12) >>
+>> endobj
+1322 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 192.889 238.066 203.793]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.13) >>
+>> endobj
+1323 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 180.933 321.512 191.837]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.14) >>
+>> endobj
+1324 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 168.978 253.219 179.882]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.15) >>
+>> endobj
+1325 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 158.961 173.18 167.927]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.16) >>
+>> endobj
+1326 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 145.068 250.181 155.972]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.17) >>
+>> endobj
+1327 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 133.113 238.644 144.017]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.18) >>
+>> endobj
+1328 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 121.158 225.383 132.062]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.19) >>
+>> endobj
+1329 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 109.202 280.666 120.106]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.20) >>
+>> endobj
+1330 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 97.247 224.248 108.151]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.21) >>
+>> endobj
+1331 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 85.292 280.177 96.196]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.22) >>
+>> endobj
+1332 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.948 73.337 249.892 84.241]
+/Subtype /Link
+/A << /S /GoTo /D (section.7.23) >>
+>> endobj
+1334 0 obj <<
+/Font << /F31 1229 0 R /F38 1279 0 R /F28 1227 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1393 0 obj <<
+/Length 1771      
+/Filter /FlateDecode
+>>
+stream
+xÚíœ]w›6Çïý)ØÍjN�ˆ]uyi–n}Yãžœ�®g#¶bë
 p›ìÓOXÛˆ¦Y+l7æ&†¢Ÿ
 =ý%áZ˵Îznùé@—X®ãHüDÄ·RqBûòõYïhØû马Ð	}è[Ãk‹øNˆ�`ñ
 ¬áØzÛ
 ˆì
Ánÿb1›Eé­=€â ¹–Ÿù”ÊÂGžŒU1âcY˜'ËYÂåÑ(Ž²Œfö»á³êi­·쓾c°ëîÍ
+ïù½ú?†H¸þÆ×÷§#.à„W
 °äpœÒ(g|"k5¥lžËò•
 Ýþ"Ï®×2÷­–wé
 ÈsÈ|‰ìõ‚óŠØï4‘¦ã*ÊGSYœAT{¨ÀC
 %�1G)�”Îh¾Š+ÆsšF£œÙ÷?Ú÷iyb¾Pñv�&³õ(Ô¢Ž`ò�)µÃů¸�¦¯
+ŸQ"ògòè˧µ”ôdâ¨käñ˜Ž’4Ê“´þà~ìY7Ölh®Å‡²fŸ'cv}[Uí<^L×*ôÉzŽùLK÷>˜&ܯ!äY“[€–zk
 @$
 Ñæ�+n}¼ÈòdÆþÝh÷Oƒ<ßñ<(–¿�çÿÏ㬫¿
Ïá²ÙXˆÄy…þ›ÓÑzkÉdw©K
 
 ˜ÔØRJ+
~s€*fç«dUH
 �UɃfÕ¹»úÆz
+à/ãqp´P!79廊˱Vž§Lé~ªzî\%H¾$¾9$sâ2}þåº0Ö[DÐwD¨‘B`ŒúL×7|¯FÁóbx«êx‘Uç‹Zþû&¥Y²HGz
 ä?ȼHŒU<V?´=ÜO#žÅ›
+ð‘�q_ÕûŒòE½™Ïh–E“†š‡þáÈSJœ8¾Âq™²N‹¡Ñ'5*šÍ“TŒ˜ì
 Ü%“–�Ý©+•�*]ù+º²îâ}Q[B³ÚR5¬°Ò–GËÜ&¼IQúnx@*eKbšR›a¥6�Ä@ý}>M“ÅdZ¿'rAÇpáUJs>�ëþŸ¶è3ú4Ž“eW”Ühr1ð;f[gVêÒ£$�+XÇ�k
 §çuAg 4°Ô·',%Eê“sZ‰«W·ù4áÚp
 “ŽÙ®˜•"øb9¨{ZKR�þ„êÃŒ.îö‰a¥7ƒ2Ù•)mÍÍäbhCcy‹b¶9KWº/)�â»
 ä?H^-‡QhÞð<⓸óDV³‚¡ Ð(»ýA73QK[ *RÕLœçÜül< 4HRDÑ")
 6›§kùm&‚¬þt
 ‚
 Cd€+çõ*2Èq™Ó˜Í_sÑhšŠôµ,þ“Ò
 rûHëÓÜàÐ&²¡g
 а…eXNV�©rñ7�™	¿Q^g�î¤BÐVÖÔ Áª—›‰±r^MÁ(ÍeZçqЩ¼-š§1ódáâ3“Õ$€�6ßxHƒ‡Ôt[ÙIŠ
 ¦&;¯
 õ~MÓšaõÞJ©+‡ûŠñq÷=ì>[ˆ,dÖá”xÎu‘§O…¤‹¥¶pÝg]Q!
 ‹[‹XÒ¦^Îi-jß=	´±À¸Ž’G/•üüÈÔÌb}
+!
 ÏUÙÖl�©E§N/š
 y,Ã-%æˆ*Yu’FE„®L³*ïÒÕ*é†Î?ÄAÇpËðü
+ž’UÇqÂé¡êß�bh.•
+{ÊÊÀ«"p4�ø„ÖVƧ.ΖU²A>j¿ÏÐ&š‰6¡¾�æö—8y°##Èx®92j�ÏÎF
 {¬ ßuƒ-wƒ
 0“”0
 S;§Up�]o¢Žá~ÁS{�~+$ã}¬