http://permalink.gmane.org/gmane.text.markdown.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.text.markdown.general/4403 <pre>IF concensus could be reached, then many implementors would have to decide how to support it. There is very little history of open source projects merging, particularly when there are multiple forks of it Mind you Posix is such a standard and it came up well after there were a zilling dialects of Unix. (And many GNU utilities have a flag, --posix-me-harder for compliance in the face of common usage.) And there lies the hint: Either command line flags, a dot rc file, or preferences for GUI implementations that handles the feature difference. This allow people who cling to 'the way that works' and is generally a good thing for any program that is use as a toolchain component. Each author could also be responsible for a conversion program to migrate texts from their way to 'standards compliant' The question then becomes for the authors: What's in it for them. Where before they were the sole prince of a small principality, now they become a cabinet member of a major state. No major feature change with</pre> Sherwood Botsford 2012-05-20T12:29:26 http://permalink.gmane.org/gmane.text.markdown.general/4402 <pre>original What impact would you expect (or require) this to have on the current varied Markdown implementations? I'm not sure that creating a bureaucracy in this manner would help all that much - yes, you could perhaps evolve a standard after substantial discussion, but what next? The current implementations serve a purpose for the authors, and the fact that they are all somewhat different is a reflection of the use that the authors put them to. A new standard would either (1) be a subset of all the existing implementations, or (2) a combination of all available options. (1) is not going to work for those who use existing conversion tools and rely on the features that your standard doesn't support. Why should they change what they need just because a committee says so? (2) is, frankly, going to be a mess. Your committee would have to choose between different syntax for very similar features, and that's going to alienate some of the development community. The likely outcome is (3) a supported feature list</pre> Paul Wilson 2012-05-20T01:00:50 http://permalink.gmane.org/gmane.text.markdown.general/4401 <pre> Similar ideas for a standard for extensions have been kicked around in the past. It always collapses in arguments about what such a standard should look like. There are two main problems with such an effort. First, there is no broad consensus among users on what the objective of such a standard should be. At one end of the spectrum you have relative Markdown purists for whom simple, readable plain text formatting is paramount and the base standard only needs a few key extensions. At the other end of the spectrum you have those who want Markdown to be a complete rich text markup language and are willing to accept more complex, less readable markup to achieve that goal. Efforts usually break down during bickering among those factions so we never get to the second problem: implementers. Those who implement Markdown extensions generally do so to meet their own needs or preferences. It's not at all certain that they would update their work to meet a standard that may not do what they want - particularly when</pre> Richard Caldwell 2012-05-19T22:44:24 http://permalink.gmane.org/gmane.text.markdown.general/4400 <pre>My stackoverflow question here: http://stackoverflow.com/questions/9222990/is-there-an-official-organization-for-discussing-or-releasing-standard-markdown. And github issue here: https://github.com/michelf/php-markdown/issues/27. So, if there were somebody hold that, the markdown world would be much better than ever! If held, the ORG need a concil to discuss standard, and a website to publish standard. I think most of the author who implemented markdown converter in any language could be the concil member, not only the original author (Because he has not been maintaining the syntax for so long time.). OK, what's your idea? mytharcher _______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Junyi Yan 2012-05-19T03:02:41 http://permalink.gmane.org/gmane.text.markdown.general/4399 <pre> Indeed! It's pretty good, but unlike MarkEdit it doesn't indent blockquotes (by which I mean moving in the left margin) and links aren't clickable. Nice to see that I am not the only one who's wanted better indentation in Markdown editors. --Andy </pre> Andy Lee 2012-05-09T15:48:18 http://permalink.gmane.org/gmane.text.markdown.general/4398 <pre>Wow, MarkEdit is the nearest I've seen to the Markdown editor I really want. Yup, it does what I meant with indentation. iA Writer is beautiful and does *pretty* well with Markdown, but MarkEdit does better. --Andy On May 8, 2012, at 9:31 PM, Bodhi wrote: </pre> Andy Lee 2012-05-09T15:44:30 http://permalink.gmane.org/gmane.text.markdown.general/4397 <pre> The Markdown grammar used by the TextMate 2.0 alpha release does this. </pre> Rob McBroom 2012-05-09T12:44:43 http://permalink.gmane.org/gmane.text.markdown.general/4396 <pre>Just to clarify, you mean this ? If so, and you're on a Mac, my editor[1] does that. It has some bugs with the indenting of ordered lists, but works reasonably well for blockquotes and unordered ones. If you mean outdenting, I think iA Writer does, or used to do this. [1] "MarkEdit": http://keshiki.net/markdown-editor/ (this page is out of date, several of the detailed bugs have been fixed) newer build than linked on that page: https://github.com/downloads/bodhi/MarkdownEditor/MarkEdit%200.2.1.zip source: https://github.com/bodhi/MarkdownEditor On 09/05/2012, at 11:01 , Andy Lee wrote: </pre> Bodhi 2012-05-09T01:31:59 http://permalink.gmane.org/gmane.text.markdown.general/4395 <pre>Great list. One thing I haven't seen anyone implement (or anyone but myself ask for) is hanging indents for list elements. The nearest I've gotten is in TextWrangler/BBEdit by selecting the "Reverse" option for "Soft-wrapped line indentation". Can I be the only one who finds nested lists hard to read when all items wrap to the left edge of the window? It occurs to me I'd like to see blockquotes fully indented too. --Andy On May 8, 2012, at 8:04 PM, Bowerbird&lt; at &gt;aol.com wrote: _______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Andy Lee 2012-05-09T01:01:02 http://permalink.gmane.org/gmane.text.markdown.general/4394 <pre>i should probably just let this listserve die, but... *** anyway, it's that brett terpstra fellow again... -bowerbird_______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Bowerbird< at >aol.com 2012-05-09T00:04:57 http://permalink.gmane.org/gmane.text.markdown.general/4393 <pre>No, but you can use HTML (and thus also CSS) within a Markdown document. On Apr 25, 2012, at 10:03 AM, Jeremy Bruce wrote: </pre> Alan Hogan 2012-04-26T17:56:41 http://permalink.gmane.org/gmane.text.markdown.general/4392 <pre>I've done a few google searches but haven't been able to come up with anything. Does markdown have support for hanging indents for APA style references? </pre> Jeremy Bruce 2012-04-25T17:03:05 http://permalink.gmane.org/gmane.text.markdown.general/4391 <pre>Nice one, bowerbird. I have one suggestion, which is that the textarea should use a monospace font so that, for example, table columns are aligned. David On 20 April 2012 17:44, &lt;Bowerbird&lt; at &gt;aol.com&gt; wrote: _______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> David Chambers 2012-04-21T19:04:47 http://permalink.gmane.org/gmane.text.markdown.general/4390 <pre>alan said: i'm hoping someone with design chops takes pity on me, and contributes something that looks significantly better. but at base, it's just a 2-pane tool, so that's what matters. that's what i was aiming at, yes. easy to understand, as a naive user, and easy to handle, as a programmer. delivering great functionality while remaining simple. mostly convention, yes. the target is books, so the first section/page is defined as the cover/title-page, which is traditionally centered bold. but where there is a lot of text, such as on the example, bold may be overkill, so that's something i might change. i've been closely examining books for several decades now, so i have a very firm idea about what my starting place is... but i'm also quite flexible to the ways authors and readers want to shape e-books to fulfill their destiny, which means i am going to be quite attentive to the feedback they give... i don't anticipate that _a_lot_ will change, but _everything_ is up for questioning; nothing is </pre> Bowerbird< at >aol.com 2012-04-21T00:44:43 http://permalink.gmane.org/gmane.text.markdown.general/4389 <pre>Congrats on shipping a nice dingus, Bowerbird. It does indeed look like an extremely clean and powerful syntax. Small question — What causes the entire first page to be in bold? Convention? Styles applied after your transformation to HTML? Alan On Apr 20, 2012, at 4:14 PM, Bowerbird&lt; at &gt;aol.com wrote: _______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Alan Hogan 2012-04-20T23:47:55 http://permalink.gmane.org/gmane.text.markdown.general/4388 <pre>spring has sprung, so on this day of grass, i guess i just can't hold this back any more. 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 easter eggs in the grass... -bowerbird_______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Bowerbird< at >aol.com 2012-04-20T23:14:00 http://permalink.gmane.org/gmane.text.markdown.general/4387 <pre>Happy Saturday everyone! I'm pleased to officially announce glorify[1], a sinatra extension to help parse markdown and provide syntax highlighting. You can install it using rubygems: $ gem install rubygems Or with bundler, in your 'Gemfile': source :rubygems gem 'sinatra' gem 'glorify' It was a lot of fun writing this, and I hope that someone will find it useful. Thanks goes out to Jonathan Stott for helping rewrite the renderer to use redcarpet 2.0 For usage, and other useful tidbits, check the readme[1]. 1: http://github.com/zzak/glorify#readme </pre> Zachary Scott 2012-04-14T18:25:21 http://permalink.gmane.org/gmane.text.markdown.general/4386 <pre>lou said: sorry, but by "dingus", i meant a tool located on a web-page; one that takes text as input, and converts it to .html output... something like this: or this: or this: or this, for restructured-text: if there are other worthwhile ones, please let me know. thanks. -bowerbird p.s. "fountain" is interesting. as http://fountain.io/faq puts it: Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Bowerbird< at >aol.com 2012-04-10T22:40:04 http://permalink.gmane.org/gmane.text.markdown.general/4385 <pre> $ kramdown test.txt &gt; index.html; heel Need fancy? Use `--template`, which will replace `&lt;%= &lt; at &gt;body %&gt;` LQ </pre> Lou Quillio 2012-04-10T05:28:40 http://permalink.gmane.org/gmane.text.markdown.general/4384 <pre>where are the worthwhile markdown dingi? (dinguses?) i'm interested in any dingus that can take a "reasonable" amount of text -- let's say anything up to a megabyte -- and return the results in real-time, without a long wait... ideally it'd handle something more than gruber-minimum, and an a.p.i. (that'd take a u.r.i. as input) would be dandy... bonus points for additional output (i.e., .epub, .mobi, .pdf). -bowerbird_______________________________________________ Markdown-Discuss mailing list Markdown-Discuss&lt; at &gt;six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss </pre> Bowerbird< at >aol.com 2012-04-10T02:21:49 http://permalink.gmane.org/gmane.text.markdown.general/4383 <pre>It has been a while since I've announced a pandoc release on this list, so here's an update. The latest version of pandoc supports conversion of markdown to a host of other formats, including * HTML formats: XHTML, HTML5, and HTML slide shows using Slidy, S5, or DZSlides * Word processor formats: Microsoft Word docx, OpenOffice odt * Ebooks: EPUB * Documentation formats: DocBook, GNU TexInfo, Groff man pages * TeX formats: LaTeX, ConTeXt, LaTeX Beamer slides * PDF: via LaTeX * Lightweight markup formats: Markdown, reStructuredText, AsciiDoc, MediaWiki, Emacs Org-Mode, Textile It also supports limited conversion *from* Textile, reStructuredText, LaTeX, and HTML to markdown or any of the above formats. Pandoc supports strict markdown syntax, plus a number of extensions, including several kinds of tables, definition lists, fancy ordered lists, automatically numbered example lists, delimited code blocks with built-in syntax highlighting, title blocks, smart punctuation, strikeout, and super/subscripts</pre> John MacFarlane 2012-03-10T15:45:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.text.markdown.general