| At line 1 added 4 lines |
| <<ALLOW edit Admin>> |
| <<ALLOW view All>> |
| [[UnlockMe]] |
|
| At line 225 added 130 lines |
| Maybe there is a better way to unambiguously show parsed structure without suggesting any particular markup? Two solutions come to my mind, one is a parse tree and the other is an XML-ish markup, with tag names different than those of (X)HTML, e.g. {{{<underlined>}}}. Both can be confusing, though. |
|
| -- [[Radomir Dopieralski]], 2007-Jan-13 |
|
| For blockquote I would recommend simply: |
| {{{ |
| " To be or not to be, that is the question |
| }}} |
| which would be the same as: |
| {{{ |
| " To be or not to be, |
| That is the question |
| }}} |
| Basically, reuse the syntax rules from lists and dictionaries. All that changes is the token. |
|
| For an inline quote: |
| {{{ |
| ""just use two tokens instead"" |
| }}} |
|
| -- [[StephenDay]], 2008-Feb-24 |
|
| Is it possible to separate "official" additions (such as {{{##}}} which is required for engines which don't render inline nowiki as monospace, and basically everything which was there when Creole 1.0 was adopted) from ongoing discussions such as quotes? |
|
| -- [[YvesPiguet]], 2008-Feb-26 |
|
| Since I haven't got any feedback, I'll do it. I'm moving discussion from [[Creole Additions]] to below. |
|
| -- [[YvesPiguet]], 2008-Feb-29 |
|
| //Monospace// |
|
| :Note that tt is a deprecated XHTML tag, XHTML 1.1 doesn't support this! {{{ This is <span class="mono">monospace</span> text. }}} is better, but is still not a very good idea. Since **class** is used for describing **structure** //not// **presentation**. Usually monospace is used for code. So it's no use of using ##monospace## since we already have inline ~{{{ and ~}}}. |
|
| //Definition lists// |
|
| Sometimes we want to use colon (:) in the term, requiring ~~ to quit is inconvinient. Also, |
|
| {{{ |
| ; term: some definition |
| beginning the same line. |
| }}} |
|
| is hard to read in source. Usrs usually cannot distinct terms and descriptions at a glance. |
|
| So I suggest that descriptions (or definitions) //must// begin on a new line beginning with a colon. |
|
| {{{ |
| ;term1 |
| :description1 |
| ;term2 |
| :description2 |
| }}} |
|
| And sometimes we may need one term with multi-definitions: |
|
| {{{ |
| ;E. M. A. C. S. |
| :Emacs Makes A Computer Slow |
| :Escape Meta Alt Control Shift |
| :Emacs Makers Are Crazy Sickos |
| }}} |
|
| //Inline quote// |
|
| {{{ |
| He said, ''Suddenly I was enlightened!''. |
| }}} |
|
| The recommended XHTML |
|
| {{{ |
| <p>He said, <q>Suddenly I was enlightened!</q></p> |
| }}} |
|
| '' is easy to type. :) |
|
| //Blockquote// |
|
| """ should begin at the first column at a new line, and should be on a line by itself to open and close blockquote. |
|
| {{{ |
| """ |
| a simple blockquote |
| """ |
| }}} |
|
| The recommended XHTML |
|
| {{{ |
| <blockquote><p>a simple blockquote</p></blockquote> |
| }}} |
|
| -- [[WeakishJiang]], 2008-Feb-26 (moved here by [[YvesPiguet]] on 2008-Feb-29) |
|
| Some replies: |
|
| * XHTML for monospace: all XHTML snippets are for illustration only, to make the Creole markup description clearer. They shouldn't be considered as recommendations. I suggest to add a note to that effect in the next revision of Creole. Why some of us consider useful to separate inline nowiki from monospace has already been discussed elsewhere. |
| * Definition lists: the current addition is in agreement with mediawiki. Constraining too much the Creole syntax for aesthetics reasons has been rejected in other cases such as lists. Multiple definition paragraphs are fine. |
|
| -- [[YvesPiguet]], 2008-Feb-29 |
|
| Allowing unnecessary flexibility where it is not really used leads to monsters like the arcane list rules. |
|
| -- [[RadomirDopieralski]] |
|
| Ok, I'm not against discussing definition lists. But I assumed implementers could pick additions which suited them. If additions are changed by newcomers after having been implemented and used by early adopters, we can as well ignore them entirely. |
|
| [[Nyctergatis|NME]] implements all current additions but alternate link syntax, and that's going to stay. |
|
| -- [[YvesPiguet]], 2008-Mar-2 |
|
| That's the risk of early adopters, isn't it? |
|
| I also don't like "ad hominem" arguments like this (about newcomers)-- let us judge the value of ideas by how well they suit Creole goals and how well argumented and documented they are, not by who submits them. |
|
| -- [[RadomirDopieralski]], 2008-Mar-05 |
|
| I didn't want to offend anybody and I apologize if I did. I'm glad if new visitors come, discuss, contribute to and improve Creole and its adoption. What made me react was changes made without prior discussion to a page which serves as the reference for features implemented in several engines, not only mine. |
|
| -- [[YvesPiguet]], 2008-Mar-5 |
|
| I know you didn't mean to offend, sorry for overreacting. Maybe there should be a separate CreoleAdditionsSpecDraft page, so that we can work on the addtions here? Or even better, one page per addition, for example the *Proposal pages? Maybe we should even |
| version them? |
|
| The "talk" link is not visible for new visitors, and one of the wiki rules is "be bold" - so please don't be annoyed. |
|
| As a side note, forcing a "discussion" (or, in wiki jargon, "thread mode") is a very clunky way of working on a document and kind of defeats the whole idea of a wiki. I know that wikipedia somehow manages to work this way, but it's hard for me. It was disturbing me from the start (although I wasn't really aware of it). Of course, I'm not going to start to pressure for a change, but I'm curious about experiences and thoughts of others in this. |
|
| --[[RadomirDopieralski]], 2008-Mar-6 |
.