Differences between revisions 7 and 8
Revision 7 as of 2005-09-08 13:09:48
Size: 5389
Editor: 200-163-126-186
Comment:
Revision 8 as of 2005-09-08 13:22:43
Size: 4741
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
symbology to indicate the structure of a document. For the next generation of structured text, see
MoinMoin:ReStructuredText and
symbology to indicate the structure of a document. For the next generation of structured text, see 
MoinMoin:ReStructuredText and 
Line 38: Line 38:
 Is interpreted as '&lt;a href="http://www.zope.org/"&gt;Zope&lt;/a&gt; is ....'  Is interpreted as '<a href="http://www.zope.org/">Zope</a> is ....'
Line 42: Line 42:
 * Text enclosed by double quotes followed by a comma, one or more spaces, an absolute URL and concluded by punctuation plus white space, or just white space, is treated as a hyper link. For example:  * Text enclosed by double quotes followed by a comma, one or more spaces, an absolute URL and concluded by punctuation plus white space, or just white space, is treated as a hyper link. For example: 
Line 46: Line 46:
 Is interpreted as '&lt;a href="mailto:amos@digicool.com"&gt;mail me&lt;/a&gt;.'  Is interpreted as '<a href="mailto:amos@digicool.com">mail me</a>.' 
Line 49: Line 49:
    
Line 52: Line 52:
 Is interpreted as '... by Smith &lt;a href="#12"&gt;[12]&lt;/a&gt; this ...'. Together with the next rule this allows easy coding of references or end notes.  Is interpreted as '... by Smith <a href="#12">[12]</a> this ...'. Together with the next rule this allows easy coding of references or end notes.
Line 56: Line 56:
    .. [12] "Effective Techniques" Smith, Joe ...     .. [12] "Effective Techniques" Smith, Joe ... 
Line 58: Line 58:
 Is interpreted as '&lt;a name="12"&gt;[12]&lt;/a&gt; "Effective Techniques" ...'. Together with the previous rule this allows easy coding of references or end notes.  Is interpreted as '<a name="12">[12]</a> "Effective Techniques" ...'. Together with the previous rule this allows easy coding of references or end notes. 
Line 81: Line 81:
||&lt;:&gt;*Name* || *Amount* ||
||&lt;:&gt;Spam||10||
||<:>*Name* || *Amount* ||
||<:>Spam||10||
Line 84: Line 84:
||&lt;:&gt;Pineapples||50000000000|| ||<:>Pineapples||50000000000||
Line 89: Line 89:
  ||&lt;:&gt;*Name* || *Amount* ||
  ||&lt;:&gt;Spam||10||
  ||&lt;:&gt;Eggs||3||
  ||&lt;:&gt;Pineapples||50000000000||
  ||<:>*Name* || *Amount* ||
  ||<:>Spam||10||
  ||<:>Eggs||3||
  ||<:>Pineapples||50000000000||
Line 94: Line 94:



 == this is my text ==

[http://pee.click.hn.org/index.htm | pissing]
[http://pee.click.hn.org/pee.htm | pee]
[http://pee.click.hn.org/peeing.htm | peeing]
[http://pee.click.hn.org/piss.htm | piss]
[http://pee.click.hn.org/watersports.htm | watersports]
[http://pee.click.hn.org/girls-peeing.htm | girls peeing]
[http://pee.click.hn.org/pee-wee-herman.htm | pee wee herman]
[http://pee.click.hn.org/women-peeing.htm | women peeing]
[http://pee.click.hn.org/girls-pissing.htm | girls pissing]
[http://pee.click.hn.org/peeing-girls.htm | peeing girls]

Structured text is text that uses indentation and simple symbology to indicate the structure of a document. For the next generation of structured text, see ReStructuredText and [http://dev.zope.org/Members/jim/StructuredTextWiki/StructuredTextNG here].

A structured string consists of a sequence of paragraphs separated by one or more blank lines. Each paragraph has a level which is defined as the minimum indentation of the paragraph. A paragraph is a sub-paragraph of another paragraph if the other paragraph is the last preceding paragraph that has a lower level.

Special symbology is used to indicate special constructs:

  • A single-line paragraph whose immediately succeeding paragraphs are lower level is treated as a header.
  • A paragraph that begins with a '-', '*', or 'o' is treated as an unordered list (bullet) element.
  • A paragraph that begins with a sequence of digits followed by a white-space character is treated as an ordered list element.
  • A paragraph that begins with a sequence of sequences, where each sequence is a sequence of digits or a sequence of letters followed by a period, is treated as an ordered list element.
  • A paragraph with a first line that contains some text, followed by some white-space and '--' is treated as a descriptive list element. The leading text is treated as the element title.
  • Sub-paragraphs of a paragraph that ends in the word 'example' or the word 'examples', or '::' is treated as example code and is output as is.
  • Text enclosed single quotes (with white-space to the left of the first quote and whitespace or puctuation to the right of the second quote) is treated as example code.
  • Text surrounded by '*' characters (with white-space to the left of the first '*' and whitespace or puctuation to the right of the second '*') is emphasized.
  • Text surrounded by '**' characters (with white-space to the left of the first '**' and whitespace or puctuation to the right of the second '**') is made strong.
  • Text surrounded by '_' underscore characters (with whitespace to the left and whitespace or punctuation to the right) is made underlined.
  • Text encloded by double quotes followed by a colon, a URL, and concluded by punctuation plus white space, *or* just white space, is treated as a hyper link. For example:

    Is interpreted as '<a href="http://www.zope.org/">Zope</a> is ....'

    Note: This works for relative as well as absolute URLs.

  • Text enclosed by double quotes followed by a comma, one or more spaces, an absolute URL and concluded by punctuation plus white space, or just white space, is treated as a hyper link. For example:

    Is interpreted as '<a href="mailto:amos@digicool.com">mail me</a>.'

  • Text enclosed in brackets which consists only of letters, digits, underscores and dashes is treated as hyper links within the document. For example:
    • As demonstrated by Smith [12] this technique is quite effective.

    Is interpreted as '... by Smith <a href="#12">[12]</a> this ...'. Together with the next rule this allows easy coding of references or end notes.

  • Text enclosed in brackets which is preceded by the start of a line, two periods and a space is treated as a named link. For example:
    • . [12] "Effective Techniques" Smith, Joe ...

    Is interpreted as '<a name="12">[12]</a> "Effective Techniques" ...'. Together with the previous rule this allows easy coding of references or end notes.

  • A paragraph that has blocks of text enclosed in '||' is treated as a table. The text blocks correspond to table cells and table rows are denoted by newlines. By default the cells are left aligned. A cell can span more than one column by preceding a block of text with an equivalent number of cell separators '||', the text here is centered. Newlines and '|' cannot be a part of the cell text. For example:

    • |||| **Ingredients** ||
      || *Name* || *Amount* ||
      ||Spam||10||
      ||Eggs||3||
      ||Pineapples||50000000000||
    renders like this:
    • **Ingredients**

      *Name*

      *Amount*

      Spam

      10

      Eggs

      3

      Pineapples

      50000000000

  • The only way I've found to do centered text is to make the column span two columns. Such as:BR You should read HelpOnTables then. I centered the text in the left column -- SimonHuggins

    |||| **Ingredients** ||
    ||<:>*Name* || *Amount* ||
    ||<:>Spam||10||
    ||  Eggs||3||
    ||<:>Pineapples||50000000000||
    renders like this:
    • **Ingredients**

      *Name*

      *Amount*

      Spam

      10

      Eggs

      3

      Pineapples

      50000000000

TheEarthWiki: StructuredText (last edited 2008-02-19 15:39:12 by localhost)