I strongly second the proposal, important separation of issues.
Being aware that Creole currently has a weak position about nested formatting: I would vote for being able to have emphasized parts within monospace programming code! It does help discussions to be able to highlight within a bigger, emphasized part.
-- Gregor Hagedorn - 2007-03-14
I also support the proposal.
Not sure if that's what Gregor means, but I wouldn't like markup in preformatted blocks. Or it should be a second kind of preformatted blocks. Otherwise, normal program listings would require way too much escaping.
-- YvesPiguet, 2007-Mar-16
So, it would be something like this:
This is normal text ##this is monospaced with a [[link]] and **emphasis**##. This is {{{[[not a link]]}}}, ##{{{this is monospaced nowiki}}}##, but: {{{ /** this is a normal comment, without any emphasis **/ # this is a comment int main() {{{ z = "//this is not italic text//" }}} }}}
So, a preformated block is something different than ##monospace## font. To have formatting within a monospaced block of text, one has to use normal text:
## int **main**() {{{{{{}}}\\ z = "''this is italic text''"\\ {{{}}}}}} ##
Note, that engines can extend the preformated block to inlcude coloring/fomratting of the code -- actually that's what I do in the MoinMoin parser:
{{{ #!perl some colored perl code }}}
But maybe the <<<...>>> or other special markup should be used for that? The current approach has an advantage of graceful degradation...
-- Radomir Dopieralski, 2007-Mar-2007