(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-2) was last changed on 13-Jan-2007 07:21 by Eric Chartre  

This page was created on 29-Dec-2006 07:30 by null

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 3 changed one line
A little bit about me. My first language is French so, sorry if my English sounds a little weird from time to time. I work as a software architect/lead developer for a large telecommunication company in Canada (my opinions expressed on this Web site are my own). I also have a broad experience with software usability.
A little bit about myself. I work as a software architect/lead developer for a large telecommunication company in Canada (my opinions expressed on this Web site are my own). I also have a broad experience with software usability.
At line 5 changed one line
I've been a very heavy user of wikis for the last 7 years mainly for internal projects - my team documents all of our software development in wikis (FlexWiki, MediaWiki, TWiki, TikiWiki, TRAC, XWiki, etc.). I'm also working really hard to install and implement wikis in my clients' organizations especially in their software development environments.
I've been a very heavy user of wikis for the last 7 years mainly for internal projects - my team writes all of our software development documents in wikis (FlexWiki, MediaWiki, TWiki, TikiWiki, TRAC, XWiki, etc.). I'm also working really hard to install and implement wikis in my clients' organizations especially in their software development environments.
At line 7 changed one line
One of my goal, is to find, someday that we use, as humans, only one type of markups to write text quickly and efficiently for blogs, wikis, newsgroups, emails, readme files, ... The SGML family is great for structured or semi structured documents/data but it sucks when you have to write plain old text files with formatting by hand.
One of my goal is that humans use only one type of markups to write text quickly and efficiently for blogs, wikis, newsgroups, emails, readme files, ... The SGML family is great for structured or semi structured documents/data but it sucks when you have to write plain old text files with formatting by hand.
At line 9 changed one line
So, to give back to the community, I would really like to contribute to this wonderful effort.
So, to give back to the community, I want to contribute a little to this wonderful effort.
At line 11 changed one line
If you want to contact me personally, you can write me at "first letter of my first name + full last name at g mail dot com (no spaces, no plus sign)".
If you want to contact me personally, you can write me at echartre at gmail dot com
At line 15 changed one line
What I like about Creole is that it could be the One Ring to Rule Them All (just kidding)! Seriously, with the broad support from wiki developers, it could be this spec that makes the unification possible in the long run. If we could get OLPC involved (http://wiki.laptop.org/go/Crossmark), it would be another great asset.
What I like about Creole is that it could be the One Ring to Rule Them All (just kidding)! Seriously, with the broad support from wiki developers, it could be this spec that makes the unification possible in the long run. If we could get OLPC involved ([CrossMark]), it would be another great asset.
At line 19 changed 10 lines
My general position is to keep the standard as simple but as rich as possible for the user, two goals that are somewhat opposite, while minimizing the effect on existing WikiMLs. It should allow for a variety of writing styles so it can be accepted quickly. For example:
* {{{__}}} , // and ** should be accepted for emphasis letting the [[language-dependant] implementation decides of the rendering.
* There should be a way to specify table headings because it has more semantic meanings than formatting.
* Markup extensions should be standardized (<<placeholder>> is a good start), allowing qualities on markup such as:
{{{
|<<special style for cell/row/column>>R1C1|R1C2|
==<<special style for heading>> Heading 2 ==
}}}
* There should be a difference between preformatted text and multiline quoted text (emphasis with indentation perhaps?)
* An Escape character... Please, please...
My general position is to keep the standard as simple but as rich as possible for the user, two goals that are somewhat opposite, while minimizing the effect on existing WikiMLs. It should allow for a variety of writing styles so it can be accepted quickly.
At line 21 added one line
----
At line 23 added one line
I will express my opinion about [NotNew] in the next couple of days...
At line 25 added 67 lines
So, after reading all of the discussions and proposals, this is what I think:
!!!Proposals (differences with [Creole0.4])
# Except in preformatted/No Wiki, a Tab, form feed or vertical feed is treated as a space
# Except in preformatted/No Wiki, spaces at the beginning and at the end of a line are ignored
# Except in preformatted/No Wiki, two or more consecutive spaces are treated as one space only
# The different types of emphasis are dependent on the rendering
# In Headings, allow for both {{{=}}} and {{{!}}} (not mixed though), {{{!}}} at the end are taken literally
# In Headings, allow for parsing of character markups (see below)
# In Headings, allow for spaces before and after the markup
# In Headings, any number of {{{=}}} at the end of the line (with or without subsequent spaces) are ignored if the heading starts with {{{=}}}
# For unordered lists, allow for both {{{*}}} and {{{-}}} (not mixed though)
# In Quoting, allow for both {{{"""}}} and {{{:::}}} (not mixed though)
# For Horizontal lines, allow for any number of {{{-}}} equal or greater than 4
# Table headings should be usable for row and column headings
# In tables, spaces before or after the markups are ignored
# All Paragraph markups except for Headings can be used in block markups (except in Preformatted where they are taken literally)
# All Paragraph markups except for Heading and Block markups can be used in Table
# New markup: Continue numbering in ordered lists ({{{#^}}})
# New element: Ordered headings
# New element: Centered line
----
!!!Markup categories
!!Character markups
||Element||Markup
|Emphasis|{{{**text**}}} \\ {{{//text//}}}\\ {{{__text__}}}
|Superscript|{{{^^superscript^^}}}
|Subscript|{{{,,subscript,,}}}
|Inline preformatted|{{{{{{text}}}}}}
|Inline quoting|{{{:::text:::}}} or {{{"""text"""}}}
|No wiki (escape)|{{{\character}}}
!!Paragraph markups
||Element||Markup
|Headings|{{{= Level 1 =}}} or {{{!Level 1}}} \\ {{{== Level 2 ==}}} or {{{!!Level 2}}} \\ {{{=== Level 3 ===}}} or {{{!!!Level 3 }}} \\ {{{==== Level 4 ====}}} or {{{!!!!Level 4}}} \\ {{{===== Level 5 ====}}} or {{{!!!!!Level 5}}}
|Ordered Headings|{{{=# Level 1 =}}} or {{{!#Level 1}}} \\ {{{==# Level 2 ==}}} or {{{!!#Level 2}}} \\ {{{===# Level 3 ===}}} or {{{!!!#Level 1}}} \\ {{{====# Level 4 ====}}} or {{{!!!!#Level 4}}} \\ {{{=====# Level 5 ====}}} or {{{!!!!!#Level 5}}}
|Unordered Lists|{{{* Item 1}}} or {{{- Item 1}}} \\ {{{** Item 2}}} or {{{-- Item 2}}} \\ ... (4 levels max.)
|Ordered Lists|{{{# Item 1}}} \\ {{{## Item 2}}} \\ {{{#^ Continue numbering level 1}}} \\ {{{##^ Continue numbering level 2}}} \\ ... (4 levels max)
|Line breaks|{{{\}}} at the end of a line (with or without subsequent spaces)
|Paragraph breaks|Two new lines or {{{\\\}}}
|Centered line|{{{>> Text}}}
!!Block markups
||Element||Markup
|Quoting|{{{"""}}} \\ {{{Quote}}} \\ {{{"""}}} \\ or \\ {{{:::}}} \\ {{{Quote}}} \\ {{{:::}}} \\ Markup must be by itself on a line (with or without spaces)
|Preformatted|{{{ {{{ }}}\\ {{{Preformatted}}} \\ {{{ }}} }}} \\ Markup must be by itself on a line (with or without spaces
!!Table markups
||Element||Markup
|Tables heading|{{{|= Row/column heading}}}
|Table cell|{{{|Cell}}}
|Cell span|TBD
!!Special objects markups
||Element||Markup
|Images|{{{{{my image}} }}} \\ Images can be used instead of a description in a link
|Links|{{{[[Description|Link]]}}} \\ The Link part is optional
|Horizontal lines|{{{----}}} \\ Any number of {{{-}}} equal or greater than 4
!!Extension markups
||Element||Markup
|Placeholder|{{{<< Placeholder >>}}}
|Element quality|TBD
Version Date Modified Size Author Changes ... Change note
2 13-Jan-2007 07:21 5.618 kB Eric Chartre to previous Huge update, rant, differences with Creole0.4 and Markup Categories
1 29-Dec-2006 07:30 2.73 kB null to last
« This page (revision-2) was last changed on 13-Jan-2007 07:21 by Eric Chartre