/[gentoo]/xml/htdocs/proj/en/glep/glep-0002.html
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0002.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.2 Revision 1.9
1<?xml version="1.0" encoding="utf-8" ?> 1<?xml version="1.0" encoding="utf-8" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> 3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4<!-- 4
5This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new
6PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
7to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE!
8-->
9<head> 5<head>
10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
11 <meta name="generator" content="Docutils 0.2.8: http://docutils.sourceforge.net/" /> 7 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
12 <title>GLEP 2 -- Sample ReStructuredText GLEP Template</title> 8 <title>GLEP 2 -- Sample ReStructuredText GLEP Template</title>
13 <link rel="stylesheet" href="tools/glep.css" type="text/css" /> 9 <link rel="stylesheet" href="tools/glep.css" type="text/css" />
14</head> 10</head>
15<body bgcolor="white"> 11<body bgcolor="white">
16<table class="navigation" cellpadding="0" cellspacing="0" 12<table class="navigation" cellpadding="0" cellspacing="0"
22<td class="textlinks" align="left"> 18<td class="textlinks" align="left">
23[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] 19[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
24[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] 20[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
25[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0002.txt">GLEP Source</a></b>] 21[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0002.txt">GLEP Source</a></b>]
26</td></tr></table> 22</td></tr></table>
27<div class="document">
28<table class="rfc2822 field-list" frame="void" rules="none"> 23<table class="rfc2822 docutils field-list" frame="void" rules="none">
29<col class="field-name" /> 24<col class="field-name" />
30<col class="field-body" /> 25<col class="field-body" />
31<tbody valign="top"> 26<tbody valign="top">
32<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">2</td> 27<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">2</td>
33</tr> 28</tr>
34<tr class="field"><th class="field-name">Title:</th><td class="field-body">Sample ReStructuredText GLEP Template</td> 29<tr class="field"><th class="field-name">Title:</th><td class="field-body">Sample ReStructuredText GLEP Template</td>
35</tr> 30</tr>
36<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</td> 31<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.4</td>
37</tr> 32</tr>
38<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0002.txt">2003/06/02 17:37:47</a></td> 33<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0002.txt?cvsroot=gentoo">2003/07/19 12:09:20</a></td>
39</tr> 34</tr>
40<tr class="field"><th class="field-name">Author:</th><td class="field-body">Grant Goodyear &lt;g2boojum&#32;&#97;t&#32;gentoo.org&gt;,</td> 35<tr class="field"><th class="field-name">Author:</th><td class="field-body">Grant Goodyear &lt;g2boojum&#32;&#97;t&#32;gentoo.org&gt;,</td>
41</tr> 36</tr>
42<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td> 37<tr class="field"><th class="field-name">Status:</th><td class="field-body">Active</td>
43</tr> 38</tr>
44<tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td> 39<tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td>
45</tr> 40</tr>
46<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td> 41<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td>
47</tr> 42</tr>
48<tr class="field"><th class="field-name">Created:</th><td class="field-body">31 May 2003</td> 43<tr class="field"><th class="field-name">Created:</th><td class="field-body">31 May 2003</td>
49</tr> 44</tr>
50<tr class="field"><th class="field-name">Post-History:</th><td class="field-body"></td> 45<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">2-Jun-2003</td>
51</tr> 46</tr>
52</tbody> 47</tbody>
53</table> 48</table>
54<hr /> 49<hr />
55<div class="contents topic" id="contents"> 50<div class="contents topic">
56<p class="topic-title"><a name="contents">Contents</a></p> 51<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
57<ul class="simple"> 52<ul class="simple">
58<li><a class="reference" href="#credits" id="id23" name="id23">Credits</a></li> 53<li><a class="reference" href="#credits" id="id23" name="id23">Credits</a></li>
59<li><a class="reference" href="#abstract" id="id24" name="id24">Abstract</a></li> 54<li><a class="reference" href="#abstract" id="id24" name="id24">Abstract</a></li>
60<li><a class="reference" href="#motivation" id="id25" name="id25">Motivation</a></li> 55<li><a class="reference" href="#motivation" id="id25" name="id25">Motivation</a></li>
61<li><a class="reference" href="#rationale" id="id26" name="id26">Rationale</a></li> 56<li><a class="reference" href="#rationale" id="id26" name="id26">Rationale</a></li>
81<li><a class="reference" href="#resources" id="id44" name="id44">Resources</a></li> 76<li><a class="reference" href="#resources" id="id44" name="id44">Resources</a></li>
82<li><a class="reference" href="#references" id="id45" name="id45">References</a></li> 77<li><a class="reference" href="#references" id="id45" name="id45">References</a></li>
83<li><a class="reference" href="#copyright" id="id46" name="id46">Copyright</a></li> 78<li><a class="reference" href="#copyright" id="id46" name="id46">Copyright</a></li>
84</ul> 79</ul>
85</div> 80</div>
86<div class="section" id="credits"> 81<div class="section">
87<h1><a class="toc-backref" href="#id23" name="credits">Credits</a></h1> 82<h1><a class="toc-backref" href="#id23" id="credits" name="credits">Credits</a></h1>
88<p>The text of this GLEP was, to a significant extent, stolen from Python's 83<p>The text of this GLEP was, to a significant extent, stolen from Python's
89<a class="footnote-reference" href="#python" id="id1" name="id1">[1]</a> PEP-0012 <a class="footnote-reference" href="#pep12" id="id2" name="id2">[2]</a> by David Goodger and Barry A. Warsaw.</p> 84<a class="footnote-reference" href="#python" id="id1" name="id1">[1]</a> PEP-0012 <a class="footnote-reference" href="#pep12" id="id2" name="id2">[2]</a> by David Goodger and Barry A. Warsaw.</p>
90</div> 85</div>
91<div class="section" id="abstract"> 86<div class="section">
92<h1><a class="toc-backref" href="#id24" name="abstract">Abstract</a></h1> 87<h1><a class="toc-backref" href="#id24" id="abstract" name="abstract">Abstract</a></h1>
93<p>This GLEP provides a boilerplate or sample template for creating your own 88<p>This GLEP provides a boilerplate or sample template for creating your own
94reStructuredText GLEPs. In conjunction with the content guidelines in GLEP 1 89reStructuredText GLEPs. In conjunction with the content guidelines in GLEP 1
95<a class="footnote-reference" href="#glep1" id="id3" name="id3">[3]</a>, this should make it easy for you to conform your own GLEPs to the 90<a class="footnote-reference" href="#glep1" id="id3" name="id3">[3]</a>, this should make it easy for you to conform your own GLEPs to the
96format outlined below.</p> 91format outlined below.</p>
97<p>Note: if you are reading this GLEP via the web, you should first grab the text 92<p>Note: if you are reading this GLEP via the web, you should first grab the text
98(reStructuredText) source of this GLEP in order to complete the steps below. 93(reStructuredText) source of this GLEP in order to complete the steps below.
99<strong>DO NOT USE THE HTML FILE AS YOUR TEMPLATE!</strong></p> 94<strong>DO NOT USE THE HTML FILE AS YOUR TEMPLATE!</strong></p>
100<p>To get the source of this (or any) GLEP, look at the top of the HTML page and 95<p>To get the source of this (or any) GLEP, look at the top of the HTML page and
101click on the link titled &quot;GLEP Source&quot;.</p> 96click on the link titled &quot;GLEP Source&quot;.</p>
102</div> 97</div>
103<div class="section" id="motivation"> 98<div class="section">
104<h1><a class="toc-backref" href="#id25" name="motivation">Motivation</a></h1> 99<h1><a class="toc-backref" href="#id25" id="motivation" name="motivation">Motivation</a></h1>
105<p>Provide adequate motivation here. In this particular case, we need to provide 100<p>Provide adequate motivation here. In this particular case, we need to provide
106people with the information necessary to submit GLEPs in the proper form.</p> 101people with the information necessary to submit GLEPs in the proper form.</p>
107</div> 102</div>
108<div class="section" id="rationale"> 103<div class="section">
109<h1><a class="toc-backref" href="#id26" name="rationale">Rationale</a></h1> 104<h1><a class="toc-backref" href="#id26" id="rationale" name="rationale">Rationale</a></h1>
110<p>GLEP submissions come in a wide variety of forms, not all adhering to the 105<p>GLEP submissions come in a wide variety of forms, not all adhering to the
111format guidelines set forth below. Use this template, in conjunction with the 106format guidelines set forth below. Use this template, in conjunction with the
112format guidelines below, to ensure that your GLEP submission won't get 107format guidelines below, to ensure that your GLEP submission won't get
113automatically rejected because of form.</p> 108automatically rejected because of form.</p>
114<p>ReStructuredText is used to allow GLEP authors more functionality and 109<p>ReStructuredText is used to allow GLEP authors more functionality and
115expressivity, while maintaining easy readability in the source text. The 110expressivity, while maintaining easy readability in the source text. The
116processed HTML form makes the functionality accessible to readers: live 111processed HTML form makes the functionality accessible to readers: live
117hyperlinks, styled text, tables, images, and automatic tables of contents, 112hyperlinks, styled text, tables, images, and automatic tables of contents,
118among other advantages.</p> 113among other advantages.</p>
119</div> 114</div>
120<div class="section" id="backwards-compatibility"> 115<div class="section">
121<h1><a class="toc-backref" href="#id27" name="backwards-compatibility">Backwards Compatibility</a></h1> 116<h1><a class="toc-backref" href="#id27" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
122<p>Not a problem for this GLEP. This section should be included <em>even</em> when it 117<p>Not a problem for this GLEP. This section should be included <em>even</em> when it
123is only to state that there are no backwards compatibility issues.</p> 118is only to state that there are no backwards compatibility issues.</p>
124</div> 119</div>
125<div class="section" id="how-to-use-this-template"> 120<div class="section">
126<h1><a class="toc-backref" href="#id28" name="how-to-use-this-template">How to Use This Template</a></h1> 121<h1><a class="toc-backref" href="#id28" id="how-to-use-this-template" name="how-to-use-this-template">How to Use This Template</a></h1>
127<p>To use this template you must first decide whether your GLEP is going to be an 122<p>To use this template you must first decide whether your GLEP is going to be an
128Informational or Standards Track GLEP. Most GLEPs are Standards Track because 123Informational or Standards Track GLEP. Most GLEPs are Standards Track because
129they propose new functionality for some aspect of Gentoo Linux. When in 124they propose new functionality for some aspect of Gentoo Linux. When in
130doubt, read GLEP 1 for details or contact the GLEP editors &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;.</p> 125doubt, read GLEP 1 for details or contact the GLEP editors &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;.</p>
131<p>Once you've decided which type of GLEP yours is going to be, follow the 126<p>Once you've decided which type of GLEP yours is going to be, follow the
132directions below.</p> 127directions below.</p>
133<ul> 128<ul>
134<li><p class="first">Make a copy of this file (<tt class="literal"><span class="pre">.txt</span></tt> file, <strong>not</strong> HTML!) and perform 129<li><p class="first">Make a copy of this file (<tt class="docutils literal"><span class="pre">.txt</span></tt> file, <strong>not</strong> HTML!) and perform
135the following edits.</p> 130the following edits.</p>
136</li> 131</li>
137<li><p class="first">Replace the &quot;GLEP: 2&quot; header with &quot;GLEP: XXX&quot; since you don't yet have 132<li><p class="first">Replace the &quot;GLEP: 2&quot; header with &quot;GLEP: XXX&quot; since you don't yet have
138a GLEP number assignment.</p> 133a GLEP number assignment.</p>
139</li> 134</li>
147appear first, and it must not be contained in parentheses. Your email 142appear first, and it must not be contained in parentheses. Your email
148address may appear second (or it can be omitted) and if it appears, it must 143address may appear second (or it can be omitted) and if it appears, it must
149appear in angle brackets. Your e-mail address 144appear in angle brackets. Your e-mail address
150here will e automatically obfuscated.</p> 145here will e automatically obfuscated.</p>
151</li> 146</li>
152<li><p class="first">If there is a forum thread or a mailing list for discussion 147<li><p class="first">If there is a forum thread or a mailing list for discussion
153of your new feature, add a Discussions-To header right after the Author 148of your new feature, add a Discussions-To header right after the Author
154header. You should not add a Discussions-To header if the mailing list to 149header. You should not add a Discussions-To header if the mailing list to
155be used is <a class="reference" href="mailto:gentoo-dev&#64;gentoo.org">gentoo-dev&#64;gentoo.org</a>, or if discussions should be sent to you 150be used is <a class="reference" href="mailto:gentoo-dev&#64;gentoo.org">gentoo-dev&#64;gentoo.org</a>, or if discussions should be sent to you
156directly. Most Informational GLEPs don't have a Discussions-To header.</p> 151directly. Most Informational GLEPs don't have a Discussions-To header.</p>
157</li> 152</li>
167after the Type header. The value should be the GLEP number of the GLEP 162after the Type header. The value should be the GLEP number of the GLEP
168yours depends on. Don't add this header if your dependent feature is 163yours depends on. Don't add this header if your dependent feature is
169described in a Final GLEP.</p> 164described in a Final GLEP.</p>
170</li> 165</li>
171<li><p class="first">Change the Created header to today's date. Be sure to follow the 166<li><p class="first">Change the Created header to today's date. Be sure to follow the
172format carefully: it must be in <tt class="literal"><span class="pre">dd-mmm-yyyy</span></tt> format, where the <tt class="literal"><span class="pre">mmm</span></tt> is 167format carefully: it must be in <tt class="docutils literal"><span class="pre">dd-mmm-yyyy</span></tt> format, where the <tt class="docutils literal"><span class="pre">mmm</span></tt> is
173the 3 English letter month abbreviation, i.e. one of Jan, Feb, Mar, Apr, 168the 3 English letter month abbreviation, i.e. one of Jan, Feb, Mar, Apr,
174May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.</p> 169May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.</p>
175</li> 170</li>
176<li><p class="first">Leave Post-History alone for now; you'll add dates to this header 171<li><p class="first">Leave Post-History alone for now; you'll add dates to this header
177each time you post your GLEP to <a class="reference" href="mailto:gentoo-dev&#64;gentoo.org">gentoo-dev&#64;gentoo.org</a>. If you posted your 172each time you post your GLEP to <a class="reference" href="mailto:gentoo-dev&#64;gentoo.org">gentoo-dev&#64;gentoo.org</a>. If you posted your
200</li> 195</li>
201<li><p class="first">Send your GLEP submission to the GLEP editors at <a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>.</p> 196<li><p class="first">Send your GLEP submission to the GLEP editors at <a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>.</p>
202</li> 197</li>
203</ul> 198</ul>
204</div> 199</div>
205<div class="section" id="restructuredtext-glep-formatting-requirements"> 200<div class="section">
206<h1><a class="toc-backref" href="#id29" name="restructuredtext-glep-formatting-requirements">ReStructuredText GLEP Formatting Requirements</a></h1> 201<h1><a class="toc-backref" href="#id29" id="restructuredtext-glep-formatting-requirements" name="restructuredtext-glep-formatting-requirements">ReStructuredText GLEP Formatting Requirements</a></h1>
207<p>The following is a GLEP-specific summary of reStructuredText syntax. For the 202<p>The following is a GLEP-specific summary of reStructuredText syntax. For the
208sake of simplicity and brevity, much detail is omitted. For more detail, see 203sake of simplicity and brevity, much detail is omitted. For more detail, see
209<a class="reference" href="#resources">Resources</a> below. <a class="reference" href="#literal-blocks">Literal blocks</a> (in which no markup processing is done) 204<a class="reference" href="#resources">Resources</a> below. <a class="reference" href="#literal-blocks">Literal blocks</a> (in which no markup processing is done)
210are used for examples throughout, to illustrate the plaintext markup.</p> 205are used for examples throughout, to illustrate the plaintext markup.</p>
211<div class="section" id="general"> 206<div class="section">
212<h2><a class="toc-backref" href="#id30" name="general">General</a></h2> 207<h2><a class="toc-backref" href="#id30" id="general" name="general">General</a></h2>
213<p>You must adhere to the convention of adding two spaces at the end of every 208<p>You must adhere to the convention of adding two spaces at the end of every
214sentence. You should fill your paragraphs to column 70, but under no 209sentence. You should fill your paragraphs to column 70, but under no
215circumstances should your lines extend past column 79. If your code samples 210circumstances should your lines extend past column 79. If your code samples
216spill over column 79, you should rewrite them.</p> 211spill over column 79, you should rewrite them.</p>
217</div> 212</div>
218<div class="section" id="section-headings"> 213<div class="section">
219<h2><a class="toc-backref" href="#id31" name="section-headings">Section Headings</a></h2> 214<h2><a class="toc-backref" href="#id31" id="section-headings" name="section-headings">Section Headings</a></h2>
220<p>GLEP headings must begin in column zero and the initial letter of each word 215<p>GLEP headings must begin in column zero and the initial letter of each word
221must be capitalized as in book titles. Acronyms should be in all capitals. 216must be capitalized as in book titles. Acronyms should be in all capitals.
222Section titles must be adorned with an underline, a single repeated 217Section titles must be adorned with an underline, a single repeated
223punctuation character, which begins in column zero and must extend at least as 218punctuation character, which begins in column zero and must extend at least as
224far as the right edge of the title text (4 characters minimum). First-level 219far as the right edge of the title text (4 characters minimum). First-level
262heading, a single blank line in-between is sufficient.</p> 257heading, a single blank line in-between is sufficient.</p>
263<p>The body of each section is not normally indented, although some constructs do 258<p>The body of each section is not normally indented, although some constructs do
264use indentation, as described below. Blank lines are used to separate 259use indentation, as described below. Blank lines are used to separate
265constructs.</p> 260constructs.</p>
266</div> 261</div>
267<div class="section" id="paragraphs"> 262<div class="section">
268<h2><a class="toc-backref" href="#id32" name="paragraphs">Paragraphs</a></h2> 263<h2><a class="toc-backref" href="#id32" id="paragraphs" name="paragraphs">Paragraphs</a></h2>
269<p>Paragraphs are left-aligned text blocks separated by blank lines. Paragraphs 264<p>Paragraphs are left-aligned text blocks separated by blank lines. Paragraphs
270are not indented unless they are part of an indented construct (such as a 265are not indented unless they are part of an indented construct (such as a
271block quote or a list item).</p> 266block quote or a list item).</p>
272</div> 267</div>
273<div class="section" id="inline-markup"> 268<div class="section">
274<h2><a class="toc-backref" href="#id33" name="inline-markup">Inline Markup</a></h2> 269<h2><a class="toc-backref" href="#id33" id="inline-markup" name="inline-markup">Inline Markup</a></h2>
275<p>Portions of text within paragraphs and other text blocks may be 270<p>Portions of text within paragraphs and other text blocks may be
276styled. For example:</p> 271styled. For example:</p>
277<pre class="literal-block"> 272<pre class="literal-block">
278Text may be marked as *emphasized* (single asterisk markup, 273Text may be marked as *emphasized* (single asterisk markup,
279typically shown in italics) or **strongly emphasized** (double 274typically shown in italics) or **strongly emphasized** (double
281backquotes) are typically rendered in a monospaced typeface. No 276backquotes) are typically rendered in a monospaced typeface. No
282further markup recognition is done within the double backquotes, 277further markup recognition is done within the double backquotes,
283so they're safe for any kind of code snippets. 278so they're safe for any kind of code snippets.
284</pre> 279</pre>
285</div> 280</div>
286<div class="section" id="block-quotes"> 281<div class="section">
287<h2><a class="toc-backref" href="#id34" name="block-quotes">Block Quotes</a></h2> 282<h2><a class="toc-backref" href="#id34" id="block-quotes" name="block-quotes">Block Quotes</a></h2>
288<p>Block quotes consist of indented body elements. For example:</p> 283<p>Block quotes consist of indented body elements. For example:</p>
289<pre class="literal-block"> 284<pre class="literal-block">
290This is a paragraph. 285This is a paragraph.
291 286
292 This is a block quote. 287 This is a block quote.
295</pre> 290</pre>
296<p>Block quotes are used to quote extended passages from other sources. 291<p>Block quotes are used to quote extended passages from other sources.
297Block quotes may be nested inside other body elements. Use a 4-space tab 292Block quotes may be nested inside other body elements. Use a 4-space tab
298per indent level.</p> 293per indent level.</p>
299</div> 294</div>
300<div class="section" id="literal-blocks"> 295<div class="section">
301<h2><a class="toc-backref" href="#id35" name="literal-blocks">Literal Blocks</a></h2> 296<h2><a class="toc-backref" href="#id35" id="literal-blocks" name="literal-blocks">Literal Blocks</a></h2>
302<!-- In the text below, double backquotes are used to denote inline 297<!-- In the text below, double backquotes are used to denote inline
303literals. "``::``" is written so that the colons will appear in a 298literals. "``::``" is written so that the colons will appear in a
304monospaced font; the backquotes (``) are markup, not part of the 299monospaced font; the backquotes (``) are markup, not part of the
305text. See "Inline Markup" above. 300text. See "Inline Markup" above.
306 301
307By the way, this is a comment, described in "Comments" below. --> 302By the way, this is a comment, described in "Comments" below. -->
308<p>Literal blocks are used for code samples or preformatted ASCII art. To 303<p>Literal blocks are used for code samples or preformatted ASCII art. To
309indicate a literal block, preface the indented text block with 304indicate a literal block, preface the indented text block with
310&quot;<tt class="literal"><span class="pre">::</span></tt>&quot; (two colons). The literal block continues until the end of 305&quot;<tt class="docutils literal"><span class="pre">::</span></tt>&quot; (two colons). The literal block continues until the end of
311the indentation. Indent the text block by a tab. For example:</p> 306the indentation. Indent the text block by a tab. For example:</p>
312<pre class="literal-block"> 307<pre class="literal-block">
313This is a typical paragraph. A literal block follows. 308This is a typical paragraph. A literal block follows.
314 309
315:: 310::
317 for a in [5,4,3,2,1]: # this is program code, shown as-is 312 for a in [5,4,3,2,1]: # this is program code, shown as-is
318 print a 313 print a
319 print &quot;it's...&quot; 314 print &quot;it's...&quot;
320 # a literal block continues until the indentation ends 315 # a literal block continues until the indentation ends
321</pre> 316</pre>
322<p>The paragraph containing only &quot;<tt class="literal"><span class="pre">::</span></tt>&quot; will be completely removed from 317<p>The paragraph containing only &quot;<tt class="docutils literal"><span class="pre">::</span></tt>&quot; will be completely removed from
323the output; no empty paragraph will remain. &quot;<tt class="literal"><span class="pre">::</span></tt>&quot; is also 318the output; no empty paragraph will remain. &quot;<tt class="docutils literal"><span class="pre">::</span></tt>&quot; is also
324recognized at the end of any paragraph. If immediately preceded by 319recognized at the end of any paragraph. If immediately preceded by
325whitespace, both colons will be removed from the output. When text 320whitespace, both colons will be removed from the output. When text
326immediately precedes the &quot;<tt class="literal"><span class="pre">::</span></tt>&quot;, <em>one</em> colon will be removed from 321immediately precedes the &quot;<tt class="docutils literal"><span class="pre">::</span></tt>&quot;, <em>one</em> colon will be removed from
327the output, leaving only one colon visible (i.e., &quot;<tt class="literal"><span class="pre">::</span></tt>&quot; will be 322the output, leaving only one colon visible (i.e., &quot;<tt class="docutils literal"><span class="pre">::</span></tt>&quot; will be
328replaced by &quot;<tt class="literal"><span class="pre">:</span></tt>&quot;). For example, one colon will remain visible 323replaced by &quot;<tt class="docutils literal"><span class="pre">:</span></tt>&quot;). For example, one colon will remain visible
329here:</p> 324here:</p>
330<pre class="literal-block"> 325<pre class="literal-block">
331Paragraph:: 326Paragraph::
332 327
333 Literal block 328 Literal block
334</pre> 329</pre>
335</div> 330</div>
336<div class="section" id="lists"> 331<div class="section">
337<h2><a class="toc-backref" href="#id36" name="lists">Lists</a></h2> 332<h2><a class="toc-backref" href="#id36" id="lists" name="lists">Lists</a></h2>
338<p>Bullet list items begin with one of &quot;-&quot;, &quot;*&quot;, or &quot;+&quot; (hyphen, 333<p>Bullet list items begin with one of &quot;-&quot;, &quot;*&quot;, or &quot;+&quot; (hyphen,
339asterisk, or plus sign), followed by whitespace and the list item 334asterisk, or plus sign), followed by whitespace and the list item
340body. List item bodies must be left-aligned and indented relative to 335body. List item bodies must be left-aligned and indented relative to
341the bullet; the text immediately after the bullet determines the 336the bullet; the text immediately after the bullet determines the
342indentation. For example:</p> 337indentation. For example:</p>
388 The term is a one-line phrase, and the definition is one 383 The term is a one-line phrase, and the definition is one
389 or more paragraphs or body elements, indented relative to 384 or more paragraphs or body elements, indented relative to
390 the term. 385 the term.
391</pre> 386</pre>
392</div> 387</div>
393<div class="section" id="tables"> 388<div class="section">
394<h2><a class="toc-backref" href="#id37" name="tables">Tables</a></h2> 389<h2><a class="toc-backref" href="#id37" id="tables" name="tables">Tables</a></h2>
395<p>Simple tables are easy and compact:</p> 390<p>Simple tables are easy and compact:</p>
396<pre class="literal-block"> 391<pre class="literal-block">
397===== ===== ======= 392===== ===== =======
398 A B A and B 393 A B A and B
399===== ===== ======= 394===== ===== =======
433 - Second item in bullet 428 - Second item in bullet
434 list (row 3, column 2). 429 list (row 3, column 2).
435===== ========================= 430===== =========================
436</pre> 431</pre>
437</div> 432</div>
438<div class="section" id="hyperlinks"> 433<div class="section">
439<h2><a class="toc-backref" href="#id38" name="hyperlinks">Hyperlinks</a></h2> 434<h2><a class="toc-backref" href="#id38" id="hyperlinks" name="hyperlinks">Hyperlinks</a></h2>
440<p>When referencing an external web page in the body of a GLEP, you should 435<p>When referencing an external web page in the body of a GLEP, you should
441include the title of the page in the text, with either an inline 436include the title of the page in the text, with either an inline
442hyperlink reference to the URL or a footnote reference (see 437hyperlink reference to the URL or a footnote reference (see
443<a class="reference" href="#footnotes">Footnotes</a> below). Do not include the URL in the body text of the 438<a class="reference" href="#footnotes">Footnotes</a> below). Do not include the URL in the body text of the
444GLEP.</p> 439GLEP.</p>
473automatically at the end of the References section of the GLEP, along 468automatically at the end of the References section of the GLEP, along
474with footnote references linking the reference text to the footnotes.</p> 469with footnote references linking the reference text to the footnotes.</p>
475<p>Text of the form &quot;GLEP x&quot; or &quot;RFC x&quot; (where &quot;x&quot; is a number) will be 470<p>Text of the form &quot;GLEP x&quot; or &quot;RFC x&quot; (where &quot;x&quot; is a number) will be
476linked automatically to the appropriate URLs.</p> 471linked automatically to the appropriate URLs.</p>
477</div> 472</div>
478<div class="section" id="footnotes"> 473<div class="section">
479<h2><a class="toc-backref" href="#id39" name="footnotes">Footnotes</a></h2> 474<h2><a class="toc-backref" href="#id39" id="footnotes" name="footnotes">Footnotes</a></h2>
480<p>Footnote references consist of a left square bracket, a number, a 475<p>Footnote references consist of a left square bracket, a number, a
481right square bracket, and a trailing underscore:</p> 476right square bracket, and a trailing underscore:</p>
482<pre class="literal-block"> 477<pre class="literal-block">
483This sentence ends with a footnote reference [1]_. 478This sentence ends with a footnote reference [1]_.
484</pre> 479</pre>
528</pre> 523</pre>
529<p>Footnotes and footnote references will be numbered automatically, and 524<p>Footnotes and footnote references will be numbered automatically, and
530the numbers will always match. Once a GLEP is finalized, auto-numbered 525the numbers will always match. Once a GLEP is finalized, auto-numbered
531labels should be replaced by numbers for simplicity.</p> 526labels should be replaced by numbers for simplicity.</p>
532</div> 527</div>
533<div class="section" id="images"> 528<div class="section">
534<h2><a class="toc-backref" href="#id40" name="images">Images</a></h2> 529<h2><a class="toc-backref" href="#id40" id="images" name="images">Images</a></h2>
535<p>If your GLEP contains a diagram, you may include it in the processed 530<p>If your GLEP contains a diagram, you may include it in the processed
536output using the &quot;image&quot; directive:</p> 531output using the &quot;image&quot; directive:</p>
537<pre class="literal-block"> 532<pre class="literal-block">
538.. image:: diagram.png 533.. image:: diagram.png
539</pre> 534</pre>
541.tiff, etc.</p> 536.tiff, etc.</p>
542<p>Since this image will not be visible to readers of the GLEP in source 537<p>Since this image will not be visible to readers of the GLEP in source
543text form, you should consider including a description or ASCII art 538text form, you should consider including a description or ASCII art
544alternative, using a comment (below).</p> 539alternative, using a comment (below).</p>
545</div> 540</div>
546<div class="section" id="comments"> 541<div class="section">
547<h2><a class="toc-backref" href="#id41" name="comments">Comments</a></h2> 542<h2><a class="toc-backref" href="#id41" id="comments" name="comments">Comments</a></h2>
548<p>A comment block is an indented block of arbitrary text immediately 543<p>A comment block is an indented block of arbitrary text immediately
549following an explicit markup start: two periods and whitespace. Leave 544following an explicit markup start: two periods and whitespace. Leave
550the &quot;..&quot; on a line by itself to ensure that the comment is not 545the &quot;..&quot; on a line by itself to ensure that the comment is not
551misinterpreted as another explicit markup construct. Comments are not 546misinterpreted as another explicit markup construct. Comments are not
552visible in the processed document. For the benefit of those reading 547visible in the processed document. For the benefit of those reading
558.. 553..
559 Data flows from the input module, through the &quot;black box&quot; 554 Data flows from the input module, through the &quot;black box&quot;
560 module, and finally into (and through) the output module. 555 module, and finally into (and through) the output module.
561</pre> 556</pre>
562</div> 557</div>
563<div class="section" id="escaping-mechanism"> 558<div class="section">
564<h2><a class="toc-backref" href="#id42" name="escaping-mechanism">Escaping Mechanism</a></h2> 559<h2><a class="toc-backref" href="#id42" id="escaping-mechanism" name="escaping-mechanism">Escaping Mechanism</a></h2>
565<p>reStructuredText uses backslashes (&quot;<tt class="literal"><span class="pre">\</span></tt>&quot;) to override the special 560<p>reStructuredText uses backslashes (&quot;<tt class="docutils literal"><span class="pre">\</span></tt>&quot;) to override the special
566meaning given to markup characters and get the literal characters 561meaning given to markup characters and get the literal characters
567themselves. To get a literal backslash, use an escaped backslash 562themselves. To get a literal backslash, use an escaped backslash
568(&quot;<tt class="literal"><span class="pre">\\</span></tt>&quot;). There are two contexts in which backslashes have no 563(&quot;<tt class="docutils literal"><span class="pre">\\</span></tt>&quot;). There are two contexts in which backslashes have no
569special meaning: <a class="reference" href="#literal-blocks">literal blocks</a> and inline literals (see <a class="reference" href="#inline-markup">Inline 564special meaning: <a class="reference" href="#literal-blocks">literal blocks</a> and inline literals (see <a class="reference" href="#inline-markup">Inline
570Markup</a> above). In these contexts, no markup recognition is done, 565Markup</a> above). In these contexts, no markup recognition is done,
571and a single backslash represents a literal backslash, without having 566and a single backslash represents a literal backslash, without having
572to double up.</p> 567to double up.</p>
573<p>If you find that you need to use a backslash in your text, consider 568<p>If you find that you need to use a backslash in your text, consider
574using inline literals or a literal block instead.</p> 569using inline literals or a literal block instead.</p>
575</div> 570</div>
576</div> 571</div>
577<div class="section" id="habits-to-avoid"> 572<div class="section">
578<h1><a class="toc-backref" href="#id43" name="habits-to-avoid">Habits to Avoid</a></h1> 573<h1><a class="toc-backref" href="#id43" id="habits-to-avoid" name="habits-to-avoid">Habits to Avoid</a></h1>
579<p>Many programmers who are familiar with TeX often write quotation marks 574<p>Many programmers who are familiar with TeX often write quotation marks
580like this:</p> 575like this:</p>
581<pre class="literal-block"> 576<pre class="literal-block">
582`single-quoted' or ``double-quoted'' 577`single-quoted' or ``double-quoted''
583</pre> 578</pre>
587above), use double-backquotes:</p> 582above), use double-backquotes:</p>
588<pre class="literal-block"> 583<pre class="literal-block">
589``literal text: in here, anything goes!`` 584``literal text: in here, anything goes!``
590</pre> 585</pre>
591</div> 586</div>
592<div class="section" id="resources"> 587<div class="section">
593<h1><a class="toc-backref" href="#id44" name="resources">Resources</a></h1> 588<h1><a class="toc-backref" href="#id44" id="resources" name="resources">Resources</a></h1>
594<p>Many other constructs and variations are possible. For more details 589<p>Many other constructs and variations are possible. For more details
595about the reStructuredText markup, in increasing order of 590about the reStructuredText markup, in increasing order of
596thoroughness, please see:</p> 591thoroughness, please see:</p>
597<ul class="simple"> 592<ul class="simple">
598<li><a class="reference" href="http://docutils.sourceforge.net/docs/rst/quickstart.html">A ReStructuredText Primer</a> <a class="footnote-reference" href="#id17" id="id18" name="id18">[8]</a>, a gentle introduction.</li> 593<li><a class="reference" href="http://docutils.sourceforge.net/docs/rst/quickstart.html">A ReStructuredText Primer</a> <a class="footnote-reference" href="#id17" id="id18" name="id18">[8]</a>, a gentle introduction.</li>
602<p>The processing of reStructuredText GLEPs is done using <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> <a class="footnote-reference" href="#id8" id="id9" name="id9">[4]</a>. If 597<p>The processing of reStructuredText GLEPs is done using <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> <a class="footnote-reference" href="#id8" id="id9" name="id9">[4]</a>. If
603you have a question or require assistance with reStructuredText or 598you have a question or require assistance with reStructuredText or
604Docutils, please <a class="reference" href="mailto:docutils-users&#64;lists.sourceforge.net?subject=GLEPs">post a message</a> <a class="footnote-reference" href="#id10" id="id11" name="id11">[5]</a> to the <a class="reference" href="http://lists.sourceforge.net/lists/listinfo/docutils-users">Docutils-Users mailing 599Docutils, please <a class="reference" href="mailto:docutils-users&#64;lists.sourceforge.net?subject=GLEPs">post a message</a> <a class="footnote-reference" href="#id10" id="id11" name="id11">[5]</a> to the <a class="reference" href="http://lists.sourceforge.net/lists/listinfo/docutils-users">Docutils-Users mailing
605list</a> <a class="footnote-reference" href="#id12" id="id13" name="id13">[6]</a>. The <a class="reference" href="http://docutils.sourceforge.net/">Docutils project web site</a> <a class="footnote-reference" href="#id8" id="id14" name="id14">[4]</a> has more information.</p> 600list</a> <a class="footnote-reference" href="#id12" id="id13" name="id13">[6]</a>. The <a class="reference" href="http://docutils.sourceforge.net/">Docutils project web site</a> <a class="footnote-reference" href="#id8" id="id14" name="id14">[4]</a> has more information.</p>
606</div> 601</div>
607<div class="section" id="references"> 602<div class="section">
608<h1><a class="toc-backref" href="#id45" name="references">References</a></h1> 603<h1><a class="toc-backref" href="#id45" id="references" name="references">References</a></h1>
609<table class="footnote" frame="void" id="python" rules="none"> 604<table class="docutils footnote" frame="void" id="python" rules="none">
610<colgroup><col class="label" /><col /></colgroup> 605<colgroup><col class="label" /><col /></colgroup>
611<tbody valign="top"> 606<tbody valign="top">
612<tr><td class="label"><a class="fn-backref" href="#id1" name="python">[1]</a></td><td><a class="reference" href="http://www.python.org">http://www.python.org</a></td></tr> 607<tr><td class="label"><a class="fn-backref" href="#id1" name="python">[1]</a></td><td><a class="reference" href="http://www.python.org">http://www.python.org</a></td></tr>
613</tbody> 608</tbody>
614</table> 609</table>
615<table class="footnote" frame="void" id="pep12" rules="none"> 610<table class="docutils footnote" frame="void" id="pep12" rules="none">
616<colgroup><col class="label" /><col /></colgroup> 611<colgroup><col class="label" /><col /></colgroup>
617<tbody valign="top"> 612<tbody valign="top">
618<tr><td class="label"><a class="fn-backref" href="#id2" name="pep12">[2]</a></td><td><a class="reference" href="http://www.python.org/peps/pep-0012.html">http://www.python.org/peps/pep-0012.html</a></td></tr> 613<tr><td class="label"><a class="fn-backref" href="#id2" name="pep12">[2]</a></td><td><a class="reference" href="http://www.python.org/peps/pep-0012.html">http://www.python.org/peps/pep-0012.html</a></td></tr>
619</tbody> 614</tbody>
620</table> 615</table>
621<table class="footnote" frame="void" id="glep1" rules="none"> 616<table class="docutils footnote" frame="void" id="glep1" rules="none">
622<colgroup><col class="label" /><col /></colgroup> 617<colgroup><col class="label" /><col /></colgroup>
623<tbody valign="top"> 618<tbody valign="top">
624<tr><td class="label"><a class="fn-backref" href="#id3" name="glep1">[3]</a></td><td>GLEP 1, GLEP Purpose and Guidelines, Goodyear, 619<tr><td class="label"><a class="fn-backref" href="#id3" name="glep1">[3]</a></td><td>GLEP 1, GLEP Purpose and Guidelines, Goodyear,
625(<a class="reference" href="http://glep.gentoo.org/glep-0001.html">http://glep.gentoo.org/glep-0001.html</a>)</td></tr> 620(<a class="reference" href="http://glep.gentoo.org/glep-0001.html">http://glep.gentoo.org/glep-0001.html</a>)</td></tr>
626</tbody> 621</tbody>
627</table> 622</table>
628<table class="footnote" frame="void" id="id8" rules="none"> 623<table class="docutils footnote" frame="void" id="id8" rules="none">
629<colgroup><col class="label" /><col /></colgroup> 624<colgroup><col class="label" /><col /></colgroup>
630<tbody valign="top"> 625<tbody valign="top">
631<tr><td class="label"><a name="id8">[4]</a></td><td><em>(<a class="fn-backref" href="#id9">1</a>, <a class="fn-backref" href="#id14">2</a>)</em> <a class="reference" href="http://docutils.sourceforge.net/">http://docutils.sourceforge.net/</a></td></tr> 626<tr><td class="label"><a name="id8">[4]</a></td><td><em>(<a class="fn-backref" href="#id9">1</a>, <a class="fn-backref" href="#id14">2</a>)</em> <a class="reference" href="http://docutils.sourceforge.net/">http://docutils.sourceforge.net/</a></td></tr>
632</tbody> 627</tbody>
633</table> 628</table>
634<table class="footnote" frame="void" id="id10" rules="none"> 629<table class="docutils footnote" frame="void" id="id10" rules="none">
635<colgroup><col class="label" /><col /></colgroup> 630<colgroup><col class="label" /><col /></colgroup>
636<tbody valign="top"> 631<tbody valign="top">
637<tr><td class="label"><a class="fn-backref" href="#id11" name="id10">[5]</a></td><td><a class="reference" href="mailto:docutils-users&#64;lists.sourceforge.net?subject=GLEPs">mailto:docutils-users&#64;lists.sourceforge.net?subject=GLEPs</a></td></tr> 632<tr><td class="label"><a class="fn-backref" href="#id11" name="id10">[5]</a></td><td><a class="reference" href="mailto:docutils-users&#64;lists.sourceforge.net?subject=GLEPs">mailto:docutils-users&#64;lists.sourceforge.net?subject=GLEPs</a></td></tr>
638</tbody> 633</tbody>
639</table> 634</table>
640<table class="footnote" frame="void" id="id12" rules="none"> 635<table class="docutils footnote" frame="void" id="id12" rules="none">
641<colgroup><col class="label" /><col /></colgroup> 636<colgroup><col class="label" /><col /></colgroup>
642<tbody valign="top"> 637<tbody valign="top">
643<tr><td class="label"><a class="fn-backref" href="#id13" name="id12">[6]</a></td><td><a class="reference" href="http://lists.sourceforge.net/lists/listinfo/docutils-users">http://lists.sourceforge.net/lists/listinfo/docutils-users</a></td></tr> 638<tr><td class="label"><a class="fn-backref" href="#id13" name="id12">[6]</a></td><td><a class="reference" href="http://lists.sourceforge.net/lists/listinfo/docutils-users">http://lists.sourceforge.net/lists/listinfo/docutils-users</a></td></tr>
644</tbody> 639</tbody>
645</table> 640</table>
646<table class="footnote" frame="void" id="id15" rules="none"> 641<table class="docutils footnote" frame="void" id="id15" rules="none">
647<colgroup><col class="label" /><col /></colgroup> 642<colgroup><col class="label" /><col /></colgroup>
648<tbody valign="top"> 643<tbody valign="top">
649<tr><td class="label"><a class="fn-backref" href="#id16" name="id15">[7]</a></td><td><a class="reference" href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a></td></tr> 644<tr><td class="label"><a class="fn-backref" href="#id16" name="id15">[7]</a></td><td><a class="reference" href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a></td></tr>
650</tbody> 645</tbody>
651</table> 646</table>
652<table class="footnote" frame="void" id="id17" rules="none"> 647<table class="docutils footnote" frame="void" id="id17" rules="none">
653<colgroup><col class="label" /><col /></colgroup> 648<colgroup><col class="label" /><col /></colgroup>
654<tbody valign="top"> 649<tbody valign="top">
655<tr><td class="label"><a class="fn-backref" href="#id18" name="id17">[8]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/docs/rst/quickstart.html">http://docutils.sourceforge.net/docs/rst/quickstart.html</a></td></tr> 650<tr><td class="label"><a class="fn-backref" href="#id18" name="id17">[8]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/docs/rst/quickstart.html">http://docutils.sourceforge.net/docs/rst/quickstart.html</a></td></tr>
656</tbody> 651</tbody>
657</table> 652</table>
658<table class="footnote" frame="void" id="id19" rules="none"> 653<table class="docutils footnote" frame="void" id="id19" rules="none">
659<colgroup><col class="label" /><col /></colgroup> 654<colgroup><col class="label" /><col /></colgroup>
660<tbody valign="top"> 655<tbody valign="top">
661<tr><td class="label"><a class="fn-backref" href="#id20" name="id19">[9]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/docs/rst/quickref.html">http://docutils.sourceforge.net/docs/rst/quickref.html</a></td></tr> 656<tr><td class="label"><a class="fn-backref" href="#id20" name="id19">[9]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/docs/rst/quickref.html">http://docutils.sourceforge.net/docs/rst/quickref.html</a></td></tr>
662</tbody> 657</tbody>
663</table> 658</table>
664<table class="footnote" frame="void" id="id21" rules="none"> 659<table class="docutils footnote" frame="void" id="id21" rules="none">
665<colgroup><col class="label" /><col /></colgroup> 660<colgroup><col class="label" /><col /></colgroup>
666<tbody valign="top"> 661<tbody valign="top">
667<tr><td class="label"><a class="fn-backref" href="#id22" name="id21">[10]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/spec/rst/reStructuredText.html">http://docutils.sourceforge.net/spec/rst/reStructuredText.html</a></td></tr> 662<tr><td class="label"><a class="fn-backref" href="#id22" name="id21">[10]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/spec/rst/reStructuredText.html">http://docutils.sourceforge.net/spec/rst/reStructuredText.html</a></td></tr>
668</tbody> 663</tbody>
669</table> 664</table>
670</div> 665</div>
671<div class="section" id="copyright"> 666<div class="section">
672<h1><a class="toc-backref" href="#id46" name="copyright">Copyright</a></h1> 667<h1><a class="toc-backref" href="#id46" id="copyright" name="copyright">Copyright</a></h1>
673<p>This document has been placed in the public domain.</p> 668<p>This document has been placed in the public domain.</p>
674</div> 669</div>
675</div>
676 670
677<hr class="footer"/> 671</div>
678<div class="footer"> 672<div class="footer">
673<hr class="footer" />
679<a class="reference" href="glep-0002.txt">View document source</a>. 674<a class="reference" href="glep-0002.txt">View document source</a>.
680Generated on: 2003-06-04 19:49 UTC. 675Generated on: 2007-10-13 13:39 UTC.
681Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 676Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
677
682</div> 678</div>
683</body> 679</body>
684</html> 680</html>
685 681

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.9

  ViewVC Help
Powered by ViewVC 1.1.20