Update readme.markdown

This commit is contained in:
Jan T. Sott 2020-07-18 01:23:35 +02:00 committed by GitHub
parent 0654442ec9
commit f1a4e4f2d5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -20,13 +20,13 @@ On November 25th, 2013, [Creative Commons](http://creativecommons.org/) announce
There's a plethora of Markdown file extensions, but I have decided to go with `markdown`. Read why: There's a plethora of Markdown file extensions, but I have decided to go with `markdown`. Read why:
> "We no longer live in a 8.3 world, so we should be using the most descriptive file extensions. Its sad that all our operating systems rely on this stupid convention instead of the better creator code or a metadata model, but great that they now support longer file extensions."* > *"We no longer live in a 8.3 world, so we should be using the most descriptive file extensions. Its sad that all our operating systems rely on this stupid convention instead of the better creator code or a metadata model, but great that they now support longer file extensions."*
> >
> <cite>Hilton Lipschitz ([via](http://hiltmon.com/blog/2012/03/07/the-markdown-file-extension/))</cite> > Hilton Lipschitz ([via](http://hiltmon.com/blog/2012/03/07/the-markdown-file-extension/))
> "…the only file extension I would endorse is “.markdown”, for the same reason offered by Hilton Lipschitz"
> >
> <cite>John Gruber, creator of Markdown ([via](http://daringfireball.net/linked/2014/01/08/markdown-extension))</cite> > *"…the only file extension I would endorse is “.markdown”, for the same reason offered by Hilton Lipschitz"*
>
> John Gruber, creator of Markdown ([via](http://daringfireball.net/linked/2014/01/08/markdown-extension))
## Usage ## Usage