Proposed table specification (long!)

Seumas Mac Uilleachan seumas at
Mon May 16 11:32:09 EDT 2011

On 15/05/11 01:17 PM, Bowerbird at wrote:

> simon-


> i'm not sure persistence will do you much good.

> nobody seems to have a desire to work together.

> which is likely why there are 39 implementations.


Isn't the existence of 39 implementations due to each implementer having
their own favourite programming/scripting lamguage? And don't most (if
not all) strive to follow the "canonical" Gruber perl markdown
implementation? The inability to "work together" as you put it is due
more th the percieved apathy of the originators of markdown in the last
few years and the lack of an appointed/accepted successor.

> an appeal on behalf of readers seems misguided,

> since very few people are reading markdown text.


In my case I use markdown for a personal info management system and I
read the text as often as the rendered html. But then it is my own text
and I already know how I intended it to be interpreted.

> but a more potent case can be made for _re-use_.

> the more easily content can be remixed, the better.


> for my contender in the light-markup derby --

> zen markup language (zml) -- to facilitate re-use,

> my goal is that users can "round-trip" the text...


> so if they copy the text out of the .pdf and use it

> to create _another_ .pdf, the two will be identical.


> likewise, if they copy the text from a web-browser,

> it will match the .zml file which created that .html.


> or copy the text out of one version (.html or .pdf)

> and use it to create the other version, just like that.


> i am coming very close in both cases. it'll certainly

> be the case that some global changes will always be

> required to restore the original .zml, but if i get it

> down to just a few, that will be an accomplishment.


> -bowerbird



> _______________________________________________

> Markdown-Discuss mailing list

> Markdown-Discuss at


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Markdown-Discuss mailing list