| At line 1 added 48 lines |
| == Multiline List Items |
|
| === List items should be [[MultilineListItems|multi-line]] |
|
| * [[YvesPiguet]] |
| * [[JanneJalkanen]] - but this is not a showstopper for me. |
| * [[ChristophSauer]] |
| * [[OliverHorn]] |
|
| === List items should be single line |
|
| Use this option if you're conservative and don't want to change the existing specification, even if you personally prefer multiline list items. |
|
| === Undecided |
|
| Use this option if you'll support either decision, but don't have a strong opinion yourself. |
|
| * AlexSchroeder: I personally support multiline list items, but I acknowledge that introducing them might break existing wikis that want to introduce Creole. I'm secretly rooting for multiline list items, but I'm not sure this is the best decision for Creole. |
| * ChuckSmith: I like the idea of multiline list items, but I'm afraid of wiki engines using mixed mode and messing up formatting in current wikis which would adopt Creole. |
| * [[MarkWharton]] - Undecided until I have a chance to check some concerns. |
|
| == Escaping closing triple curly braces in nowiki |
|
| If you want to display a closing triple curly brace {{{ ~}}} }}} within nowiki, should it be done by putting a tilde in front of it, or by putting a space in front of it? See [[EscapingCurlyBracesInNowiki]]. |
|
| [[YvesPiguet]]: do you really want to bring this into question again? We had a solution working perfectly well, and using the tilde as proposed above **does not work** if we don't add other exceptions for escaping the tilde itself. |
|
| [[ChristophSauer]]: It is for documentation purposes. People should know that there was a second proposal, even if I will no longer push for it if I am really the only one. But Alex questions in the [[19 Jun Meeting]] encouraged me to bring that up again. |
|
| [[YvesPiguet]]: see also [[Talk.EscapingCurlyBracesInNowiki]] where JSPWiki examples show that tildes with reduced escaping power aren't obvious to design right (they seem to be broken to me) |
|
| [[OliverHorn]]: I'm against reopening this question again. Sure, escaping in nowiki is different, but isn't //no//wiki an exception anyway? |
|
| === Tilde === |
|
| * [[ChristophSauer]] |
| * Martin Junghans - This is necessary for both nowiki inline and block. IMHO a user who knows escape characters would expect this behavior. And a leading space should be everywhere else meaningless in Creole 1.0, as far as I know. |
|
| === Space === |
|
| * [[YvesPiguet]] |
| * [[MarkWharton]] - Space for preformatted block, greedy rule for inline nowiki. No escape characters inside preformatted/nowiki is the clearest solution. |
| * [[ChuckSmith]] |
|
| === Hate both options === |
|
| * [[JanneJalkanen]] - significant whitespace is always an issue; and having a non-generic escape character makes no sense. |
|
| At line 59 added 2 lines |
| * [[JanneJalkanen]] |
| * Martin Junghans |
| At line 66 added 2 lines |
| * AlexSchroeder: Currently I support both, but - requires a space and cannot be nested. Back to Creole 1.0! :) |
| * [[Michele Tomaiuolo]] |
| At line 74 added 7 lines |
| *Juan Carlos |
| * [[MarkWharton]] 75%: - It does not work as an addition. It should be core or nothing (i.e. meaning simple escape for preformatted block only). |
| * [[OliverHorn]] a generic escape mechanism is really needed and imho it belongs to the core |
| * [[ChristophSauer]] I don't care too much. Since I gave up on hyphens for lists, it does not need to be core anymore. But it would be a good to have it in the core anyway. |
| * [[ChuckSmith]] |
| * [[JanneJalkanen]] |
| * Martin Junghans - It is essential because it is not defined whether nowiki inline content generates monospaced text or not. |
| At line 25 changed 4 lines |
| - 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. |
| * Having the character specified, but optional, makes most sense to me, as it mainly applies to wikis that recognize raw (unbracketed) wiki words. [[AxelRauschmayer]] |
| * [[MarkWharton]] 25%: 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). |
| * AlexSchroeder: What for? Plus: We don't have a good candidate since \ is used as a path deparator by some operating systems, and ~ is used to designate the home directory on many other systems. Escaping WikiWords on many wikis uses ! instead of the proposed escape characters. For new users, disappearing ~ characters can be confusing. (This vote being an example.) |
| At line 30 removed one line |
|
| At line 96 added 3 lines |
| *Juan Carlos |
| * [[OliverHorn]] |
| * Martin Junghans |
| At line 102 added 4 lines |
| === Don't care, just pick something === |
|
| * [[JanneJalkanen]] |
|
| At line 112 added 8 lines |
| *Juan Carlos |
| * [[ChristophSauer]] if it helps making implementation easier |
| * [[OliverHorn]] the only way to go. I favor the following rule: The escape character (tilde) escapes the following single character if and only if that character is not a letter, a digit or whitespace. In any case, I'm strongly against escaping whole markup sequences because it does not seem useful with regard to additions (the escaping behavior would then depend on the set of markup supported by the wiki engine and could differ between different engines). |
| * AlexSchroeder: Escape character should display as-is inside nowiki and preformatted except when it appears before a nowiki or preformatted end-sequence. Escape character have no effect inside URLs such as http://www.epfarms.org/~alex/old-school-hex.pl. |
| * [[Michele Tomaiuolo]] |
| * [[ChuckSmith]] |
| * [[JanneJalkanen]] - this is easy to explain to the user. Alex's opinion, above, makes sense. |
| * Martin Junghans - it's easier for the users. I wouldn't ever try to escape an entire URI ;) |
| At line 49 removed one line |
|
| At line 52 changed 2 lines |
| - [[ChuckSmith]] |
| * [[ChristophSauer]] just had a discussion with chuck, I guess the spec is unclear here: of course if I want to escape large heading I do it like {{{~==}}} and not like this {{{~=~=}}} |
| * none |
.