| At line 3 changed one line |
| In the meantime, the simple escape mechanism proposed here for preformatted blocks, I believe, is both adequate and safe. If we don't end up with an escape character then this is the best alternative, without a doubt. Having said that, I will endeavour to work through my escape thinking over the next few weeks and input into any escape arguments. |
| In the [[meantime]], the simple escape mechanism proposed here for preformatted blocks, I believe, is both adequate and safe. If we don't end up with an escape character then this is the best alternative, without a doubt. Having said that, I will endeavour to work through my escape thinking over the next few weeks and input into any escape arguments. |
| At line 607 added 57 lines |
|
| In front of something which is converted automagically, such as a URL (but not explicit markup), it prevents the conversion. Elsewhere (except in nowiki, preformatted and inside URL, or in front of a blank), it escapes a single character. |
|
| -- [[YvesPiguet]], 2008-04-04 |
|
| The EscapeCharacterProposal is somewhat different from the final spec. I don't like ~~ in URLs be considered escapes. They are common in user URLs and there is no need escaping a character that is not considered special by Creole. |
|
| * {{{http://example.org/~user/}}} -> http://example.org/~user/ |
|
| On this Wiki, ~~ escapes the URL, but the URL is parsed as inline text: |
|
| * {{{~http://example**.org**/~user/}}} is rendered ~http://example**.org**/~user/ |
| * {{{~http://example//.org///~user/}}} is rendered ~http://example//.org///~user/ |
|
| Another test; Creole formatting inside URLs: |
|
| * {{{http://example//.org///~user/}}} -> http://example//.org///~user/ |
| * {{{http://example**.org**/~user/}}} -> http://example**.org**/~user/ |
|
| -- [[LarsChristensen]], 23-May-2008 |
|
| Please don't consider what this wiki is doing to be "the final spec". The implementation isn't perfect. You've pointed out a few deficiencies here for sure. Tildes in urls are fairly common and Croele should treat them as any other character. |
|
| [[http://werkzeug.pocoo.org/e/simplewiki/tildes_in_urls|This wiki]] uses Creole and it does a better job with your tests. ;) |
|
| -- [[StephenDay]], 23-May-2008 |
|
| = Example with two opening braces? = |
|
| The current (12-May-2008) page gives the following example for inline NoWiki markup: |
|
| {{{ |
| {{if (a>b) { b = a; }}} |
| }}} |
|
| There are only two opening braces. Is that intentional? |
|
| -- [[Ben Kovitz]], 12-May-2008 |
|
| The parser is having trouble with this. There should be three opening braces and four closing ones. |
|
| An admin needs to unlock the page to fix it (or add a comment that it is not displaying correctly). |
|
| -- [[StephenDay]], 13-May-2008 |
|
| Thanks for the clarification. I'm implementing the ~{{{ just as a token, and not bothering trying to match up braces inside the Nowiki text with any braces that occur before the ~}}} appears. |
|
| -- [[Ben Kovitz]], 13-May-2008 |
|
| == Use of TT tag for representing code |
| For code rendered using the {{{{{{ }}}}}} technique, would it not be better for the markup to be <code></code> tags rather than <tt></tt> tags, as the former gives semantic meaning and allows the browser to choose an appropriate font, wheras the latter is simply a display tag? |
|
| -- M1ke, 18-May-2008 |
|
| Creole doesn't specify that <tt></tt> be used, it's just a suggested implementation. <code> could be used, as could <span>, or no markup at all (or whatever). |
|
| -- [[StephenDay]], 18-May-2008 |
.