similar to: Metadata syntax (was Universal syntax for Markdown)

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

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

So, hi all. First time commenting on the list. I personally think having tags (whether of type "author:" or type "by") is useful for two reasons. One: It allows multiple tags to be entered. Two, it clears up the potential problem listed by Fletcher regarding tags. by Christoph Freitag Affiliation: XYZ by Fletcher T. Penney Affiliation: ABC tags: Markdown, Standardization,

Hi, because of the great editor "Writer" from Information Architects I've learned about Markdown and I love it. But it's very confusing, that there are so many standards with different features: classical Markdown, Markdown Extra, MultiMarkdown. I think for most users and the spreading of Markdown it would be nice, to have only one syntax. And this universal syntax should have

sherwood said: > If agreement is reached, then the group > looks at variants 6,7,8,9 and inquires > if they would like to join in this effort. well, that kind of leveraged consensus would have been the way to go about this process a year ago. but not today. > Has anyone collected a would-be canonical list > of either the ambiguous cases in original MD, >

For those of you who are expert you may chuckle over this. Perhaps if it's in the record, however, it may help someone else. I was getting cases of <div id="content"> standing on a line by itself, getting converted to this: <p><div id="content"></p> Yes, the line above and below are blank. Yes the div tag is starting at the first column It

looks like my message from last week about writing tools was right on time... we are enjoying a display of fireworks now going off in this particular arena... fletcher started work on an editing app with markdown-preview built right in, after reporting on his blog that he had "seen the future" in ali's post last month, where ali debuted his syntax highlighter, and fletcher is

i've released the first beta of my e-book converter-tool. you are invited to throw stones at it (and at me) if you like: > http://jaguarps.com "beta" is a compromise. i developed it on a mac, so that particular version is solid. but "alpha" would be a better label for the status of the windows and linux versions, so if you have one of _those_ machines, and you

Bradley Taylor shot me this *goldmine* of ugly ugly ugly dogs: http://www.sonoma-marinfair.org/uglydogvote.shtml I *have* to use one of these for the Mongrel BUGS Mascot. He''ll go on our bug list page and replace the little beetles on the left. Pick the dog you think best represents a lovable but defective pooch and reply to this with your +1. Let the voting begin! -- Zed A. Shaw

Not only is [Markdown] dead, it's starting to smell really bad. (Apologies to Pike.) It's author appears to have little interest in developing the tool and participating in the community which uses it. I'd like to see the community cooperate toward a specification which addresses the shortcomings and ambiguities of Markdown (even if it need be released under a new name).

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

ok, while i was in the process of writing that last post, fletcher and john weighed in themselves. that's good. i can say some things that they can't, though, so i will. fletcher told you how multimarkdown is booming, and it was an impressive list. what you might not realize is, he _undersold_ it. it is even bigger than he described, and it's gonna _double_ in size in the next

i am considering writing converters between my "zen markup language' and "markdown", but i don't know which version of markdown to target. i'd think it'd be the "pandoc" version, and i understand that to be closest to "multimarkdown", but gruber has said he "disagrees" with "almost every part" of multimarkdown's syntax

hey fletcher, thanks for your input here. :+) and -- quite obviously -- your program will be whatever it is that _you_ think that it should be. of course. the thing is, i am certain that i have been clear that the feature that i believe will be "killer" is on-the-fly formatted display. that's my stand. and i'd say my reasoning has been equally clear, namely that this

alan said: > I think I am in agreement, > if by "isn't necessary" you mean to say that > simply providing more features to Markdown > doesn't force end users to use them, > or even really know they exist. except that wasn't what i meant. i mean that it's not necessary to trade simplicity in order to get the power of additional

godspeed, steve. thanks for giving us the tools to catch fish. -bowerbird -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20111006/3e1c11bd/attachment.htm>

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

brett terpstra continues his obsession with markdown... > http://fuckyeahmarkdown.com/ there's also a g-rated version: > http://heckyesmarkdown.com/ brett has accomplished more in the last three months than this listserve accomplished in the last three years. and it looks like he's only just getting started... meanwhile, fletcher is about to send off his rocket, which

I'd love to hear everyone's favorite way to convert markdown to PDF. I'm looking for the easiest, most straightforward option. >From what I've gathered, the method needs to include something like LaTeX in order to have it paginate correctly, so I'll need to install that as well. Is this correct? When I've used the simple export-to-PDF options in Marked, MMD

spring has sprung, so on this day of grass, i guess i just can't hold this back any more. > http://zenmagiclove.com/aarp2.py voila. a dingus for zen markup language. lighter than markdown. _and_ more powerful... i know. wha? go figure. not that it's a competition. supporters will love finally seeing a look. detractors will love the bugs i left in there, just for them, as