RubyGems - bixbite - Versions diffs - 0.1.0 - Mend

bixbite 0.1.0

Files changed (194) hide show

data/template/assets/naturaldocs/NaturalDocs/Help/styles.html ADDED

@@ -0,0 +1,52 @@
+<html><head><title>CSS Styles - Natural Docs</title><link rel=stylesheet type="text/css" href="styles.css"><style type="text/css"><!--
+        .StyleTable {
+            margin: 1em 5ex 0 5ex }
+        .StyleTable td {
+            padding-bottom: .5em}
+        .StyleName {
+            font: bold 12pt Georgia, serif;
+            }
+        .StyleView,
+        .StyleDownload
+            {
+            padding-left: 3ex;
+            }
+        .StyleDescription {
+            width: 100%;
+            padding-left: 3ex }
+        .StyleView,
+        .StyleDownload,
+        .StyleDescription {
+            padding-top: 1px;
+            }
+        .IE .StyleView,
+        .IE .StyleDownload,
+        .IE .StyleDescription {
+            padding-top: 0;
+            }
+--></style><script language=JavaScript src="javascript/PNGHandling.js"></script><script language=JavaScript src="javascript/BrowserStyles.js"></script></head><body marginwidth=0 marginheight=0 leftmargin=0 topmargin=0><script language=JavaScript><!--
+OpeningBrowserTags();// --></script>
+<!-- saved from url=(0026)http://www.naturaldocs.org -->
+<table width=100% border=0 cellspacing=0 cellpadding=0><tr><td colspan=3 class=Header><table width=100% border=0 cellspacing=0 cellpadding=0><tr><td><img src="images/header/leftside.png" width=30 height=75><a href="index.html"><img src="images/header/logo.png" width=524 height=75 alt="Natural Docs"></a></td><td align=right><img src="images/header/rightside.png" width=30 height=75></td></tr></table></td></tr><tr><td><img src="images/header/overleftmargin.png" width=10 height=6></td><td class=SideMenuTop><img src="images/header/overmenu.png" width=14 height=6></td><td class=BodyTop><img src="images/header/overbody.png" width=24 height=6></td></tr><tr><td></td><td class=SideMenu nowrap><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/about.png" width=52 height=13 alt="About"></div><div class=SideMenuBody><a href="languages.html" class=SideMenuEntry>Language Support</a><a href="output.html" class=SideMenuEntry>Output Formats</a></div></div><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/using.png" width=45 height=13 alt="Using"></div><div class=SideMenuBody><a href="documenting.html" class=SideMenuEntry>Documenting<br>Your Code</a><a href="keywords.html" class=SideMenuEntry>Keywords</a><a href="running.html" class=SideMenuEntry>Running</a><a href="troubleshooting.html" class=SideMenuEntry>Troubleshooting</a></div></div><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/customizing.png" width=96 height=13 alt="Customizing"></div><div class=SideMenuBody><a href="menu.html" class=SideMenuEntry>Organizing the Menu</a><span class=SideMenuEntry id=SelectedSideMenuEntry>CSS Styles</span><a href="customizingtopics.html" class=SideMenuEntry>Topics and Keywords</a><a href="customizinglanguages.html" class=SideMenuEntry>Languages, Indexes,<br>and Prototypes</a></div></div><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/community.png" width=86 height=13 alt="Community"></div><div class=SideMenuBody><a href="http://www.naturaldocs.org/" class=SideMenuEntry>Web Site</a><a href="http://www.naturaldocs.org/mailinglist.html" class=SideMenuEntry>Mailing Lists</a><a href="http://www.naturaldocs.org/messageboards.html" class=SideMenuEntry>Message Boards</a><a href="http://www.naturaldocs.org/bugs.html" class=SideMenuEntry>Bugs and<br>Feature Requests</a></div></div></td><td class=Body width=100%><div class=PageTitle>CSS Styles</div><div class=TOC><a href="#DefaultStyles">Default Styles</a> &middot; <a href="#Customizing">Customizing</a> &middot; <a href="#CommonCustomizations">Common Customizations</a></div><div class=Topic><a name="DefaultStyles"></a><div class=TopicTitle>Default Styles</div><p>These are the styles that come with Natural Docs.&nbsp; They all follow the same color scheme and general layout; the choices are more so that you can choose the style of text you want.</p><p>You choose which style you want for your project by adding &ldquo;<code>-s <i>[style name]</i></code>&rdquo; to the command line.</p><table width=100% border=0 cellspacing=0 cellpadding=0 class=StyleTable><tr><td class=StyleName>Default</td><td class=StyleDescription>This is the default style that Natural Docs uses.&nbsp; Most of the text is 10pt Verdana.</td></tr><tr><td class=StyleName>Small</td><td class=StyleDescription>Smaller fonts than Default with most of the text using 8pt Verdana.&nbsp; Some people like the small fonts because you can fit more on the screen at once.&nbsp; However, some people hate them and find them hard to read.</td></tr><tr><td class=StyleName>Roman</td><td class=StyleDescription>Serif fonts with most of the text using 12pt Roman.&nbsp; Some people prefer Roman fonts, usually those that have decent anti-aliasing displays like Mac OS X or Windows XP with ClearType.</td></tr></table></div><div class=Topic><a name="Customizing"></a><div class=TopicTitle>Customizing</div><p>There are two ways to customize the CSS files.&nbsp; One is to build your own file from scratch, and the other is to make a touch-up file that gets applied after one of the default styles.&nbsp; Either way you want to create your own CSS file in your project directory (the one you use with <code>-p</code>) or if you plan on sharing it between many projects, in Natural Docs&rsquo; Styles directory.</p><p>To use a custom file, no matter where you put it, you just use it with <code>-s</code> without the CSS extension.&nbsp; So if you made Red.css, you use &ldquo;<code>-s Red</code>&rdquo;.&nbsp; If you made a touch-up file instead, you use it after one of the default styles, such as with &ldquo;<code>-s Default Red</code>&rdquo;.&nbsp; If you&rsquo;re so inclined, you can string as many touch-up files together as you want or use one of your own as a base.</p><p>The <a href="http://www.naturaldocs.org/documentation/html/files/Info/CSSGuide-txt.html">CSS Guide</a> documents the page structure and CSS styles of Natural Docs&rsquo; output.&nbsp; Always remember to check its <a href="http://www.naturaldocs.org/documentation/html/files/Info/CSSGuide-txt.html#Revisions">revisions section</a> every time you upgrade Natural Docs because it may change between releases.</p></div><div class=Topic><a name="CommonCustomizations"></a><div class=TopicTitle>Common Customizations</div><a name="WebStyleParagraphs"></a><div class="SubTopic First">Web-Style Paragraphs</div><p>Natural Docs defaults to print-style paragraphs like the one you are reading.&nbsp; Each one is indented and there are no blank lines between them.&nbsp; To switch to web-style paragraphs, which have blank lines and no indents, add this to your custom CSS file:</p><pre class=Example>p {
+   text-indent: 0;
+   margin-bottom: 1em;
+   }
+</pre><a name="PrototypeColors"></a><div class="SubTopic">Prototype Colors</div><p>If you&rsquo;ve <a href="customizingtopics.html#AddingTopicTypes">added a custom topic type</a> and have it <a href="customizinglanguages.html#Prototypes">finding prototypes for you</a>, you may want to have them appear in a different color than the default black and white.&nbsp; Add this to your custom CSS file:</p><pre class=Example>.C<i>[type]</i> .Prototype {
+   background-color: <i>[color]</i>;
+   border-color: <i>[color]</i>;
+   }
+</pre><p>Replace <code><i>[type]</i></code> with the name of your topic type, minus any symbols and spaces.&nbsp; So if you added a type &ldquo;Sound Effect&rdquo;, you would apply the style to &ldquo;<code>.CSoundEffect .Prototype</code>&rdquo;.</p></div></td></tr><tr><td></td><td class=SideMenuBottom><table width=100% border=0 cellspacing=0 cellpadding=0><tr><td class=SideMenuBottomLeft><img src="images/menu/bottomleft.png" width=18 height=19></td><td class=SideMenuBottomRight><img src="images/menu/bottomright.png" width=18 height=19></td></tr></table></td><td class=BodyBottom>Copyright &copy; 2003-2008 Greg Valure</td></tr></table><script language=JavaScript><!--
+ClosingBrowserTags();// --></script></body></html>

data/template/assets/naturaldocs/NaturalDocs/Help/troubleshooting.html ADDED

@@ -0,0 +1,18 @@
+<html><head><title>Troubleshooting - Natural Docs</title><link rel=stylesheet type="text/css" href="styles.css"><style type="text/css"><!--
+            .FAQSummary a:link,
+            .FAQSummary a:visited,
+            .FAQSummary a:hover,
+            .FAQSummary a:active {
+                color: #000000;
+--></style><script language=JavaScript src="javascript/PNGHandling.js"></script><script language=JavaScript src="javascript/BrowserStyles.js"></script></head><body marginwidth=0 marginheight=0 leftmargin=0 topmargin=0><script language=JavaScript><!--
+OpeningBrowserTags();// --></script>
+<!-- saved from url=(0026)http://www.naturaldocs.org -->
+<table width=100% border=0 cellspacing=0 cellpadding=0><tr><td colspan=3 class=Header><table width=100% border=0 cellspacing=0 cellpadding=0><tr><td><img src="images/header/leftside.png" width=30 height=75><a href="index.html"><img src="images/header/logo.png" width=524 height=75 alt="Natural Docs"></a></td><td align=right><img src="images/header/rightside.png" width=30 height=75></td></tr></table></td></tr><tr><td><img src="images/header/overleftmargin.png" width=10 height=6></td><td class=SideMenuTop><img src="images/header/overmenu.png" width=14 height=6></td><td class=BodyTop><img src="images/header/overbody.png" width=24 height=6></td></tr><tr><td></td><td class=SideMenu nowrap><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/about.png" width=52 height=13 alt="About"></div><div class=SideMenuBody><a href="languages.html" class=SideMenuEntry>Language Support</a><a href="output.html" class=SideMenuEntry>Output Formats</a></div></div><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/using.png" width=45 height=13 alt="Using"></div><div class=SideMenuBody><a href="documenting.html" class=SideMenuEntry>Documenting<br>Your Code</a><a href="keywords.html" class=SideMenuEntry>Keywords</a><a href="running.html" class=SideMenuEntry>Running</a><span class=SideMenuEntry id=SelectedSideMenuEntry>Troubleshooting</span></div></div><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/customizing.png" width=96 height=13 alt="Customizing"></div><div class=SideMenuBody><a href="menu.html" class=SideMenuEntry>Organizing the Menu</a><a href="styles.html" class=SideMenuEntry>CSS Styles</a><a href="customizingtopics.html" class=SideMenuEntry>Topics and Keywords</a><a href="customizinglanguages.html" class=SideMenuEntry>Languages, Indexes,<br>and Prototypes</a></div></div><div class=SideMenuSection><div class=SideMenuTitle><img src="images/menu/community.png" width=86 height=13 alt="Community"></div><div class=SideMenuBody><a href="http://www.naturaldocs.org/" class=SideMenuEntry>Web Site</a><a href="http://www.naturaldocs.org/mailinglist.html" class=SideMenuEntry>Mailing Lists</a><a href="http://www.naturaldocs.org/messageboards.html" class=SideMenuEntry>Message Boards</a><a href="http://www.naturaldocs.org/bugs.html" class=SideMenuEntry>Bugs and<br>Feature Requests</a></div></div></td><td class=Body width=100%><div class=PageTitle>Troubleshooting</div><div class=FAQSummary><div class=FAQSummaryGroup>Natural Docs Issues</div><ul><li><a href="#NoDocs" class=FAQSummaryEntry>I don&rsquo;t get any documentation.</a></li><li><a href="#MissingTopics" class=FAQSummaryEntry>Some of my topics don&rsquo;t show up.</a></li><li><a href="#BadFormatting" class=FAQSummaryEntry>Some of my topics aren&rsquo;t formatting correctly.</a></li><li><a href="#NoPrototypes" class=FAQSummaryEntry>I&rsquo;m not getting prototypes.</a></li><li><a href="#LinksDontResolve" class=FAQSummaryEntry>My links aren&rsquo;t working.</a></li></ul><div class=FAQSummaryGroup>Windows Issues</div><ul><li><a href="#CantFindPerl" class=FAQSummaryEntry>I get the message &ldquo;Bad command or file name&rdquo; or &ldquo;perl is not recognized&rdquo;.</a></li><li><a href="#CantFindND" class=FAQSummaryEntry>I get the message &ldquo;Can&rsquo;t open perl script NaturalDocs&rdquo;.</a></li></ul></div><div class=FAQGroup>Natural Docs Issues</div><div class=FAQEntry><div class=FAQEntryTitle><a name=NoDocs></a>I don&rsquo;t get any documentation</div><div class="First SubTopic">Is it recognizing your source files?</div><p>If Natural Docs has never said &ldquo;Parsing <i>n</i> files...&rdquo; when you run it, or <i>n</i> was way too low a number, it is not finding your source files.</p><p>If it has, try this test.&nbsp; Run Natural Docs once.&nbsp; Edit one of your source files and save it.&nbsp; Run Natural Docs again.&nbsp; If it doesn&rsquo;t say &ldquo;Parsing 1 file...&rdquo; it is not recognizing your file.</p><div class=SubTopic>No, it&rsquo;s not recognizing them</div><p>The most likely scenario is that Natural Docs doesn&rsquo;t associate the file extension you&rsquo;re using with your programming language.&nbsp; Open <code>Languages.txt</code> in Natural Docs&rsquo; Config directory and find your language.&nbsp; Underneath it you should see a line that says something like &ldquo;<code>Extensions: c cpp cxx h hpp hxx</code>&rdquo;.&nbsp; Add the file extensions you use and try again.</p><p>If you use extensionless or .cgi files, do the same thing but instead look for a line that says something like &ldquo;<code>Shebang Strings: tclsh wish expect</code>&rdquo;.&nbsp; If it is not there, you may need to add it yourself.&nbsp; Edit it to include whatever appears in your shebang (<code>#!</code>) line that would say this file belongs to your language.</p><p>Otherwise just make sure you included the directory or one of its parents with <a href="running.html#CommandLine"><code>-i</code> on the command line.</a></p><div class=SubTopic>Yes, it&rsquo;s recognizing them</div><p>First note that unless you have <a href="languages.html">full language support</a>, Natural Docs will only include <a href="documenting.html">what you write for it.</a>&nbsp; It will not be able to scan your code and pick out all the classes and functions on its own.</p><p>If the problem is with text files, the most likely scenario is that you&rsquo;re not <a href="documenting/reference.html#TextFiles">including topic lines.</a>&nbsp; Like in comments, only things that appear under &ldquo;<code>keyword: name</code>&rdquo; lines count as Natural Docs content.</p><p>If this is happening in code, remember that comments must appear alone on a line.&nbsp; You cannot put Natural Docs comments on the same line as code.&nbsp; This includes having anything appear after a closing block comment symbol.</p></div><div class=FAQEntry><div class=FAQEntryTitle><a name=MissingTopics></a>Some of my topics don&rsquo;t show up</div><ul><li><a href="keywords.html">Check the list of keywords</a> to see if the one you&rsquo;re using is there and you spelled it correctly.&nbsp; Note that the web page only has the default set of keywords.&nbsp; You may need to check <code>Topics.txt</code> in Natural Docs&rsquo; Config directory and your project directory if you&rsquo;ve edited them</li><li>If the topics appear in code, make sure that the comments are alone on a line.&nbsp; You cannot put Natural Docs content on the same line as code.&nbsp; This includes having anything appear after a closing block comment symbol.</li><li>Make sure that if you have more than one topic in a comment, there is a blank line above the topic line.</li><li>If you have text boxes or lines, make sure they are completely unbroken.&nbsp; You can also try removing them completely.</li><li>If the topics appear in a text file, make sure you included topic lines.&nbsp; Like in comments, only things that appear after &ldquo;<code>keyword: name</code>&rdquo; lines count as Natural Docs content.&nbsp; You could just add a <code>Title:</code> line to the top of the file to fix this.</li></ul></div><div class=FAQEntry><div class=FAQEntryTitle><a name=BadFormatting></a>Some of my topics aren&rsquo;t formatting correctly</div><ul><li><a href="documenting/reference.html#Headings">Headings</a> must have a blank line above them.</li><li>Lines directly after <a href="documenting/reference.html#BulletLists">bullet</a> or <a href="documenting/reference.html#DefinitionLists">definition</a> lines are part of the previous bullet or definition, even if it&rsquo;s not indented.&nbsp; Skip a line first to do something else</li><li>If you&rsquo;re getting symbols scattered throughout your text, make sure any text boxes or lines are completely unbroken.&nbsp; You can also try removing them altogether.</li><li>If your example source code is getting mangled, remember to use the <a href="documenting/reference.html#CodeAndTextDiagrams">example code syntax</a>.</li><li>If a line&rsquo;s becoming a <a href="documenting/reference.html#Headings">heading</a> but shouldn&rsquo;t, either get rid of the colon at the end or break it into two lines so the colon appears on the second line</li><li>If a line&rsquo;s becoming a <a href="documenting/reference.html#DefinitionLists">definition</a> but shouldn&rsquo;t, either get rid of the space-dash-space (use two dashes or remove one of the spaces) or break it into two lines so that the space-dash-space is on the second line.</li></ul><p>I realize the last two aren&rsquo;t great.&nbsp; If you have any ideas as to how to reliably detect these kinds of false positives, <a href="#" onClick="location.href='mai' + 'lto:' + 'gregv' + 'alure' + '@' + 'natural' + 'docs.org'; return false;">e-mail me</a>.</p></div><div class=FAQEntry><div class=FAQEntryTitle><a name=NoPrototypes></a>I&rsquo;m not getting prototypes</div><ul><li>The topic must appear directly above the thing it&rsquo;s documenting.</li><li>Topics <a href="documenting/reference.html#DefinitionLists">documented in lists</a> will not get prototypes, even if the list break apart in the output.</li><li>The topic name must be present in the prototype somewhere.&nbsp; Make sure the topic title has the same case as in the prototype and that it&rsquo;s not misspelled.&nbsp; This applies even if your language isn&rsquo;t case sensitive.</li><li>If you&rsquo;re documenting something with a new topic type you <a href="customizingtopics.html">added to <code>Topics.txt</code></a>, you must also <a href="customizinglanguages.html#Prototypes">edit <code>Languages.txt</code></a> to tell it how to detect prototypes for that type.</li></ul></div><div class=FAQEntry><div class=FAQEntryTitle><a name=LinksDontResolve></a>My links aren&rsquo;t working</div><p>If your links appear in the output as &ldquo;<code>&lt;text&gt;</code>&rdquo; instead of being converted to links, do the following:</p><ul><li>Make sure the target appears in the output.&nbsp; The easiest way is to see if it appears in the Everything index.</li><li>Make sure the link is spelled correctly and has the same case as what you&rsquo;re linking to.&nbsp; This applies even if your language isn&rsquo;t case sensitive.</li><li>If the topic your link appears in and the link target are not in the same class (or are not both global) make sure you include the class in the link with <code>class.target</code>, <code>class::target</code>, or <code>class-&gt;target</code>.&nbsp; You can check which classes topics appear in with the Everything index.&nbsp; If your topics are appearing in the wrong classes, fix the documentation remembering the <a href="documenting/reference.html#KeywordsTopicsAndScope">topic scoping rules</a>.</li></ul></div><div class=FAQGroup>Windows Issues</div><div class=FAQEntry><div class=FAQEntryTitle><a name=CantFindPerl></a>I get the message &ldquo;Bad command or file name&rdquo; or &ldquo;perl is not recognized&rdquo;</div><p>What&rsquo;s happening is that NaturalDocs.bat can&rsquo;t find Perl.&nbsp; You need Perl installed to run Natural Docs, so if you haven&rsquo;t done so already, you can download and install <a href="http://www.activestate.com/Products/activeperl/">ActiveState&rsquo;s ActivePerl</a> for free.</p><p>If you already have Perl, it&rsquo;s bin directory is either not in your path or the path isn&rsquo;t being used by whatever you&rsquo;re running it from, which happens on some IDEs.&nbsp; Edit NaturalDocs.bat and on the line that says &ldquo;<code>perl NaturalDocs %NaturalDocsParams%</code>&rdquo;, change <code>perl</code> to be the full path to perl.exe, such as <code>&ldquo;C:\perl\bin\perl.exe&rdquo;</code>.&nbsp; You need to include the quotes if there are spaces in the path.</p></div><div class=FAQEntry><div class=FAQEntryTitle><a name=CantFindND></a>I get the message &ldquo;Can&rsquo;t open perl script NaturalDocs&rdquo;</div><p>What&rsquo;s happening is that Perl can&rsquo;t find the Natural Docs script file.&nbsp; This happens when the working directory or &ldquo;start in&rdquo; folder isn&rsquo;t the directory Natural Docs was installed to.&nbsp; If changing that doesn&rsquo;t work, or if you don&rsquo;t have the option to set that, edit NaturalDocs.bat and find the line that says &ldquo;<code>perl NaturalDocs %NaturalDocsParams%</code>&rdquo;.&nbsp; Change <code>NaturalDocs</code> to include the full path Natural Docs was installed to, such as <code>&ldquo;C:\Program Files\Natural Docs\NaturalDocs&rdquo;</code>.&nbsp; You need to include the quotes if there are spaces in the path.</p></div></td></tr><tr><td></td><td class=SideMenuBottom><table width=100% border=0 cellspacing=0 cellpadding=0><tr><td class=SideMenuBottomLeft><img src="images/menu/bottomleft.png" width=18 height=19></td><td class=SideMenuBottomRight><img src="images/menu/bottomright.png" width=18 height=19></td></tr></table></td><td class=BodyBottom>Copyright &copy; 2003-2008 Greg Valure</td></tr></table><script language=JavaScript><!--
+ClosingBrowserTags();// --></script></body></html>

data/template/assets/naturaldocs/NaturalDocs/Info/CSSGuide.txt ADDED

@@ -0,0 +1,947 @@
+   Architecture: CSS Structure
+_______________________________________________________________________________
+It's important to understand the internal HTML file structure and styles in order to design your own CSS style for Natural Docs.  If
+you're content with the default styles, there's no need to read this document.
+Topic: Diagram Conventions
+    The diagrams are designed for clarity.  In the actual HTML, you'd obviously see "<table class=CDescriptionList></table>"
+    instead of "<table CDescriptionList></table CDescriptionList>".
+    - A tag with just a style, for example "CTitle", means an unspecified element with that class.  Style with .CTitle.
+    - A tag that includes a #, for example "#Menu", means an unspecified element with that ID.  Style with #Menu.
+    - A tag that includes a HTML element as well, for example "table CDescriptionList", means it will always be that element.  You
+      can style with either .CDescriptionList or table.CDescriptionList.
+    - A tag that has multiple classes or has an "and" in it, for example "CType and CTopic", means that both styles will apply to the
+      same element.  You can style it with .CType.CTopic, noting that the space between them must be omitted.
+    - A tag that has an "or" in it, for example "#Content or #Index", is just shorthand for either of those elements.  The diagram
+      applies to both of them but only one will actually appear at a time in the output.
+    - A tag or style with a question mark means that tag or style will only be there in certain situations.
+Topic: Page Structure
+_______________________________________________________________________________
+    The body tag is used to distinguish between the types of pages.
+    Unframed Content/Index Page:
+        (start diagram)
+        <body ContentPage or IndexPage)>
+            [browser styles]
+            <#Content or #Index>
+                Content or Index
+            </#Content or #Index>
+            <#Menu>
+                Menu
+            </#Menu>
+            <#Footer>
+                Footer
+            </#Footer>
+            [/browser styles]
+        </body ContentPage or IndexPage)>
+        (end diagram)
+    Unframed Search Results Popup Page:
+        (start diagram)
+        <body PopupSearchResultsPage>
+            [browser styles]
+            <#Index>
+                Index
+            </#Index>
+            [browser styles]
+        </body PopupSearchResultsPage>
+        (end diagram)
+    Framed Menu Page:
+        (start diagram)
+        <body FramedMenuPage>
+            [browser styles]
+            <#Menu>
+                Menu
+            </#Menu>
+            <#Footer>
+                Footer
+            </#Footer>
+            [browser styles]
+        </body FramedMenuPage>
+        (end diagram)
+    Framed Content/Index/SearchResults Page:
+        (start diagram)
+        <body FramedContentPage or FramedIndexPage or FramedSearchResultsPage>
+            [browser styles]
+            <#Content or #Index>
+                Content or Index
+            </#Content or #Index>
+            [browser styles]
+        </body FramedContentPage or FramedIndexPage or FramedSearchResultsPage>
+        (end diagram)
+Styles: Page Styles
+    ContentPage - An unframed content page.
+    IndexPage - An unframed index page.
+    PopupSearchResultsPage - A search results page for use in a popup iframe.
+    FramedContentPage - A framed content page.
+    FramedIndexPage - A framed index page.
+    FramedSearchResultsPage - A framed search results page.
+    #Footer - The page footer.  Will be in a framed menu page or on its own in a non-framed page.
+    See Also:
+        - <#Content>
+        - <#Menu>
+        - <#Index>
+        - <#Footer>
+Styles: Browser Styles
+_______________________________________________________________________________
+    Natural Docs pages include JavaScript to detect which browser the user is running and apply styles so that you can work
+    around browser quirks right in the CSS file.
+    The browser type and version styles will be applied immediately after the body tag.  However, neither are guaranteed to be
+    there; the user may have JavaScript turned off or be using a browser that isn't detected.  These styles should only be used to
+    correct minor flaws and should not be heavily relied on.
+    >   <body>
+    >       <browser type>?
+    >           <browser version>?
+    >
+    >           Page Content
+    >
+    >           <browser version>?
+    >       <browser type>?
+    >   </body>
+    For example, if a <CTopic>'s style is giving you problems in Internet Explorer 6, override it with .IE6 .CTopic.  If a <MTitle>'s
+    style gives you a problem in Opera 7 but only in frames, override it with .Framed.Opera7 .MTitle.
+    Browser Types:
+        If the browser is not one of the types below, neither this nor the browser version will be present.  There's the possibility that
+        some obscure browser will appear as one of the others by spoofing, but the most prominent of these, Opera, Konqueror, and
+        Safari, are taken care of.
+        IE - Internet Explorer
+        Firefox - Firefox and anything else based on the Gecko rendering engine.
+        Opera - Opera
+        Safari - Safari
+        Konqueror - Konqueror and anything else based on the KHTML rendering engine except Safari.
+    Browser Versions:
+        If the browser is not one of the versions below, this style will not be present.  The browser type still may be.
+        IE6 - Internet Explorer 6.x.
+        IE7 - Internet Explorer 7.x.
+        Firefox1 - Firefox 1.0.x and anything else based on Gecko 1.7.x.
+        Firefox15 - Firefox 1.5.x and anything else based on Gecko 1.8.0.x.
+        Firefox2 - Firefox 2.0.x and anything else based on Gecko 1.8.1.x.
+        Opera7 - Opera 7.x.
+        Opera8 - Opera 8.x.
+        Opera9 - Opera 9.x.
+        Safari2 - Safari 2.x.
+        Safari3 - Safari 3.x.
+    Notes:
+        Why not apply them to the body tag itself?  The JavaScript is easy enough and everything supports multiple classes, right?
+        Because IE 6 doesn't support multiple selectors so I wouldn't be able to combine browser and page styles.
+        .Opera.ContentPage will apply to all ContentPages in IE because it treats it as if only the last class is there.
+Topic: Content Structure
+_______________________________________________________________________________
+    All the topics of a given file is contained in a <#Content>.  All other content styles are prefixed with a C.
+    Surrounding each piece of content is a <CTopic> and its type; for example, CFunction for a function.  Inside that are the
+    <CTitle> and if necessary, <CBody>.  Inside <CBody> are analogues to all the top-level <NDMarkup> tags: <h1>, <p>, etc.
+    In addition to the top-level <NDMarkup> tags, you also have prototypes, class hierarchies, and summaries which are
+    described in their own sections.
+    (start diagram)
+    <#Content>
+        <CType (CFunction, CVariable, etc.)>
+            <CTopic and #MainTopic?>
+                <CTitle>
+                    Topic title
+                </CTitle>
+                <CBody>
+                    [Class Hierarchy]
+                    [Prototype]
+                    <CHeading>
+                        Heading
+                    <CHeading>
+                    <p>
+                        Paragraph
+                    </p>
+                    <pre>
+                        Code or text diagram
+                    </pre>
+                    <ul>
+                        <li>
+                            Bullet item
+                        </li>
+                    </ul>
+                    <CImageCaption>?
+                        Caption
+                    </CImageCaption>?
+                    <img>
+                    <a CImageLink>
+                        text
+                    </a CImageLink>
+                    <table CDescriptionList>
+                        <tr>
+                            <td CDLEntry>
+                                Entry
+                            </td CDLEntry>
+                            <td CDLDescription>
+                                Description
+                            </td CDLDescription>
+                        </tr>
+                    </table CDescriptionList>
+                    [Summary]
+               </CBody>
+           </CTopic and #MainTopic?>
+       </CType (CFunction, CVariable, etc.)>
+    </#Content>
+    (end diagram)
+    Take advantange of the CSS inheritance model.  For example, you can style all titles via .CTitle, and you can style
+    specific titles with .CType .CTitle.
+Styles: Content Styles
+    #Content - Parent element containing all topics.
+    CTopic - An individual topic.
+    CTitle - The title of a topic.
+    CBody - The body of a topic.  May not exist.
+    CHeading - Surrounds a heading.
+    CImageCaption - Surrounds an image caption.
+    CImageLink - Surrounds a link to an image.
+    CDescriptionList - A description list, which is the type of list you're reading right now.  Is implemented with a table.
+    CDLEntry - A description list entry, which is the left side.
+    CDLDescription - A description list description, which is the right side.
+    #MainTopic - The ID given to the main topic, which is the first in the file.  It is applied to the <CTopic>.
+    CType - A placeholder for all type-specific styles.  The actual styles will be C followed by the alphanumeric-only topic type name.
+                So the CType of a "PL/SQL Function" topic will actually be CPLSQLFunction.
+Topic: Menu Structure
+_______________________________________________________________________________
+    Everything is enclosed in a <#Menu>.  All other menu styles are prefixed with an M.
+    The title is an <MTitle> and will always be at the beginning of the menu if it exists.  If a subtitle exists as well, it will appear
+    as an <MSubTitle> inside <MTitle>.  Subtitles aren't allowed without titles.  Most other entries in the menu are contained in
+    <MEntries>.  Here's the diagram:
+    (start diagram)
+    <#Menu>
+        <MTitle>
+            Menu title
+            <MSubTitle>
+                Menu sub title
+            </MSubTitle>
+        </MTitle>
+        <MEntry>
+            <MFile (and #MSelected?)>
+                <a href>File</a href>
+            </MFile>
+        </MEntry>
+        <MEntry>
+            <MIndex (and #MSelected?)>
+                <a href>File</a href>
+            </MIndex>
+        </MEntry>
+        <MEntry>
+            <MText>
+                Text
+            </MText>
+        </MEntry>
+        <MEntry>
+            <MLink>
+                <a href>Link</a href>
+            </MLink>
+        </MEntry>
+        <MEntry>
+            <MGroup>
+                <a href>Group</a href>
+                <MGroupContent>
+                    (MEntries)
+                </MGroupContent>
+           </MGroup>
+        </MEntry>
+        <#MSearchPanel and MSearchPanelActive/Inactive>
+            <input #MSeachField>
+            <select #MSearchType>
+                <option #MSearchEverything>
+                <option>
+                <option>
+            </select #MSearchType>
+        </#MSearchPanel and MSearchPanelActive/Inactive>
+    </#Menu>
+    (if in unframed HTML)
+    <#MSearchResultsWindow>
+        <iframe #MSearchResults>
+        </iframe #MSearchResults>
+        <a #MSearchResultsWindowClose>
+    </#MSearchResultsWindow>
+    (end)
+    The <MFile> or <MIndex> entry that's currently selected will have the <#MSelected> ID, so you can reference it in CSS via
+    .MFile#MSelected.
+    The search panel is has its own ID, <#MSearchPanel>, but also has one of the classes <MSearchPanelActive> or
+    <MSearchPanelInactive> depending on whether any of the controls are selected or the results window is open.
+    <#MSearchResultsWindow> is separate because it may be floating.
+Styles: Menu Styles
+    #Menu - Parent element containing the entire menu.
+    MTitle - The title of the menu.
+    MSubTitle - The subtitle of the menu.  Will appear within <MTitle>.
+    MFile - A file entry.
+    MGroup - A group entry.
+    MGroupContent - A container for a <MGroup's> content.
+    MText - A plain text entry.
+    MLink - An external link entry.
+    MIndex - An index entry.
+    #MSelected - The ID of the currently selected <MFile> or <MIndex>.
+    MType - <MFile>, <MGroup>, <MText>, <MLink>, or <MIndex>.
+    #MSearchPanel - Contains all the search controls.
+    MSearchPanelActive - Applied to <#MSearchPanel> when any of the controls are selected or the results window is open.
+    MSearchPanelInactive - Applied to <#MSearchPanel> when not in use.
+    #MSearchField - The text input field of the search panel.
+    #MSearchType - The drop down type selector of the search panel.
+    #MSearchEverything - The <#MSearchType> option for the Everything index.
+    #MSearchResultsWindow - Contains all the search results elements.
+    #MSearchResults - Contains the iframe that will hold the results.
+    #MSearchRseultsWindowClose - The link to manually close the search results window.
+Topic: Class Hierarchy Structure
+_______________________________________________________________________________
+    Everything is contained in a single <ClassHierarchy>.  Each entry is surrounded by its type, such as <CHParent>, and the
+    generic <CHEntry>.  Depending on the context, entries may be surrounded by one or more <CHIndents>.
+    (start diagram)
+    <ClassHierarchy>
+        <CHIndent>?
+            <CHType>
+                <CHEntry>
+                    <a href>?
+                        Entry
+                    </a href>
+                </CHEntry>
+            </CHType>
+        </CHIndent>?
+    </ClassHierarchy>
+    (end diagram)
+Styles: Class Hierarchy Styles
+    ClassHierarchy - The topmost style containing everything.
+    CHEntry - A generic class entry.
+    CHParent - The style for a parent class.
+    CHCurrent - The style for the current class, which is the one the hierarchy is generated for.
+    CHChild - The style for a child class.
+    CHChildNote - The style for when a child is added that just shows how many other children were omitted.
+    CHIndent - A style used to indent a level.
+    CHType - <CHParent>, <CHCurrent>, <CHChild>, or <CHChildNote>.
+Topic: Summary Structure
+_______________________________________________________________________________
+    Everything is enclosed in a single <Summary>.  All the other summary styles are prefixed with an S.
+    <STitle> holds the actual word "Summary" and <SBorder> and <STable> hold the content.  <SBorder> exists because different
+    browsers apply table padding attributes in different ways.  <STable> exists as a class to separate the main table from any other
+    tables that may be necessary.  Here's a diagram:
+    >   <Summary>
+    >
+    >       <STitle>
+    >           Title
+    >       </STitle>
+    >
+    >       <SBorder>
+    >           <table STable>
+    >               ...
+    >           </table STable>
+    >       </SBorder>
+    >
+    >   </Summary>
+    On to the table content.
+    >   <tr SType and SEntry (and SIndent#?) (and SMarked?)>
+    >       <td SEntry>
+    >
+    >           <a href>Entry</a href>
+    >
+    >       </td SEntry>
+    >       <td SDescription>
+    >
+    >           Description
+    >
+    >       </td SDescription>
+    >   </tr SType and SEntry (and SIndent#?) (and SMarked?)>
+    <SIndent#> exist to allow indenting.  They're necessary because implementing it as nested tables, while structurally cleaner,
+    won't allow the desciptions to line up on the right throughout the entire summary.  <SMarked> will be applied on almost every
+    other row to allow for tinting to improve readability.
+    Use the power of CSS's inheritance rules to specify styles.  For example, to set the style of a group entry, apply it to
+    .SGroup .SEntry.  However, you could also apply a style to both the group's entry and description by applying the
+    style to .SGroup td.  Or, you could apply a style to all the entries by applying it to .SEntry.  And so on.
+Styles: Summary Styles
+    Summary - The topmost style containing the entire summary.
+    STitle - Contains the summary title, which is the part that actually says "Summary".
+    SBorder - Surrounds <STable>, since some browsers can't do table padding right.  A hack, I know.
+    STable - The actual summary table.  This class separates it from other layout tables that may appear.
+    SMarked - A class applied to rows that should have a slightly different color than the rest of the rows to make them easier to
+                    read.
+    SEntry - The entry (left) side of the table.
+    SDescription - The description (right) side of the table.
+    SIndent# - Surrounding entries and descriptions that are part of a group and need to be indented.  Actual styles will be
+                     SIndent1, SIndent2, etc.
+    SType - A placeholder for all topic-specific styles.  The actual styles will be S followed by the alphanumeric-only topic type name.
+                So the SType of a "PL/SQL Function" topic will actually be SPLSQLFunction.
+Topic: Prototype Structure
+_______________________________________________________________________________
+    Everything is enclosed in a <Prototype>.  All other styles are prefixed with a P.
+    Parameter Type First Style:
+        For prototypes such as
+        > void Function (unsigned int* a, int b = 0)
+        where the types come first.
+        (start diagram)
+        <table Prototype>
+            <td PBeforeParameters>
+                "void Function ("
+            </td PBeforeParameters>
+            <td PTypePrefix>
+                "unsigned"
+            </td PTypePrefix>
+            <td PType>
+                "int"
+            </td PType>
+            <td PParameterPrefix>
+                "*"
+            </td PParameterPrefix>
+            <td PParameter>
+                "a", "b"
+            </td PParameter>
+            <td PDefaultValuePrefix>
+                "="
+            </td PDefaultValuePrefix>
+            <td PDefaultValue>
+                "0"
+            </td PDefaultValue>
+            (repeated as necessary)
+            <td PAfterParameters>
+                ")"
+            </td PAfterParameters>
+        </table Prototype>
+        (end diagram)
+    Parameter Name First Style:
+        For prototypes such as
+        > function Function (a, b: int; c: int := 0)
+        where the parameters come first.
+        (start diagram)
+        <table Prototype>
+            <td PBeforeParameters>
+                "function Function ("
+            </td PBeforeParameters>
+            <td PParameter>
+                "a,", "b:", "c:"
+            </td PParameter>
+            <td PType>
+                "int"
+            </td PType>
+            <td PDefaultValuePrefix>
+                ":="
+            </td PDefaultValuePrefix>
+            <td PDefaultValue>
+                "0"
+            </td PDefaultValue>
+            (repeated as necessary)
+            <td PAfterParameters>
+                ")"
+            </td PAfterParameters>
+        </table Prototype>
+        (end diagram)
+    Note that any section may not exist.  For example, there will be no <PTypePrefix> cells generated if none of the parameters
+    have it.
+Styles: Prototype Styles
+    Prototype - The style encompassing the entire prototype.
+    PBeforeParameters - The part of the prototype that comes before the parameters.
+    PAfterParameters - The part of the prototype that comes after the parameters.
+    PType - The parameter type.
+    PTypePrefix - The prefix of a parameter type.
+    PParameter - The parameter name.
+    PParameterPrefix - The prefix of a parameter name.
+    PDefaultValue - The default value expression for a parameter.
+    PDefaultValuePrefix - The prefix of the default value expression.
+Topic: Link Structure
+_______________________________________________________________________________
+    All links to symbols have a type style prefixed with L.  The only exceptions are summary entries; summary descriptions use
+    them as well.
+    >   <a LType>
+    >       Link
+    >   </a LType>
+    You can use this to make links to different symbols appear in different styles.  For example, making .LClass bold will make all
+    links to classes bold, except when appearing in summary entries.  You can combine this with other styles to be even more
+    specific.  For example, you can apply a style to function links appearing in summary descriptions with .SDescription .LFunction.
+Styles: Link Styles
+    LType - A placeholder for all topic-specific styles.  The actual styles will be L followed by the alphanumeric-only topic type name.
+                So the LType of a "PL/SQL Function" topic will actually be LPLSQLFunction.
+Topic: Index Structure
+_______________________________________________________________________________
+    Everything is enclosed in an <#Index>.  Combine with <Framed> and <Unframed> to distinguish between output formats.  All
+    other index styles are prefixed with an I.
+    (start diagram)
+    <#Index>
+        <IPageTitle>
+            Page Title
+        </IPageTitle>
+        <INavigationBar>
+            A - <a href>B</a href> - C ...
+        </INavigationBar>
+        <table>
+            <IHeading>
+                Heading (A, B, etc.)
+            </IHeading>
+            <td ISymbolPrefix>
+                Prefix, if any
+            </td ISymbolPrefix>
+            <td IEntry>
+                Entry
+            </td IEntry>
+            ...
+        </table>
+    </#Index>
+    (end diagram)
+    Every index entry, including headings, are rows in a table.  The first column of a non-heading are <ISymbolPrefixes> so that
+    the non-prefix portions align correctly.  The other column are <IEntries>, of which there are multiple formats, described below.
+    (start diagram)
+    <a href ISymbol>
+        Symbol
+    </a href ISymbol>,
+    <IParent>
+        Class
+    </IParent>
+    <ISymbol>
+        Symbol
+    </ISymbol>
+    <ISubIndex>
+        <a href IParent>
+            Class
+        </a href IParent>
+        ...
+    </ISubIndex>
+    <ISymbol>
+        Symbol
+    </ISymbol>
+    <ISubIndex>
+        <IParent>
+            Class
+        </IParent>
+        <ISubIndex>
+            <a href IFile>
+                File
+            </a href IFile>
+            ...
+        </ISubIndex>
+        ...
+    </ISubIndex>
+    (end diagram)
+    Each part of the entry is surrounded by its type, which may or may not be a link.  If an entry has more than one defining class
+    or file,  they're broken out into <ISubIndexes>.
+    It's called <IParent> instead of <IClass> because class entries are <ISymbols>.  <IParents> are only used when the symbol
+    has a class.  If the symbol _is_ a class, the symbol is global.
+Styles: Index Styles
+    #Index - Parent element for the entire index.
+    IPageTitle - The page title.
+    INavigationBar - The navigation bar.
+    IHeading - An index heading, such as the letter for the group.
+    IEntry - An entry in the index.
+    ISymbolPrefix - The stripped prefix of the entry.
+    ISymbol - The entry symbol.
+    IParent - The entry parent class.  If the entry _is_ a class, this isn't defined because classes are global and don't have parent
+                  classes.  This is why it's called IParent instead of IClass; hopefully it's less confusing.
+    IFile - The file the entry is defined in.
+    ISubIndex - The surrounding block if an entry needs to be broken out into a sub-index.
+    #IFirstHeading - The ID of the first <IHeading> to appear in the file.
+    #IFirstSymbolPrefix - The ID for the first <ISymbolPrefix> to appear under an <IHeading>.
+    #ILastSymbolPrefix - The ID for the last <ISymbolPrefix> to appear under an <IHeading>.
+    #IOnlySymbolPrefix - The ID if there is only one <ISymbolPrefix> for an <IHeading>.
+Topic: Search Results Structure
+_______________________________________________________________________________
+    The search results use virtually the same structure and styles as the indexes, except that <#SearchResults> replaces
+    <#Index>, there's a new <SRResult> style, and there are a few additional <SRStatus> blocks.
+    Visibility:
+        Visibility is *very* important to making the search work correctly.  JavaScript will handle most of it, but your CSS needs to
+        abide by these rules.
+        - <SRStatus> sections are visible by default.
+        - <SRResult> sections are *not* visible by default.  They must use display: none.
+        - <ISubIndex> should be display: none when under <#SearchResults>.
+Styles: Search Results Styles
+    #SearchResults - Parent element for the entire page.
+    SRStatus - Status message.  Must be visible by default.
+    SRResult - A result.  All you need to do for this class is set it to display: none.  Nothing else should be set on it.
+Topic: Tool Tip Structure
+_______________________________________________________________________________
+    Tool tips may appear anywhere in the page, mainly because it's assumed that they will use position: absolute and
+    visibility: hidden.
+    The entire tool tip is found in a <CToolTip> style, with a CType style inside it.  CTypes are normally outside their elements, but
+    that would cause it to be partially visible in this case.  We need <CToolTip> to be the outermost style so its visibility and
+    position can be manipulated in JavaScript.
+    Inside there's a <CPrototype> and/or the description text.  The description text has no special surrounding tags.
+    >   <CToolTip>
+    >
+    >       <CPrototype>
+    >           Prototype
+    >       </CPrototype>
+    >
+    >       Summary text
+    >
+    >   </CToolTip>
+Styles: Tool Tip Styles
+    CToolTip - Surrounds the entire tool tip.  This *must* have position: absolute and visibility: hidden for the tool tip mechanism
+                    to work.
+    See also <CPrototype>.
+Styles: Miscellaneous Styles
+    blockquote - This HTML element should surround anything that needs to be scrolled if it's too wide, like prototypes and text
+                       diagrams.  It's not a style because this makes it much easier to do the JavaScript necessary to get this working
+                       in IE.
+Group: History
+Topic: Revisions
+_______________________________________________________________________________
+    How the page structure has changed throughout the various releases.
+    1.4:
+        - Replaced UnframedPage with <ContentPage> and <IndexPage>.
+        - Added <#Menu>, <#Content>, <#Footer>, and <#Index>.  They were previously shown in the diagrams as classes but did
+          not actually appear in the generated output.
+        - Removed MenuSection, ContentSection, and IndexSection.  Use things like ".ContentPage #Menu" instead.
+        - Removed tables from the unframed <Page Structure>.  Use CSS to position the elements instead.
+        - <#MainTopic> is applied to <CTopic> instead of <CType>.
+        - IE4, IE5, Opera5, Opera6, Netscape, and Netscape4 browser styles have been removed.  <IE7>, <Opera8>,
+          and <Opera9> have been added.  Gecko has been replaced by <Firefox>, <Firefox1>, <Firefox15>, and <Firefox2>.
+          KHTML has been replaced by <Safari>, <Safari2>, <Safari3>, and <Konqueror>.
+        - Removed redundant CParagraph, CCode, and CBulletList classes.  Use <CBody> with p, pre, and ul instead.
+        - Added <CImageCaption> and <CImageLink>.
+        - Added <#MSearchPanel>, <#MSearchResultsWindow>, and all related styles.
+        - Added <Search Results Structure>, <Search Results Styles>, and <FramedSearchResultsPage>.
+        - Removed SEntrySize.  Apply the width to <SEntry> and <SDescription> instead.
+        - <SType>, <SEntry>, and <SIndent#> were moved from the td and divs into the tr.
+        - Removed HB style.  Now using wbr tag.
+    1.33:
+        - Added <PDefaultValuePrefix>.
+    1.32:
+        - <blockquotes> now surround elements that should scroll if they're too wide for the page.
+    1.3:
+        - Removed CPrototype.  See the replacement <Prototype Structure> and <Prototype Styles>.
+        - Removed SInGroup, SInClass, and SInSection in favor of more general <SIndent#>.
+        - <CTypes>, <STypes>, and <LTypes> are now completely determined by <Topics.txt> configuration files.
+        - <CTypes>, <STypes>, and <LTypes> no longer have separate list types.  A CFunctionList is now just a CFunction.
+        - Indexes are now done with tables.
+        - ISection was removed.
+        - <IEntries> are only used for the entry cell, not for each entry in an <ISubIndex>.
+        - Added <ISymbolPrefix>, related IDs, and <#IFirstHeading>.
+        - Merged <CType> and <CTopic> into the same element.  Must now be styled with .CType.CTopic (no space) while all
+          sub-elements will still be .CType .CElement (with space.)
+    1.21:
+        - Added <TOPIC_PROPERTY> and TOPIC_PROPERTY_LIST styles, so they get corresponding <CTypes>, <STypes>, and
+          <LTypes>.
+    1.2:
+        - Added <Class Hierarchy Styles> since 1.2 added class hierarchies.
+    1.16:
+        - Changed the first topic from having a CMain type to having a normal type with a <#MainTopic> ID.
+    1.1:
+        - Added <Tool Tip Styles>.
+        - Renamed HiddenBreak to <HB>.
+        - Added <TOPIC_CONSTANT>, TOPIC_CONSTANT_LIST, <TOPIC_TYPE>, and TOPIC_TYPE_LIST types, so they get
+          corresponding <CTypes>, <STypes>, and <LTypes>.
+    1.0:
+        - The <CType> tags now appear arround the <CTopic> tags instead of vice versa.
+        - Added a <CBody> tag to surround non-<CTitle> elements.
+        - <SMarked> now appears in tr's instead of td's, where it belonged in the first place.
+    0.95:
+        - Added <Browser Styles>.
+        - Redid <Page Structure>, replacing generic styles like Menu with page type styles like UnframedPage/MenuSection and
+          FramedMenuPage.
+    0.91:
+        - Added <LURL> and <LEMail> link styles, since 0.91 added URL and e-mail links.
+        - Added <ISection> style, which is better than <IHeading> floating on its own.
+    0.9:
+        - Added <Index Styles>, since 0.9 added indexes.