(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Unnumbered List Markup: (- or *)#

Character should be -, Accept HyphenListMarkupProposal#

Character should be *, don't specify space after bullet #

Remark: This will set back the spec on this element to 0.5

AxelRauschmayer: Christoph aren't you the guy who suggested the hyphen as list markup? Are you now against it?
ChristophSauer: Axel, actually I was, but too many people are against it and for the sake of a consensus I gave it up. Maybee you think about it and add your vote to "Is indifferent".

Is indifferent about * or -#

  • ChuckSmith: while I think the hyphen is easier to read, it will be much easier to implement Creole in existing wikis if the star is used, since practically all wikis have it, so for me it's a toss-up, although I do feel responsible for not implementing the hyphen as the WikiSym workshop had recommended

Accept Escape character as core element (Y or N)?#

Escape character should be core#

Escape character should be addition#

  • Having the character specified, but optional, makes most sense to me, as it mainly applies to wikis that recognize raw (unbracketed) wiki words. AxelRauschmayer
  • I think some developers would be willing to put the work to make it parsable without the escape character, but the escape character throws in too many potential problems. I think it should be optional. As for not being able to write the spec without it, one could you the space or tilde just before the closing curly braces. This is the only escape character that is truly required imho. ChuckSmith
  • MarkWharton: Preformatted escaping (i.e. ~}}}) should be the minimum requirement, full text escaping (i.e. across all the text, not just inside preformatted) should be addition. My only concern is that external links containing ~ become "spoiled" when moving between engines that do/don't support full text escaping. To address that, I'd suggest making external links an exception and not escape them, rather than escape whole Creole markup sequences to avoid the issue (as I understand it).
  • ChristophSauer I don't care too much. Since I gave up on hyphens for lists, it does not need to be core anymore.

Escape character (~ or \)?#

Escape character should be ~#

Escape character should be \#

What is escaped by escape character#

Escape character should escape a single character#

Escape character should escape whole Creole markup sequences#

Add new attachment

Only authorized users are allowed to upload new attachments.

« This particular version was published on 02-Mai-2007 14:16 by ChristophSauer.