Description

Unordered lists will be rendered as numbered list, if preceded immediately by a numbered list.

Example

 1. One
 1. Two

 * Some
 * Thing

1. One
2. Two
3. Some
4. Thing

Details

Workaround

 1. One
 1. Two
## Separating remark
 * Some
 * Thing

1. One
2. Two

• Some
• Thing

Discussion

Don't concatenate lists: lists separated by one or more white lines should be rendered one by one as separated lists. Thus, even

 1. One
 1. Two

 1. First
 1. Second

should be rendered like

1. One
2. Two

°

1. First
2. Second

and not

1. One
2. Two
3. First
4. Second

Note that even an offset won't work here:

 1. One
 1. Two

 1.#1 First
 1.#2 Second

1. One
2. Two
3. First
4. Second

This is due to some features, not bugs:

• You can have paragraphs in a list item, you can have gaps in a list. A paragraph or gap is made by a blank line.

• If you start with a number, this sets the list type to <ol>. If you stay on the same level, it won't open a nested list (nor close this list level and return to an upper level list). Following items will just add a <li> (which has not type itself). Same applies if you start with a "*" and <ul> or "." and "ul none". (<--Thomas Waldmann)

I can see the need for these features, but that in no way invalidates the problems described here. There seems to be a clash of conceptual rules that needs to be somehow resolved. Some comments and questions: -- SteveDavison 2007-02-19 12:50:55

1. A basic rule of the markup is that a blank line (two newlines in a row) delimits a new paragraph. Allowing space between list items begs the question: does a list item constitute a paragraph?
2. Is it necessary to allow some list items to be single-spaced, and others double-spaced, within the same list? If not, an alternate method of specifying the list spacing could be performed once at the top, perhaps.
3. Does it make sense to embed a paragraph within a list by having a blank line before and after it? The blank lines are not necessary in order to achieve the embedded paragraph, and might be better interpreted as starting a new list?

4. While I think it's generally not common to end one list and begin another without some sort of "normal" paragraph in between, people are evidentally running into it (hence, this page). What is the official way to end one list and begin another? Inserting a comment seems to work fine, but in my mind that is a bug. What if someone wants to put a comment within their list without ending the list? That should be a normal and OK thing to do, but as the workaround proves, it will break the list. This is counterintuitive.

5. Any issues with switching between list types at the same level is in no way related to HTML markup. It is the wiki parser's job to recognize the transition, and do something more intelligent about it. I'm not sure yet whether best thing is to simply start a new list, or to embed the different-type list entry (maybe auto-indenting it).

6. These issues are pretty closely related to MoinMoinBugs/ParagraphBreaksBrokenWhenIndented

7. Personally, with all the inconsistencies involving indentation, lists, and paragraphs, I think it may be time for a re-think. Considering all the use-cases to be supported and all the available markup options could result in a more intuitive and less problematic markup.

Plan

• Priority:
• Assigned to:
• Status:

CategoryMoinMoinBug