search for: t0c

...structions. So TT was NOT handling markdown the closing </div> in the non-working cases. Markdown couldn't find a closing tag to match the opening tag, therefore it must be text, and gets wrapped in <p> tags. Go figure. -- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548

I quite often find myself making documents that pull together other fragmentary documents. Does anyone have suggestions for an include or embed syntax? I.e. a way of saying "pull in the contents of document X here". Has this been implemented before? Such a syntax might be: (embed: snippet.txt) or [include](snippet.txt) Your thoughts? Best regards, - Daniel

Hey everyone. Just and FYI that I started a list of markdown implementations: https://github.com/markdown/markdown.github.com/wiki/Implementations Please review and make any corrections/additions. The page should be publicly editable as long as you have a github account. Note that this is a list of _libraries_, which differentiates it from wikipedia's list [1]. For example, mmd2pdf is a

Is there a file/document browser that render and display Markdown files? (for the Mac) jem

>From http://daringfireball.net/projects/markdown/syntax#html: > Note that Markdown formatting syntax is not processed within block-level > HTML tags. E.g., you can?t use Markdown-style *emphasis* inside an > HTML block. [...] Unlike block-level HTML tags, Markdown syntax is > processed within span-level tags. How do people work around this when they want to apply Markdown to text

New to mailing lists and Markup as well so please bear with me. I have been looking for two things. A project management system that syncs with Notational Velocity as well as something that lets me write and format script in plain text, then have that converted to the proper formatting for a script. I was wondering would Markdown have the ability to do this or have the changes necessary for this?

fletcher said: > For any consensus to come about, > I think we need to agree on the > fundamental purpose and philosophy of > the consensus we claim to be interested in. it would be nice. > Otherwise many of these discussions will > continue to occur without much hope of > moving forward to any actual outcome/resolution. yep. > it's

ok, i waited for 2 weeks, and still no votes -- none! -- on whether my posts are sufficiently on-topic, or not... and that basically confirms what i suspected all along, which is that no one really cares one way or the other. even the guys who put up the bitchy posts are probably just having a bad day, and they don't have a dog to kick, and the wife made 'em stop smoking herb, so they

It took much more time than I expected, and it is currently less complete than I have hoped, but I've finaly made a first draft of the Markdown Extra spec. You can find it at <http://michelf.com/specs/markdown-extra/ > Currently, the specification defines its goals and a document model for Markdown Extra. It lacks the most important part though: the parsing section, which

FYI, There was an interest from a few people to create a formalization of Markdown as it is currently implemented. A W3C Community Group has been created for moving forward and exploring the idea and create a spec if necessary. A W3C Community Group [1] is a platform for discussing, publishing about a topic. You just need a free public W3C account [2] The community markdown group [3] has

nick said: > http://nickgravgaard.com/elastictabstops/ exactly. thanks for writing it up, nick. the only thing i'd add is the notion that tables should be copyfit to the viewport. if the viewport gives you plenty of room, give the columns some breathing space. if not, tighten them as much as needed. *** > http://readown.googlecode.com/ cool. now how about an

Hello List, Firstly, I was very impressed when I tried markdown 2.0 recently. Fantastic work all! I have a query about the treatment of emphasis. I realise that the horse has bolted, and changes to currently supported functionality are unlikely to attract support. However, there does seem (at least in my tiny mind) to be a mis-match between the following stated goal and the present

Dear Markdown enthusiasts out there! Sure, I don't need to tell you how great an versatile Markdown is for writing standard documents. I think, that it would make a really great universal standard as a programming documentation language, too, and maybe "CodeDown" would be a good title for this approach. The idea started when I was trying to document some PHP scripts. I need to