It's a step in the right direction, but in my humble opinion is light on [courage|C2:XpCourageValue].

I think "{{{bold and italics should //be}}}" should be "{{{bold and italics should //be \\}}}". Otherwise, how is that line break supposed to get in there?

Is there any compelling reason to allow {{{\\}}} in the middle of a line, rather than requiring it to be at the end?

I don't think that a source linebreak in a list item should force a new paragraph - that defeats the ability to edit in a normal text editor without long lines.

It felt to me like we had broad consensus to require whitespace after bullets.

Also, some time soon, we need to take a hard, critical look at the incompatibilities with the current [Crossmark] draft spec.

-- RaphLevien 2007-01-10

The bold and italics markers are fine as they are right now as far as I'm concerned. Using \\ to force a linebreak is fine, but I would require it to be on the end of the line. Is it the intention that normal ENTERs should be ignored entirely?

To require users to put a space behind a bullet feels a little restricting. Also, it wouldn't be necessary if you only allow "**" to be recognized as a 2nd level list item if the list was already started.

I'd like a clarification on the use of the <<>> placeholder for "something advanced". Does this mean we could use the placeholder for macros or plugins? If so, a way to deal with parameters would be nice. Something like {{{<<plugin|parm1|parm2>>}}} or
{{{
<<plugin>>
parm1 
parm2
<<plugin>>
}}}
--MartijnVanDerKleijn, 10 jan 2007

I think the only compelling reason to allow line breaks in the middle of a line are for table cells.  I just explicitly added that line breaks are allowed in table cells.

-- [ChuckSmith], 2007-Jan-11

I'd like to add an argument to reverseing the link syntax from {{{[url|description]}}} to {{{[description|url]}}} as our experience from writing large texts in Wikipedia Syntax is that long links make the wikipedia syntax almost completely unreadable and quite hard to work with otherwise. -- Martin Häcker, 12 Jan 2007

I added your proposal to [[AlternateLinkSyntaxProposal]] along with advantages and disadvantages.

-- [[ChuckSmith]], 2007-Jan-17


I would suggest to distinguish left and right-align text in table cells, like:
{{{|left-aligned  | centered |  right-aligned|}}}
No new markup syntax is necessary and it's quite intuitive.

-- JoachimStolberg 2007-Jan-23

I agree with Martijn, a multiline version of placeholder would be very useful. I'd suggest the following syntax:
{{{
<<< org.domain.app
arbitrary data
>>>
}}}

It could be filtered by interpreters like PHP and Sysquake Remote and used for applications similar to
[[http://en.wikipedia.org/wiki/Mathematica|Mathematica]] notebooks or
[[http://en.wikipedia.org/wiki/Literate_programming|literate programming]], where code is mixed
with text. With globally unique identifiers, multiple filters could be applied without conflicts.

-- [[YvesPiguet]], 2007-Jan-24

Why not just use {{{<<anything goes>>}}}? I mean, you can put newlines inside the placegolder -- the only "forbidden" sequence is ">>". OTOH, I always understood that a placeholder would only hold something like {{{<<1>>}}} or a MD5 hash of the content, or something like that -- and the rest is remembered by the engine.

Maybe we should take care of preparing some recommendations for non-Creole syntax? But that can wait for when we have the core fairly stable.

On a second thought, maybe we should remove the placeholder from the spec too and leave it as a recommendation?

-- RadomirDopieralski, 2007-01-24