The Status of Markdown

[Joshua Kuritzky]

I've been using your MultiMarkdown as well as your OmniOutliner plug- 
in and your LaTex stylesheets (modified to handle unicode for use  
with XeTeX). Thanks for all of them.

-Joshua

On Oct 29, 2005, at 8:56 AM, Fletcher T. Penney wrote:


> It looks like you chose the same format for metadata as I did when  

> I wrote MultiMarkdown.  I'm not sure how you handle it, but  

> MultiMarkdown uses the metadata to create the title for the XHTML  

> document (if creating a "complete" XHTML document (body, header,  

> etc) and not just a snippet of XHTML to be included in a larger  

> document).

>

> Then, the metadata is used by my XSLT scripts to populate the  

> title, author, date, keywords, etc in my LaTeX documents, so that  

> information is placed in the appropriate places in my pdf files.

>

> If enough people are using this idea, it might be nice to  

> standardize some of the keys - for instance, I use Title, Date,  

> Author, Keywords, Copyright for the obvious.  I use Format to  

> specify "complete" if I want to generate the full XHTML and not  

> just a snippet.  I use HeaderLevel if I want to increase the top  

> level header a certain amount (start with <h2> rather than <h1> for  

> instance - this comes about because I use OmniOutliner to write my  

> documents, so the the header code ( `#`) is generated for me)

>

> Is anyone else out there doing something like this?  Is there  

> enough support for it to petition it's inclusion in the "real"  

> Markdown, or should it remain a custom only feature?

>

> Fletcher

>

> http://fletcher.freeshell.org/wiki/MultiMarkdown

>

>

> On Oct 29, 2005, at 3:38 AM, Jan Erik Moström wrote:

>

>

>> Lst Recv <listrecv at gmail.com> 2005-10-28 20:50:

>>

>>

>>

>>> * How to stucture the Markdown.  Beyond headings, I'd like to

>>> semanticaly annotate different parts.  (This also helps with

>>> formatting, as above.)  Should I just create my own tags (eg

>>> <reminder> <example> <warning>)?

>>>

>>>

>>

>> I don't know exactly what you want but I'm doing something along  

>> these lines,

>> at the top of the each document I have a simple header with some meta

>> information. My solution to this is to wrap some additional code  

>> around the

>> call to Markdown that removes this info before sending it to  

>> Markdown, I can

>> then use the meta information as I see fit. An example can be  

>> found at

>> <http://blog.mostrom.pp.se/?p=63>

>>

>>                 jem

>> -- 

>> Jan Erik Moström, www.mostrom.pp.se

>> _______________________________________________

>> Markdown-Discuss mailing list

>> Markdown-Discuss at six.pairlist.net

>> http://six.pairlist.net/mailman/listinfo/markdown-discuss

>>

>>

>

>

> -- 

> Fletcher T. Penney

> fletcher at alumni.duke.edu

>

> I put contact lenses in my dog's eyes. They had little pictures of  

> cats

> on them. Then I took one out and he ran around in circles.

>         - Steven Wright

>

>

> _______________________________________________

> Markdown-Discuss mailing list

> Markdown-Discuss at six.pairlist.net

> http://six.pairlist.net/mailman/listinfo/markdown-discuss

>