[ZDP] Distributed authoring test

[Robert O'Connor]

Hi Craig,

Structured Text Example by Bob 
Examples from StructuredText.py 

I've tried the structured text contribution area and did a
fairly complete example using the comments in 
StructuredText.py.  Perhaps this error is generated
because of something in my "structured text" that
makes the zdp.zope barf???

http://zdp.zope.org/guide/contributions/chapter1/

(.../25)

But when I click on the link to my text I get error:

IE5 gives:
"HTTP 500 - Internal server error
Internet Explorer"

Also same error if I go into the management screens
to my "26 (text for 25) " and click view.

When I use Netscape 4.6 I get
"System Unavailable...This site is currently experiencing technical..."
and with NS, the traceback:

Traceback (innermost last):
  File lib/python/ZPublisher/Publish.py, line 877, in publish_module
  File lib/python/ZPublisher/Publish.py, line 590, in publish
    (Info: /guide/contributions/chapter1/25)
  File lib/python/OFS/DTMLDocument.py, line 212, in __call__
    (Object: 25)
  File lib/python/OFS/DTMLDocument.py, line 208, in __call__
    (Object: 25)
  File lib/python/DocumentTemplate/DT_String.py, line 513, in __call__
    (Object: 25)
  File lib/python/DocumentTemplate/DT_Var.py, line 239, in render
    (Object: _[mate])
  File lib/python/DocumentTemplate/DT_Util.py, line 266, in eval
    (Object: _[mate])
  File <string>, line 0, in ?
  File lib/python/DocumentTemplate/DT_Util.py, line 150, in careful_getitem
  File lib/python/OFS/DTMLMethod.py, line 147, in __call__
    (Object: 26)
  File lib/python/DocumentTemplate/DT_String.py, line 513, in __call__
    (Object: 26)
  File lib/python/DocumentTemplate/DT_With.py, line 130, in render
    (Object: BigFolder)
KeyError: (see above)

For further information, I' m posting my example structured text
*---start

STRUCTURED TEXT - Mini Example (a header) VER 0.1

 ( **From**: structured.py comment area) Structured text 
 is text that uses indentation and simple symbology to  
 indicate the structure of a document.

  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.

Symbology

 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. (-) used

 - A paragraph that begins with a '-', '*', or 'o' is  
  treated as an unordered list (bullet) element. (-) used

  1 ) A paragraph that begins with a sequence of digits 
  followed by a white-space character is treated as an 
  ordered list element.

  2 ) A paragraph that begins with a sequence of digits 
  followed by a white-space character is treated as an 
  ordered list element.

  3a.  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.

  3b.  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.

Some text and white space (End Title) -- 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. Here is the
code with double colon here::

<!--#with BigFolder-->
<!--#with SubFolder-->
<!--#var "_.getitem('foo',1)"-->
<!--#/with-->
<!--#/with-->


- 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.
This is the code: '<!--#var "bob"-->'.


*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 emphasized.


- **STRONG 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.

_Underlinded Text_ surrounded by '_' underscore characters (with 
whitespace to the left and whitespace or punctuation to the right) 
is made underlined.

- Text enclosed 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:

    "Zope":http://www.zope.org/ is ...

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:
    "mail me", mailto:amos@digicool.com.

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.

End test by "bob oconnor", mailto:bob@rocnet.com.

*---end

-Bob OConnor bob@rocnet.com