(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-45) was last changed on 26-Sep-2007 08:56 by ChuckSmith  

This page was created on 11-Apr-2007 10:38 by ChuckSmith

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 9 changed one line
-[[ChristophSauer]]: **strongly** avoids conflicts with bold, since using bold at the beginning of lists is not an edge case; intuitive - first guess of endusers; [[not new]]; choice of the vast majority at [Participants at the WMS Workshop, Wikisym 06|People]; singnature/horzontal rule conflicts are easier to solve then conflicts that are introduced by asterisk since space after bullet is not an option.
-[[ChristophSauer]]: **strongly** avoids conflicts with bold, since using bold at the beginning of lists is not an edge case; intuitive - first guess of endusers; [[not new]]; choice of the vast majority at [Participants at the WMS Workshop, Wikisym 06|People]; signature/horizontal rule conflicts are easier to solve then conflicts that are introduced by asterisk since space after bullet is not an option.
At line 12 added one line
-AlexSchroeder: I've seen people use it; but this causes problems if multiple dashes amount to an indented list item, because some people like to sign {{{-- AlexSchroeder}}} at the end of their contribution.
At line 18 added 2 lines
-AlexSchroeder: Why discard something that works?
*[[YvesPiguet]] less common than hyphens in plain text, no conflicts with signatures and rules
At line 31 added one line
-AlexSchroeder: With an asterix, this eliminates the confusion with simple emphasis often used in plain text, whether the wiki renders it bold or not. Putting a bold word at the beginning of a line only to see it turn into a list item is strange. With a dash, this eliminates the confusion with an ordinary quotation dash used to intrudce a signature. Otherwise a signatures like {{{-- Alex}}} will turn into a list item containing {{{- Alex}}}. That's too surprising.
At line 38 added 3 lines
-[[AlainDésilets]]: **strongly**, for the same reasons exposed by [[ChristophSauer]]. To which I would add that in my empirical observation of wiki users, I saw many of them type a space after the asterisk, and about as many of them type no space after the asterisk.
-[[JaredWilliams]]: Don't see why its necessarry just for disambiguation.
* [[YvesPiguet]] most common, provided disambiguation with bold is clearly defined.
At line 43 changed one line
-[[ChristophSauer]]: **weakly** there should be unified way for parser developers that want to simplify escaping, but it should be optional, since I agree that escaping is hard to understand for endusers. Also it's not Creoles goal to add new markup, that was not there in other engines. Therefore I opt for escape as an addition - a suggestion to solve a certain problem in an more elegant way than using nowiki.
-[[ChristophSauer]]: there should be unified way for parser developers that want to simplify escaping. Escape character should be in the core. Without the escape character (be it \ or ~) I feel that the spec is not "round" - we are not giving answers to obvious questions.
At line 52 added 2 lines
-[[JaredWilliams]]: **weakly**.
* [[YvesPiguet]] strongly, much cleaner than triple-braces in some cases. Must be simple, which is very easy.
At line 60 added one line
--[[GregorHagedorn]]: It is a question of coexistence. As long as Creole is intended to work in mixed mode, many Wikis will add CamelCase as native markup. It would be good if Creole users already had a method to react. Better than any Wiki having a different solution for this - then very frequent - case. But as Christoph says, this could be "optional" markup.
At line 62 added one line
-AlexSchroeder: What for? Plus: We don't have a good candidate since \ is used as a path deparator by some operating systems. All proposals are very complicated.
At line 55 changed one line
== Escape character (~ or \)?
== Escape character (~~ or \)?
At line 57 changed one line
=== Escape character should be ~
=== Escape character should be ~~
At line 72 added one line
* [[YvesPiguet]] weakly (backslash also possible if defined cleanly)
At line 65 changed one line
-[[Michele Tomaiuolo]]: **weakly**, it would one character less in syntax, and easier to type on many keyboards. It could also made compatible with forced linebreaks.
-[[Michele Tomaiuolo]]: **weakly**, it would one character less in syntax, and easier to type on many keyboards. It could also made compatible with forced line breaks.
--[[Gregor Hagedorn]], "make it compatible with forced line breaks": I wonder how? Can you explain or link if already discussed?
--[[Michele Tomaiuolo]]: backslask-backslash = linebreak; backslash-space = backslash (this is being proposed for tilde also: tilde-space = tilde). See [[Escape Character Proposal]]
-[[JaredWilliams]]: generally excepted escape character almost everywhere else.
At line 76 changed one line
-[[MarkWharton]] behavior remains consistent - simple placeholders could be used for inline plain-text nowiki\\For example: this could be how to show {{{<<**>>}}} no wiki type {{{<<//>>}}} characters and text, etc.\\i.e. Placholders which cannot resolve to a plugin display their text content inline
-[[MarkWharton]] behavior remains consistent - simple placeholders could be used for inline plain-text nowiki. For example: this could be how to show {{{<<**>>}}} no wiki type {{{<<//>>}}} characters and text, etc., i.e. Placeholders which cannot resolve to a plugin display their text content inline
--[[Gregor Hagedorn]] (On [[Generic Extension Element Proposal]] the opposite requirement was raised, to make sure that a non-recognized plugin does //not// become [[Invisible Markup]])
At line 98 added one line
* [[YvesPiguet]] strongly
At line 127 added one line
* [[YvesPiguet]] strongly
At line 132 added 2 lines
-AlexSchroeder: I use a variant of nowiki that renders as monospace, and I'm happy with it. No separate solution required.
-ChristophSauer: Like Alex: nowiki that renders as monospace, I am happy with it. Wiki markup should be simple. Common things people need. Less choice is better.
Version Date Modified Size Author Changes ... Change note
45 26-Sep-2007 08:56 13.328 kB ChuckSmith to previous restore
44 26-Sep-2007 00:52 13.342 kB 219.138.204.162 to previous | to last
43 24-Apr-2007 20:25 13.328 kB ChristophSauer to previous | to last escape characters should be core.
42 23-Apr-2007 17:42 13.469 kB YvesPiguet to previous | to last minor precision
41 23-Apr-2007 00:44 13.455 kB YvesPiguet to previous | to last Yves' opinion
« This page (revision-45) was last changed on 26-Sep-2007 08:56 by ChuckSmith