.
Talk.Creole0.6 seemd to indicate that it wouldn't be a good idea to make the escape character an addition. That's still my opinion.
I have difficulty in understanding how the decision process works, especially since last week.
-- YvesPiguet, 2007-Apr-9
Isn't embedding the style directly in the generated (x)html a mark of bad, uhm, style? I mean, it should be <div class="mail-quote"> rather than <div style="some arbitrary presentation that might not fit the overall style of the site">. Then again, there is the question of users using browsers that are not CSS-enabled -- they should at least see that they are missing something.
I think that the spec should show a "good" solution, or just don't show any at all if no good solution exists. I see several possibilities:
- only say that the text should be rendered as indented,
- only say thet the text should be marked as a quotation, in any way, not necessarily by indentation (some styles might use colors or colored bars),
- generate the quted parts as a blockquote (with a class),
- generate the quoted parts as a single-element, unordered list with special class for styling (with a class),
- generate the quoted parts as a single-element definition list with empty 'term' part,
- generate the quoted parts as a div, but with the '>' left in the text, and removed with style,
All of these solutions have their pros and cons, as far as I can tell none is 100% "correct".
-- RadomirDopieralski, 2007-06-12
The examples are just a possibility of how the markup could be represented. Developers have to decide for themselves which way would make most sense for their situation.
-- ChuckSmith, 2007-Jun-12
I've replaced "recommended" with "possible" for the XHTML with embedded style. Maybe this should be done everywhere. I agree that embedded style isn't very nice; however, the simplest, shortest rendition is sometimes more informational than clean output following W3 advices, which recommends against <i> and <b>.
-- YvesPiguet, 2007-Jun-12