/usr/share/doc/rest2web/html/restindex.html is in rest2web-doc 0.5.2~alpha+svn-r248-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>The restindex</title>
<link rel="stylesheet" href="stylesheets/rest2web.css" type="text/css" />
<link rel="stylesheet" href="stylesheets/voidspace_docutils2.css" type="text/css" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="description" content="rest2web - build websites with Python and docutils." />
<meta name="author" content="Michael Foord" />
<meta name="copyright" content="© 2003-2006 Michael Foord, subject to BSD License" />
<meta name="keywords" content="rest2web - build websites with Python and docutils,
rest, restructured text, text, website, internet, web, net, web builder, site,
site builder, docutils, i18n, internationalization, templates, templating,
python, " />
</head>
<body style="background: url(images/logos/img_background.gif) top center repeat-y;">
<div id="wrap">
<div id="header-section">
<a href="http://www.voidspace.org.uk/python/index.shtml" title="Voidspace"><img src="images/logos/header760.gif" alt="Voidspace"/></a>
<p align="center" class="headertitle"><span style="font-size:130%">rest2web:</span> Building Websites Across the Known Universe</p>
</div>
<div id="header">
<ul>
<li><a href="index.html">rest2web</a></li>
<li>></li>
<li>restindex</li>
</ul>
</div>
<table>
<tr>
<td><img src="images/logos/1.gif" width="1" height="1" alt="" /></td>
<!-- main content cell first, with rowspan=2 -->
<td valign="top" align="left" rowspan="2">
<div id="middle-column">
<a name="startcontent" id="startcontent"></a>
<div id="gallery">
<div class="document" id="the-restindex">
<h1 class="title">The restindex</h1>
<h2 class="subtitle" id="controlling-rest2web-through-the-restindex">Controlling rest2web Through the restindex</h2>
<div class="contents topic" id="id1">
<p class="topic-title first">The restindex</p>
<ul class="simple">
<li><a class="reference internal" href="#introduction" id="id9">Introduction</a></li>
<li><a class="reference internal" href="#the-master-restindex" id="id10">The Master restindex</a><ul>
<li><a class="reference internal" href="#restindex-and-uservalues-in-a-rest-comment" id="id11">Restindex and Uservalues in a ReST Comment</a></li>
</ul>
</li>
<li><a class="reference internal" href="#the-keywords" id="id12">The Keywords</a></li>
<li><a class="reference internal" href="#building-the-index" id="id13">Building the Index</a></li>
<li><a class="reference internal" href="#handling-paths" id="id14">Handling Paths</a></li>
<li><a class="reference internal" href="#restindex-txt" id="id15">restindex.txt</a></li>
<li><a class="reference internal" href="#footnotes" id="id16">Footnotes</a></li>
</ul>
</div>
<div class="section" id="introduction">
<h1><a class="toc-backref" href="#id9">Introduction</a></h1>
<p>reST format alone doesn't tell us everything we need in order to build the pages. It will generate a title from the top headline - but it won't tell us things like which template file to use, what text to use as a description of the page in the index, etc. For this I've added something called a <em>restindex</em>, which is a simple list of keywords and values to go at the start of every page you want rest2web to render for you.</p>
<p>There is another set of values you can add at the start of your files. These are <em>uservalues</em> and they allow you to add your own values into the namespace when templating. See the <a class="reference external" href="reference/uservalues.html">uservalues</a> page for the details.</p>
</div>
<div class="section" id="the-master-restindex">
<h1><a class="toc-backref" href="#id10">The Master restindex</a></h1>
<p>This shows every option in the <strong>restindex</strong> - with an example value. In practise you only need to ever <em>use</em> values that are different from the defaults. For a good example see the <a class="reference external" href="tutorial.html">tutorial</a>.</p>
<pre class="literal-block">
restindex
# this is a comment
include: yes
format: html
file-extension: shtml
template: template.txt
template-encoding: utf8
index-file: index.txt
section: section name
link-title: This is the text to use in the link
page-title: We *usually* only need a title for HTML
page-description:
this is a description
It can go across several line
And even be indented a bit.
It will be interpreted as *reST*.
/description
crumb: Short Name
build: yes
initialheaderlevel: 1
tags: keyword1, keyword2, keyword3
file: filename1
file: filename2
file: filename3
target: thisfile.html
encoding: utf8
output-encoding: utf8
sectionlist: section-name1, section-name2, section-name3
section-pages: section-name1, page1, page2, page3
section-title: section-name1, title
section-description: section-name1
This is also a description.
/description
section-pages: , page1, page2, page3
section-title: , Default Section Title
# note the leading ',' to specify the default section
section-description:
Default section description.
/description
/restindex
</pre>
<p>Every <strong>rest2web</strong> source file must start with a 'restindex' chunk. This tells rest2web how to render the page. If a text file doesn't start with a restindex, it won't be processed.</p>
<p>To qualify as a restindex - the first non-empty line of the file must be <strong>restindex</strong>. Subsequent lines that start with a '#' are comments.</p>
<p>Each line is in the format - <tt class="docutils literal"><span class="pre">keyword:</span> <span class="pre">value</span></tt>, except for multiline values. Currently this means only the <tt class="docutils literal"><span class="pre">description:</span></tt> type keywords.</p>
<p>If a keyword is missing, or the value is blank, then the default will be used.</p>
<p>The restindex is used for two purposes.</p>
<ol class="arabic simple">
<li>For setting values for individual pages. In this case the index is at the start of the page that is being processed. Only certain values are relevant.</li>
<li>In the index page, the restindex can set options for a whole directory.</li>
</ol>
<div class="section" id="restindex-and-uservalues-in-a-rest-comment">
<h2><a class="toc-backref" href="#id11">Restindex and Uservalues in a ReST Comment</a></h2>
<p>Since rest2web 0.5.0, you can put the restindex (and <a class="reference external" href="reference/uservalues.html">uservalues</a>) inside a ReST comment.</p>
<p>That means that your source documents can contain a restindex <em>and</em> still be valid ReStructured Text documents :</p>
<pre class="literal-block">
..
This is a ReST Comment
This page is copyright by me, 1941
restindex
format: html
page-title: This is a Phantasmagorical Page
/restindex
uservalues
site_title: My Great Site
copyright: A Copyright Message
/uservalues
</pre>
<p>Due to technical limitations (read laziness), the restindex and the uservalues <em>must</em> be the last part of the comment. <img src="images/smilies/smile.gif" alt="Smile" /> </p>
</div>
</div>
<div class="section" id="the-keywords">
<h1><a class="toc-backref" href="#id12">The Keywords</a></h1>
<p>The keywords are as follows. <a class="footnote-reference" href="#id5" id="id2">[1]</a> :</p>
<ol class="arabic">
<li><p class="first"><strong>include</strong> - include this file in the index ? Should be yes or no. If no, the page is still generated from the template - but not included in the index page.</p>
<blockquote>
<p>This value applies to both normal files and index files.</p>
<p>Default value is yes.</p>
</blockquote>
</li>
<li><p class="first"><strong>format:</strong> - so far this can either be 'rest' or 'html'. It would be theoretically possible to allow other markup formats like 'sextile', or 'textile'. This is the markup format of the page. If it is 'rest' then docutils is used to generate the html (and usually the page title). The page contents are processed for embedded code, along with the templates (this allows you to use the templating in your indexes, using the <tt class="docutils literal"><span class="pre">..</span> <span class="pre">raw::</span></tt> directive you can even do this in reST documents).</p>
<blockquote>
<p>The default value for this is 'rest'.</p>
</blockquote>
</li>
<li><p class="first"><strong>file-extension:</strong> - what file extension to use for this file. You don't need to specify the '.'. Normal values would be <em>html</em>, <em>htm</em>, <em>shtml</em>, or <em>shtm</em>. In 'index.txt' it can apply to a whole directory.</p>
<blockquote>
<p>The default value for this is 'html'. (Grr... I'd prefer it to be 'shtml', but there you go).</p>
</blockquote>
</li>
<li><p class="first"><strong>template:</strong> - this is the file to use as the template file. Relative locations will be relative to this directory of course. The template is processed for each page - and the body inserted, title created, dynamic elements are processed etc. See note on <a class="reference internal" href="#handling-paths">Handling Paths</a>.</p>
<blockquote>
<p>In an 'index.txt' this can specify the template file for the whole directory (and directories below it as well).</p>
<p>The default value for this is 'template.txt'. If none is specified in 'index.txt' and 'template.txt' doesn't exist, then 'template.txt' in the directory above will be tried. (moving up directories until one is found)</p>
</blockquote>
</li>
<li><p class="first"><strong>template-encoding:</strong> - This is the encoding of the specified template file. If an encoding isn't supplied then it will be guessed.</p>
</li>
<li><p class="first"><strong>index-file:</strong> - this specifies which page to use as the index file. (This file is used as the source to <em>build</em> the index file and as the target to link to in the index for the next level up). If 'index.txt' has this value, then all other values will be read from the restindex of the specified file. See note on <a class="reference internal" href="#handling-paths">Handling Paths</a>.</p>
<blockquote>
<p>It only has any meaning in the 'index.txt'. It can be used to specify an alternative page as being the main index page for this directory. The index page in the next level up will link to the target of the specified file.</p>
<p>Default value is 'index.txt'.</p>
</blockquote>
</li>
<li><p class="first"><strong>section:</strong> - This specifies what section this page should appear in, in the relevant index page.</p>
<blockquote>
<p>For 'index.txt', the relevant index page is the next level up. The section is the section this index page will appear in, in <em>the index above</em> ! Got it ? (So for the 'root index' this value will never be used).</p>
<p>The default value is for a page to be in the <tt class="docutils literal"><span class="pre">None</span></tt> section.</p>
</blockquote>
</li>
<li><p class="first"><strong>link-title:</strong> - this is the text used in the <em>link</em> to this page from the index page.</p>
<blockquote>
<p>In an 'index.txt', this will be the link to the index from the next level up.</p>
<p>The page title will be uased as the default value, if none is specified.</p>
</blockquote>
</li>
<li><p class="first"><strong>page-title:</strong> - this is the page title. You should specify the <tt class="docutils literal"><span class="pre">page-title</span></tt> for index pages <em>and</em> for html pages. If the page body is in rest, this value overrides any autogenerated value.</p>
<blockquote>
<p>In an 'index.txt' this has the same meaning as in ordinary pages.</p>
<p>There is no default value for this <em>FIXME: could use the filename ?</em></p>
</blockquote>
</li>
<li><p class="first"><strong>page-description:</strong> - This marks the start of the description, which actually starts on the next line. The description is the text used along with the link to this page. Currently description format is 'rest' only. If you want to include HTML you can always use the 'raw' directive ! The page description can go over several lines - it terminates with '/description' on a newline. Uniform indentation (spaces) that occurs on <em>every</em> line, will be removed before processing.</p>
<blockquote>
<p>In an 'index.txt', this is the description used in the next level up.</p>
<p>The default value is '' (no description).</p>
</blockquote>
</li>
<li><p class="first"><strong>crumb:</strong> - this is a short name for the page. It will be used for generating the 'breadcrumb' navigation links.</p>
<blockquote>
<p>For index pages, this name will form a link back to the page.</p>
<p>The default value is to use the page title <a class="footnote-reference" href="#id6" id="id3">[2]</a>. (Which will usually be too long).</p>
<p>For index pages (or if no page title is available), the filename is used as
the default crumb instead.</p>
</blockquote>
</li>
<li><p class="first"><strong>target:</strong> - This specifies the target file. This will be the filename of the 'built' file, and the filename linked to in the index. If this keyword is used, the 'file-extension' keyword is ignored. (So a file extension must be included in the value for this keyword). The target can be a relative path to the file. See note on <a class="reference internal" href="#handling-paths">Handling Paths</a>.</p>
<blockquote>
<p>This value applies equally to 'index.txt' as other files.</p>
<p>The default value is the filename, minus '.txt', plus the value of the 'file-extension' keyword.</p>
</blockquote>
</li>
<li><p class="first"><strong>build:</strong> - This should be 'yes' or 'no'. This allows you to specify that a file is not to be built, but should be included in the index. This allows you to include prebuilt files in the index. In conjunction with the target keyword, it can be used to link to files in other locations.</p>
<blockquote>
<p>This value applies equally to 'index.txt' as other files.</p>
<p>The default value is 'yes'.</p>
</blockquote>
</li>
<li><p class="first"><strong>initialheaderlevel</strong> - An integer value. If your page format is ReST, then
this value is passed to docutils when the page is built. This specifies the
starting level (<tt class="docutils literal"><span class="pre">h1</span></tt>, <tt class="docutils literal"><span class="pre">h2</span></tt> etc) for headers in the page.</p>
<blockquote>
<p>This value applies equally to 'index.txt' as other files.</p>
<p>The default value is '1'.</p>
</blockquote>
</li>
<li><p class="first"><strong>encoding</strong> - this is the encoding of the file. The value must be a recognised python standard encoding.</p>
<blockquote>
<p>This value applies equally to an index file.</p>
<p>The default value is to ignore encoding and leave the 'subtools' (docutils) to guess encoding.</p>
</blockquote>
</li>
<li><p class="first"><strong>output-encoding</strong> - this is the encoding the page is written out as. The <tt class="docutils literal"><span class="pre">output-encoding</span></tt> ought to match the encoding used for the template ! The value must be a recognised python standard encoding, or one of two special values. <strong>unicode</strong> means don't encode the page - but present it to the template as a unicode string. <strong>None</strong> means use the encoding the page was originally encoded with.</p>
<blockquote>
<p>This value applies equally to an index file. Setting it in an index file will set this value as the default for the whole directory <em>and</em> any subdirectories. (Unless an alternative is explicitly specified).</p>
<p>The default value is 'None', which encodes the page using the encoding the page was originally encoded with. If a value is specified in any of the index pages above this page, then that will be used <em>instead</em> of the default.</p>
<div class="warning">
<p class="first admonition-title">Warning</p>
<p>Not including this keyword <em>is not</em> the same as including the keyword with no value.</p>
<p>Not including it will cause the default for this directory to be used.</p>
<p class="last">Including it, but leaving it empty is the same as specifying <tt class="docutils literal"><span class="pre">None</span></tt>.</p>
</div>
</blockquote>
</li>
<li><p class="first"><strong>sectionlist:</strong> - This is a list of different sections for an index page. Links to pages in this directory appear in these different sections. The names should be unique as they will be used as "id's" to reference the section in the index.</p>
<blockquote>
<p>This value <em>only</em> has meaning in an index page.</p>
<p>The default value is to have a single section referenced as 'default' if it isn't named.</p>
</blockquote>
</li>
<li><p class="first"><strong>section-title:</strong> - This is how you specify the title for each section. The first value is the nameof the section, followed by the title to be used for the section. This can be made into a link back up to a section table at the top of the index page. You can have multiple section titles, one per section.</p>
<blockquote>
<p>This value <em>only</em> has meaning in an index page.</p>
<p>The default value is to use the section name as the title. (In 'Title-Case').</p>
</blockquote>
</li>
<li><p class="first"><strong>section-pages</strong> - This specifies the <em>order</em> that pages appear in the section, for example in sidebars and in the <tt class="docutils literal"><span class="pre">sections</span></tt> data structure (used by the <tt class="docutils literal"><span class="pre">print_details</span></tt> <a class="reference external" href="functions.html">standard function</a>).</p>
<p>The first value is the section name (or a leading comma for the default section). You use the filename (minus the '.txt') to specify a page. You don't have to list all the pages - but including a page that doesn't exist will raise an error. The pages you specify will appear in that order, followed by the rest of the pages in an arbitrary order.</p>
<p>If you want to specify a subdirectory then use the directory name followed by 'index'. For example - <tt class="docutils literal"><span class="pre">subdirectory/index</span></tt>.</p>
<blockquote>
<p>This value <em>only</em> has meaning in an index page.</p>
<p>The default value is for pages to be in an arbitrary order.</p>
</blockquote>
</li>
<li><p class="first"><strong>section-description:</strong> - This is a description used for this section. It will appear above the links to the pages in the section. Other details are the same as the <em>page-description</em>.</p>
<blockquote>
<p>This value <em>only</em> has meaning in an index page.</p>
<p>The default value is '' (no description).</p>
</blockquote>
</li>
<li><p class="first"><strong>tags</strong> - This option takes a list of keywords that applies to the page. You can then use this list in your template and pages. (E.g. for the <tt class="docutils literal"><span class="pre">meta</span> <span class="pre">type="keywords"</span></tt> data).</p>
<blockquote>
<p>This value applies equally to an index file.</p>
<p>The default value is for it to be an empty list.</p>
</blockquote>
</li>
<li><p class="first"><strong>file</strong> - This option specifies an additonal file to copy from the source directory to the same directory as the target file. You can use this keyword multiple times in the restindex.</p>
<blockquote>
<p>This value applies equally to an index file.</p>
<p>The default is for no additional files to be copied.</p>
</blockquote>
</li>
<li><p class="first"><strong>plugins</strong> - A list of plugins that should be applied to the page. See the <a class="reference external" href="reference/plugins.html">plugins</a> page for more details.</p>
</li>
</ol>
</div>
<div class="section" id="building-the-index">
<h1><a class="toc-backref" href="#id13">Building the Index</a></h1>
<p>The contents of a directory will only be built if it has an 'index.txt' file. This doesn't mean that the main file needs to be called 'index.html' or similar. There are two ways of changing this.</p>
<p>First - the 'index.txt' file can contain the content, but have a <em>target</em> value set. This sets the filename that the built file will be saved as.</p>
<p>Alternatively, 'index.txt' can have an <em>index-file</em> value. This will specify an alternative file that is to be used as the index page. In this case <em>all</em> the other values in 'index.txt' will be ignored and the values from the specified file will be used. This means the restindex will be very short :</p>
<pre class="literal-block">
restindex
index-file: anotherfile.txt
/restindex
</pre>
</div>
<div class="section" id="handling-paths">
<h1><a class="toc-backref" href="#id14">Handling Paths</a></h1>
<p>Windows, Linux, and the Mac, all handle paths differently. rest2web uses the file structure on disk to represent the structure of the website <a class="footnote-reference" href="#id7" id="id4">[3]</a>. This means we are using the same relative file paths to represent the file path on the local computer (on which rest2web is running) and the links within the website. Because the different OS's represent filepaths differently - we have a conflict between specifing file paths and urls.</p>
<p>A few of the restindex keywords expect a path. Specifically <tt class="docutils literal"><span class="pre">template</span></tt>, <tt class="docutils literal"><span class="pre">index-file</span></tt>, and <tt class="docutils literal"><span class="pre">target</span></tt>. <tt class="docutils literal"><span class="pre">template</span></tt> is always a filepath - because it specifies a file which is built into other pages. This means it can be specified as an absolute location - or using a native, relative file path.</p>
<p>For the other two values, <tt class="docutils literal"><span class="pre">index-file</span></tt> and <tt class="docutils literal"><span class="pre">target</span></tt>, rest2web expects the path to be a <em>relative path, that follows the Unix path conventions</em>. This greatly simplifies our path handling routines.</p>
</div>
<div class="section" id="restindex-txt">
<h1><a class="toc-backref" href="#id15">restindex.txt</a></h1>
<p>You may be using rest2web to only generate some of the pages in your website. In this case it can be useful to provide a restindex for pages that rest2web <em>isn't</em> building. This enables rest2web to include them in indexes etc. You can easily doing this by setting the <tt class="docutils literal"><span class="pre">build:</span> <span class="pre">No</span></tt> option in the restindex. If you have several pages like this in a directory it can be a nuisance to maintain all the files for them. rest2web allows you to put several restindexes in a file called 'restindex.txt'. See the <a class="reference external" href="special_files.html">Special Files</a> page for more details.</p>
<p>As a summary - every restindex in 'restindex.txt' will be assumed to have <tt class="docutils literal"><span class="pre">build:</span> <span class="pre">No</span></tt> set, but you must specify a target - or all the ouput files will be named 'restindex.html' <img src="images/smilies/badgrin.gif" alt="Bad Grin" /> </p>
</div>
<hr class="docutils" />
<div class="section" id="footnotes">
<h1><a class="toc-backref" href="#id16">Footnotes</a></h1>
<table class="docutils footnote" frame="void" id="id5" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>If you see <strong>#</strong> by every entry in this list (in the output html) rather than a numbered list, you need to update your version of docutils. (0.3.8 or more recent required)</td></tr>
</tbody>
</table>
<table class="docutils footnote" frame="void" id="id6" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id3">[2]</a></td><td>For index pages we may not pick up on the default of using the title - this is because we don't generate the page when reading the defaults. Index pages <strong>need</strong> crumbs !</td></tr>
</tbody>
</table>
<table class="docutils footnote" frame="void" id="id7" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id4">[3]</a></td><td>Although you can override this using the <em>'target'</em> keyword.</td></tr>
</tbody>
</table>
</div>
</div>
</div>
<div id="end">
<p><a href="#startcontent">Return to Top</a><br />
<small>Part of the <a href="http://www.voidspace.org.uk/python/rest2web/">rest2web Docs</a></small><br />
<small>Page last modified <strong>Thu Oct 12 21:49:14 2006</strong>.</small>
</p>
</div>
</div></td>
</tr>
<tr>
<td valign="top" align="left" width="25%">
<div id="left-column">
<div id="sidie">
<ul>
<li class="left-navheader-first">
<a href="index.html" class="left-navheader">Index Page</a>
</li>
<li class="left-navheader">Pages</li>
<li><a href="introduction.html">Introduction</a></li>
<li><a href="quickstart.html">Quickstart</a></li>
<li><a href="config_file.html">Config File</a></li>
<li><a href="tutorial.html">Tutorial</a></li>
<li><a href="command_line.html">Command Line</a></li>
<li><a href="force_mode.html">Force Mode</a></li>
<li><a href="templating.html">Templates</a></li>
<li><a href="restindex.html">restindex</a></li>
<li><a href="functions.html">Functions</a></li>
<li><a href="macros.html">Macros</a></li>
<li><a href="special_files.html">Special Files</a></li>
<li class="left-navheader">Sub Sections</li>
<li><a href="reference/index.html">Reference</a></li>
<li><a href="test_site/index.html">Test Site</a></li>
<li><a href="translation/index.html">Translation</a></li>
<li><a href="gallery_test/index.html">Gallery</a></li>
</ul>
</div>
<p class="sidieimg">
<a href="http://www.python.org">
<img src="images/logos/new_python.gif" width="88"
height="103" border="0" alt="Powered by Python" />
</a>
</p>
<p class="sidieimg">
<a href="http://sourceforge.net/donate/index.php?group_id=138579">
<img src="http://images.sourceforge.net/images/project-support.jpg" width="100"
height="32" border="0" alt="Support This Project" />
</a>
</p>
<p class="sidieimg">
<a href="http://www.voidspace.org.uk/python/rest2web/"><img
src="images/logos/rest2web140x62.gif" width="142" height="62"
alt="Site Built with rest2web" /></a><br />
</p>
</div>
</td>
</tr>
</table>
<hr />
<p class="sidieimg">
<a href="http://www.voidspace.org.uk/python/rest2web/"><img src="images/logos/rest2web200x80.gif" width="200" height="80" alt="Site Built with rest2web" /></a>
<a href="http://sourceforge.net"><img src="http://sourceforge.net/sflogo.php?group_id=138579&type=5" width="210" height="62" alt="SourceForge.net Logo" /></a>
<a href="http://www.opensource.org"><img src="images/logos/osi-certified-120x100.gif" width="120" height="100" alt="Certified Open Source" border="1" /></a>
</p>
<p class="sidieimg">
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-203625-1";
urchinTracker();
</script>
</p>
<p class="sidieimg">
<a href="http://www.voidspace.org.uk/python/index.shtml"><img
src="images/logos/pythonbanner.gif" width="468" height="60"
alt="Python on Voidspace" /></a>
</p>
<div id="footer">
Copyright © Voidspace<br />Design by <a href="http://www.fuchsiashockz.co.uk">Fuchsiashockz</a> | <a href="http://validator.w3.org/check?uri=referer" title="Validate code as W3C XHTML 1.1 Strict Compliant">W3C XHTML 1.1</a> | <a href="http://jigsaw.w3.org/css-validator/check?uri=referer" title="Validate Style Sheet as W3C CSS 2.0 Compliant">W3C CSS 2.0</a>
</div>
</div>
</body>
</html>
|