Re: File Extension Consensus
On Sun, Nov 7, 2010 at 8:47 AM, Seumas Mac Uilleachan seu...@idirect.ca wrote: Since generally where needed the extension can be custom defined, why do we need a standard anyway? For this reason I have been silent on this issue. [^1] On 06/11/10 06:59 PM, Brett wrote: Here are the results from the limited data set provided. It looks like 'markdown' is the winner followed by 'mdown'. Third place is a tie between 'text' and 'md'. If usage sets a standard, then 'markdown' is the standard. However, I will say that standard or not, I doubt I will ever use markdown as a file extension. Call me lazy if you like, but I simply don't want to type that much every time. I prefer txt and if I must use something else (for example on github) I'll use md. Truth be told, in many situations I see no reason for any special designation. Docs for my projects on github are written in makdown and all have txt for file extensions. Yes, they then display as plan text. I don't care. If github some day adds a feature where they figure out I'm using markdown and convert my docs to html, that's fine too. On the other hand, while something like [Github Pages] does need to know what markup language a document is written in, it shouldn't need to rely on a file extension for that info. As Github Pages is just an instance of [Jekyll] (of which there are many clones) and Jekyll source files all require [metadata], and the metadata is always in the same format regardless of the markup language used, then the metadata could easily include the markup language used regardless of the file extension. Hey, then I could use .txt for everything. I think I'll go file a bug report with Jekyll. [Github Pages]: http://pages.github.com/ [Jekyll]: http://github.com/mojombo/jekyll/ [metadata]: https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter [^1]: I can't help but notice that the other implementors have been silent as well. I suspect that in part it is because we have all had this discussion before. For some, because we really don't care.And in part, because it really doesn't matter. It's the later for me mostly. -- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
re: File Extension Consensus
why do we need a standard anyway? for the same reason any file needs a descriptive extension -- so the humans will know something about that file's contents... in this case, the need-to-know is that the file can be displayed in a more esoteric and pleasing way if the human desires that... and i would also suspect, at this time when the ordinary person is totally unaware of markdown and its benefits, that consistent use of an extension might well serve to prod the curiosity of the more curious of the species, and thus help to spread the word... myself, i'd be satisfied if our computers would auto-recognize any markdown files and render them in the sophisticated style. but it seems we've crippled our computers by making them so dumb that they, too, rely on file-extensions, almost completely. -bowerbird___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
Here are the results from the limited data set provided. It looks like 'markdown' is the winner followed by 'mdown'. Third place is a tie between 'text' and 'md'. If usage sets a standard, then 'markdown' is the standard. Used by Multiple Sources * markdown - BBEdit, Elements, GitHub, Gruber http://tinyurl.com/25bzct8, TextMate * mdown - Elements, GitHub, TextMate * text - BBEdit, Gruber http://tinyurl.com/2abbfjh * md - Elements, GitHub Used by One Source -- * mark - BBEdit * mdwn - Elements * mkd - GitHub * mkdn - GitHub Suggested - * mdtext * mdtxt * mtext ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
You can make TextMate recognize any extension you like by changing the `fileTypes` list in the Markdown language definition. Mine looks like this: fileTypes = ( 'md', 'markdown', 'mdown', 'markdn' ); ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
I don't think you can get Gruber to bless an extension. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
On 5 Nov 2010, at 10:18, Jan Erik Moström wrote: I don't think you can get Gruber to bless an extension. Indeed — this has come up before. Gruber used ‘.text’ at that time. One suggestion I liked was ‘.mtext’ since it stresses the readability of the file. I use ‘.mdown’ myself — I’d prefer ‘.md’ if it wasn’t for the ambiguity/clashes. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
I haven't experimented with others, but TextMate seems to recognize .markdown so that's what I use. On Nov 4, 2010, at 11:28 PM, Dr. Drang wrote: The iOS text editor Elements recognizes these: md, mdwn, mdown, and markdown. /david -- david herren-lage - shoreham, vt pamplona, es Among millions of cows, we can find the only one with mad-cow disease, but we can't seem to find Osama bin Laden. Maybe we should take the CIA and the military off the case and put the Department of Agriculture in charge? ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
On 2010 Nov 05, at 05:18, Jan Erik Moström wrote: I don't think you can get Gruber to bless an extension. Gruber is the markdown pope so he should walk around blessing stuff. :-) ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
File Extension Consensus
I see in the archives that using a common extension for markdown has been discussed. Has an official consensus ever been reached? Thanks -- Brett ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
I don't think you can find any official body that would be able to say anything :) Short answer: not that I know of. I use either '.markdown' or '.txt' - jem ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
On 2010 Nov 04, at 19:22, Jan Erik Moström wrote: I don't think you can find any official body that would be able to say anything :) Well, here's a way to get consensus. Make this list the official body, get suggestions, take a vote, and then get John Gruber to approve. Voila, a consensus file extension (or small set of file extensions [3-4]). -- Brett ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: File Extension Consensus
For what it's worth, GitHub recognizes these extensions for Markdown-formatted README files: md, mkd, mkdn, mdown, and markdown. My sense, from scanning various GitHub repositories, is that md and markdown are the most popular extensions. The iOS text editor Elements recognizes these: md, mdwn, mdown, and markdown. In the great Unix tradition of laziness, I use md. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
