Re: [cowiki-dev] Extension to coWiki text formatting

I really don't know about the extent to which 'availability of 
[sophisticated formatting] will be controlled by the site 
administrator', but I would like to comment briefly on the proposed 
markup, mostly the stuff that is already familiar.

Does coWiki attempt to save & redisplay? Certainly stuff that can't be 
processed is often displayed in full, a sort of 'default to verbatim'. 
If we can define parser-success, then we can fail-to-verbatim. What if 
closing all tags was all we had to put faith in?

Doubled emphasis is a simple and effective solution. Nice one. I was 
thinking of of forcing the position of emphasis markup, but doubled 
emphasis with self-escaping covers everything.

For argument's sake, a content-section begins where a new context is 
defined, and lasts until the close of that context, commonly with a newline.

Headings should be recognised at the beginning of a content-section.

Lists, horizontal rules, preformatted text, code boxes, postings, 
quotes, similarly.

Beginning-of-content markups are available inside tables & lists, for 
example.

Links & variables & may be found wherever emphasis or justification may 
be, line break, subscript & superscript likewise.

New elements...

The <URL...> syntax should define the containing element for the merged 
(included) document?

Image syntax as given doesn't reflect proposed wiki-ness of images. 
Possibly as dtg works we will come to specify them as 
coming-from-the-database, not by url.

Changes to table format...

Since there are times when defined row-element and rigorous table syntax 
is required, I move that ^-delimited tables should be offered alongside 
<table>|-</table> syntax. Use as required.

LPIs...

May be found at newline, also must be first element (provided by initial 
parse if not submitted).

Only cowiki and html (pasted verbatim) a present. Awaiting security. How 
do we secure raw php? Or is what is wanted more a syntax highlighter 
like GeSHi?