Re: [Phpwiki-talk] RFC - markup changes for list items.

[Arno H. <aho...@in...>]

Neil,

could you point me to a patch so that I can look at your changes?

>  So, I would prefer that list items could continue onto multiple
>  lines. I have implemented a change that achieves this and it works quite
>  well.  When transform.php finds a line that starts with normal text,
>  it just includes it in the current context.  To terminate a list, you
>  just need a blank line, and this feels quite natural.

Hm, but you still could not indent the following lines, right? Or is this 
allowed as well? If so, is it then a <pre> block, or just normal text?
If you can't indent the lines, what's the difference? It wouldn't be 
visually more appealing, or am I wrong?

> ... add a new markup which means "paragraph break at this level"
>   1/ ";;;" is currently line break, so maybe ";;;;" could be new-para,

You mean "%%%" right?

>   2/ "." on a line by itself or at the start of a line might be good
>       as it is visually similar to the required concept:

Looks better, but generally speaking I'm no fan of creating too much new 
markup. After all, we don't want to reinvent HTML. We will modularize 
lib/transform.php in 1.3.x so it will be easier to integrate such custom 
markup.

>   Somewhat related to this, consider the lists in TextFormattingRules.
>   That are actually sequences of singleton lists.

That's true. Actually, I'm not too happy about the current state of 
SetHTMLOutputMode() but for different reasons. But apart from that, why is 
the current HTML that bad? It makes no difference to browsers, unless you 
are handicapped of some sort and rely on proper lists. In that case just 
include a style-sheet that spreads list-items. Not everything has to be 
done within wiki.

/Arno