I don't have any opinion about this one at the moment. Keep as an addition? -- MarioLenz
Wait a moment, I do have an opinion about indented paragraphs. From Creole 1.0/additions/Discussion: "Use '>' and not ':'. I don't see why both should be supported. Especially as the colon is proposed for use in definition lists." I agree and think this should be tidied up in 2.0. -- MarioLenz 2009-04-16 06:37:18
The question is, should there be markup for indentation (presentational), quotation, citation, pull quote, example, note, etc. (semantic) or some kind of middle ground like "emphasized paragraph"? From my own experience, it would be nice to have an e-mail-like quotations and a separate markup for emphasizing a paragraph -- leaving the exact way in which it is emphasized (indented, colored, framed, adorned with a picture, floated, set with a different font) to the style designer of the particular site, and leaving the exact meaning, the reason why it is emphasized (quote, example, note, warning, poem) to the context, mabe with a possibility to attach an optional formatting hint (class) to it. I agree that whatever we agree on, it should be added to the core. -- RadomirDopieralski 2009-04-16 18:32:23
I agree: Better remove indented paragraphs completely and define some "emphasized paragraph" markup. But I have some some problems with formatting hints: You'd have to specify them in the WikiCreole standard, otherwise they wouldn't be interoperable. -- MarioLenz 2009-04-17 07:55:57
The whole idea of hints is that they are not part of the data -- just some fluff to maybe make things look better. But I'm not very attached to the idea: people would probably abuse it for formatting just like they do with tables in MoinMoin. Plus it's a relatively advanced feature for a core wiki markup.
One way to handle all and any formatting hints would be to hash the hint's text into one of the available colors, in such a way, that different hints are likely to have different colors (or other presentation differences, of course, like borders or fonts or combinations of them). Then the hint is merely used to identify emphasized paragraphs with the same meaning, not the exact meaning of each paragraph. I'm not sure if it's really worth the effort though.
Defining keywords being a part of the specification would hurt non-English speakers and Creole language-neutrality, I think.
-- RadomirDopieralski 2009-04-17 15:00:09
I like MoinMoin's way to mark parts of the text to be used with different parsers:
{{{#!python
format this with the python parser
}}}What you're talking about would be something similar, probably:
+++FORMATTING Format this according to FORMATTING. +++
FORMATTING could be something like citation, hint, important, indented... If the engine doesn't know the given FORMATTING, it is simply ignored and the paragraph is displayed normally. What do you think? I used "+++" to demonstrate what I mean since three pluses shouldn't be too common. -- MarioLenz 2009-04-18 10:35:12
I'm worried about those:
+++例如 Lorem ipsum dolor sit amet... +++ +++Something Lorem ipsum +++Nested dolor sit +++ amet... +++ +++warning Please don't use English in this wiki. +++
There are also more questions to answer about any such markup:
- should it nest? how?
- should it be barce-like, like "{{{}}}" or prefix-like, like "> ..." e-mail quotes?
- should it span multiple paragraphs?
- should it be allowed inside a single paragrap, that is, without ending it?
- should it be allowed inside list items, tables, headings, links?
- what markup should be allowed inside?
- who gets to decide on which labels are available? Should they be standardized? If so, which language? Separate list per language?
- which characters are allowed inside those labels? what markup?
I don't have any ready answers to those, I think we should find a way to decide -- other than looking at it and saying "I like that". Find examples of usage of such things, maybe test it on live users, look for documentation on possible pitfalls and problems, etc.
MoinMoin has a similar feature, as you pointed out, so maybe we can look at how it's used on some MoinMoin wikis. Docbook also has "adminitions". Many newspaper sites have pull quotes. Maybe we can make a catalogue of common uses?
-- RadomirDopieralski 2009-04-18 16:46:26
Confluence uses macros to add "fluff":
{info}Lorem ipsum dolor sit amet blue{info}
{tip}Lorem ipsum dolor sit amet green{tip}
{note}Lorem ipsum dolor sit amet yellow{note}Note that Confluence macros can have bodies (unlike MoinMoin macros)
Interestingly, there is no {indent} macro (http://confluence.atlassian.com/display/DOC/Working+with+Macros)
-- StephenDay 2009-04-18 21:08:50
Agree that email-style (>, >>, etc) should be for quoting. This is commonly understood because of email, and compatible with at least Markdown.
MoinMoin's Creole implementation currently extends the {{{ markup thusly:
{{{
#!engine
stuff...}}}
-- Singpolyma 2009-08-06 00:08:50