Wiki Creole wish list

This page is intended to discuss and clarify Creole markup as it pertains to the Hatta implementation.

Please note that work on Creole itself and things not specific to Hatta should happen on the Creole sites – on the wiki or on the frozen site (maybe contact that site's admins to discuss it).

Improve this page… Its your Wiki too!

The Wiki Creole conventions, goals and strategy are desirable and practical. Many aspects of Creole are not specified by the designers. The objective was to identify and rationalize those aspects of Wiki markup which might gain broad acceptance. This was a conscience decision and reasonable compromise, because the Wiki landscape is so varied and dynamic.

Creole sites:

• Official site, now frozen
• Creole 1.0 (current) specification
• About possible future development
• Editable wiki for feedback and development

The wikicreole site should be probably reviewed for conventions, proposals, discussions and decisions. Conflicts with this page should generally be resolved in favor of the official wikicreole web site.

Discussion is also encouraged for markup extensions beyond Creole 1.0, since its an evolving standard. If the ideas have merit, they should be propogated to the official wikicreole site for further review.

Priority scale for opinions below:

• Critical (essential for Hatta adoption)
• High (very important for my usage)
• Medium (desirable, would use it routinely)
• Low (not important for my usage)
• Harmful (detrimental to Hatta adoption)

Lists:

• Option white space prefix
  • Implemented already
• Numbered items:
  • Example: # Item with auto-numbering.
  • Implementation pending as of 2009-10-15
    • Opinion (2009-10-15 RLS): Medium [1]
• Multi line items:
  • Example: * Item... newline. item continued
  • Issue: continuation character prefix (like ":")? [3]
  • Implementation pending as of 2009-10-15
    • Opinion (2009-10-15 RLS): Low [2]
• Multi paragraph items:
  • Example: * Item... 2 newlines. item continued
  • Issue: continuation character prefix (like ":")? [3]
  • Implementation pending as of 2009-10-15
    • Opinion (2009-10-15 RLS): Low [2]

Links:

• Links within pages:
  • Example [[#target]]
  • Example [[#target|text]]
  • Example [[page#target|text]]
  • Implementation pending as of 2009-10-15
    • Opinion (2009-10-15 RLS): Medium [1]
• Explicit anchors within page:
  • Example: proposal needed for target of "#name".
    • Opinion (2009-10-15 RLS): Medium [1]
• Footnotes:
  • Example: [#] or [#3] or [#name] Auto num or explicit num or symbolic num.
  • If specified at the beginning of a line, its an anchor which is implicitly rendered at the bottom of the page.
  • If specified after some text, its a link to an anchor (which may be marked up near the link).

Headings:

• H1 heading at top of page:
  • Example: proposal needed for explicit H1 heading

Tables:

• Headings
  • Implemented already
• Forced line breaks within cells
  • Implemented already
• Table alignment within page.
• Text alignment within cell.
• '|' breaks table layout, as in [[foo|bar]]
• Row span.
• Column span.

Code syntax highlights:

• { { { …mono-text… } } } (without the blanks).
  • Implemented already
• { { {#!css …mono-text… } } } (without the blanks).
  • Implemented already
• { { {#!css+php …mono-text… } } } (without the blanks).
  • Broken? … needs RegEx tweak?

[1] Useful. Well defined. Widely used. Moderate cost.

[2] Perhaps useful. Sporadically implemented. Moderate cost.

[3] Continuation character prefix (like ":"), example list markup:

Example list caption:
  * Item A (conventional)
  * Item B (continued), ending with newline.
    : Item B continuation in the same paragraph.
    :
    : Item B continuation in another paragraph.
  * Item C (conventional)
  Preformatted text, such as this, without any prefix terminates the list.
Regular text, such as this, without any prefix also terminates the list.

I see the original author of this page is not going to do anything with it, so I guess I will just delete the empty promises. – Radomir Dopieralski