Alex Schroeder

I started Emacs Wiki, I run Community Wiki, I maintain Oddmuse, and I have a blog.

When I implemented the Oddmuse extension for Creole Markup, I added notes to all the talk pages where I felt the next revision of the recommendation should be more precise.

My position statement on Creole 0.3:

• Not happy with simple tables, because we're picking the least popular variant, and introducing extra markup for headers and linebreaks inside cells.

My position statement on Creole 0.2:

• **bold** and //italics// -- supported, including nesting and spanning lines but not paragraphs.
• * unordered lists -- supported, but requiring a space after the * should part of the recommendation so that people can start paragraphs with bold words. That would be much better than the special case introduced. http://www.wikicreole.org/wiki/Creole0.2#section-Creole0.2-Lists (CS: We agreed at the workshop not to require spaces, because many users do not put a space after a bullet.)
• # ordered lists -- supported, but requiring a space after the # should part of the recommendation for consistency with the unordered list markup.
• Nested lists are usually not needed except for table of contents and other sort of dynamically assembled hierarchical data; repeating the list item character is not intuitive, using whitespace intuitive. Mixed nested lists add to the difficulties. (CS: Kept nested lists (sublevels of lists) in 0.1, but removed mixed lists (i.e. mixing ordered and unordered lists in one structure) from Creole 0.1. Will continue discussion for Creole 0.2.)
• List items can span lines but not paragraphs. Empty lines between list items is are allowed.
• == headings -- supported, but the recommendation should only require three different different heading levels. More levels should be optional. (CS:Good idea! Added your recommendation to Creole 0.1.)
• [[links]] -- supported.
• {{image}} / {{image|text}} -- supported.
• Paragraphs, linebreaks -- supported.
• ~{{{Preformatted & unprocessed}}} -- supported as follows: If the opening triple braces start on the first column, open a pre block. It is closed by closing triple braces starting on the first column. Any other opening triple braces open a code element. They are closed by tripple braces.
• ---- -- supported.
• <<x>> -- irrelevant.

Thanks for all your hard work! --Chuck Smith (CS)

Some comments by Martin Budden:

1. I agree with Alex's point that a space after the * for unordered lists should be part of the recomendation. A simple rule makes things easier for users, even if it means they initially have to remember to put a space after the *. I've noticed that most users tend to do this anyway.
2. Likewise for ordered lists.
   • Martin Budden 2006-12-06