(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]


The original goals of creole were developed at WikiSym2006. and included goals which conflict with the generation of a clear specification such as a requirement to be CollisionFree,which implicitly suggests Creole is not so much a specificatiion of a form of wiki markup but is a compromise like the Israel-Palestinian"peace" which is doomed to failure.

If Creole is to become a markup specification, then it will invariably collide with some other forms of markup, and it is about time it made those aims clear, otherwise I'm wasting my timehere!! - indeed

A markup inherently collides with the simplest text editor where each and every character is defined as representing itself and therefore any other interpretation is a collission and so it is clearly TOTALLY impossibel to have a collission free markup and so this is a TOTALLY unrelistic goal.

The point about a specification is that it prescribes how to comply ... it inherently requires change to comply and if you do not accept that then it is not possible to write a single specification that will solve the problem of incompatible wikis


I used to work for a company that insisted all emails were sent as HTML using a specific font. They thought they were being clever, until I showed them what it looked like on my home PC which did not have their font installed and then I pointed out that many of their customers were getting the same very amateurish looking text.

The problem was that the company was telling the customers how they had to read the emails. They weren't letting the customers pick the best font for them - did they care if someone had poor eyesight and so wanted to read emails with a particularly clear font - the company didn't care and so didn't want their business!!

Unfortunately, without html, some of the very common formatting isn't possible. It really is annoying not being able to emphasise part of the text. And so many times I've tried to put things in a tabulated table, knowing that only if people happen to use the same font will they see it the same.

So, what we need is a specification that lets people emphasis text, without telling them how to display it. ONe that doesn't insist you have Micro$oft fonts installed on your spectrum PC, but which lets you EMPHASISE.

So I am suggesting that creole should be a relative specification. That is to say, the specification says how parts of the text relate to each other not how those parts will be displayed absolutely.


  1. Times-New-Roman
  2. Red
  3. 12point/pica
  4. position on screen.
  5. Code?


  1. stronger emphasis
  2. different from the rest of the text
  3. more important
  4. raised up
  5. smaller text
  6. included as a note (how the note is displayed is absolute)
  7. included as a quote (how displayed is absolute)
  8. Tables - describe the relative layout of items

Add new attachment

Only authorized users are allowed to upload new attachments.

« This particular version was published on 16-Mai-2008 16:01 by Isonomia.