Talk:Markdown

message: Isn't it a mistake that `monospace` is repeated in the following?
Text attributes *italic*,
 **bold**, `monospace`,~~monospace~~, `monospace` .
Ronbarak (talk) 14:29, 3 January 2015 (UTC)
replies: text: Thanks for spotting this error. I've corrected the text attributes example. --Mark viking (talk) 06:27, 4 January 2015 (UTC)
thread_title:  Why is `monospace` repeated? 

message: I've done a little bit of cleaning-up; here's the rundown:
* Cut out the list of languages Markdown has been implemented in, since it was getting rather long.
** 212.179.125.196 (talk) 13:05, 1 December 2008 (UTC)
thread_title: Untitled

message: Now someone put a reference request on top - but what kind of references should be named here - from the scientific community? I'm afraid for these kind of articles we have to cope with the fact that we won't find this kind of reference - and still want the article in WP. --Edoe (talk) 12:08, 27 February 2009 (UTC)
thread_title:  References asked 

message: Certain unofficial extensions to the language, such as those included in PHP Markdown Extra, have become quite popular.  Ideally, this article should list some of the more common ones, with examples, and which implementations support it.  —Preceding unsigned comment added by 72.222.130.167 (talk) 04:50, 21 August 2009 (UTC)
thread_title:  Variants 

message: ll A list of Markdown Editors based on Platform (Windows/Mac/Browser-based) with the various.md flavors they support.
http://andybrandt531.com/2015/03/markdown-for-bloggers-part-6-monster-list-of-markdown-tools/
http://www.sitepoint.com/best-markdown-editors-windows/
https://en.wikipedia.org/wiki/Comparison_of_documentation_generators
http://mashable.com/2013/06/24/markdown-tools/
143.112.144.129 (talk) 22:23, 7 July 2015 (UTC)
thread_title:  Markdown Users 

message: Most of the links above the "External links" sections are not linked to Wikipedia topic.  Rather, they are linked to external websites for programs whose notability has not been addressed.  They are not "references" either, since there is no WP:RS which provides this list. TEDickey (talk) 11:43, 21 April 2012 (UTC)
replies: text: I agree and am removing these lists. If anyone feels a specific piece of software is notable enough to validate being mentioned, make a wikipage for it and link to it. (Narkstraws (talk) 05:23, 3 June 2012 (UTC)
thread_title:  Link-farm 

message: Again, there is no WP:RS other than the primary source for this section.  It consists of detailed examples, and its only purpose is as a manual for markdown TEDickey (talk) 11:45, 21 April 2012 (UTC)
thread_title:  Manual as "Syntax Examples" 

message: At the moment, there are three footnotes.  The first is a review, more or less (actually the latter, since the given source is someone's blog rather than by a knowledgeable review).  The other two just happen to mention markdown in passing; they are discussing something else.  The other links (see the link farm discussion) are all primary sources. TEDickey (talk) 11:50, 21 April 2012 (UTC)
replies: text: I agree. I removed them. (Narkstraws (talk) 05:43, 3 June 2012 (UTC)
thread_title:  Use of primary sources 

message: I have removed the many links to external sources and as such have also removed the warnings about them. If you wish to add one of these links back in because you feel the source is notable enough (doubtful given that markdown's notability itself was questioned not too long ago), I recommend making a wikipedia page for this software. Then link to that wikipedia page. Note I am not encouraging people to spam Wikipedia with non-notable software, I am simply relying on Wikipedia's ability to regulate pages to keep this page spam free. In addition if you feel like adding a link, please be honest about your relationship to the site you are linking to and why you think it merits inclusion. (Narkstraws (talk) 05:51, 3 June 2012 (UTC)
replies: text: I should mention that the use of BBEdit in the article is a great example of how this should be done. (Narkstraws (talk) 05:54, 3 June 2012 (UTC)
replies: text: I just create a page which is borrowed from List of real-time operating systems and Comparison of file archivers specially for Markdown implementations (see: List of Markdown implementations). This keeps the Markdown page clean and satisfies the users which want to know more about available implementations. This is the same guideline for RTOS and is also not polluted with link spam but has a seperate list for available software Wafelijzer (talk) 09:25, 24 June 2012 (UTC)
thread_title:  Removed link spam and warnings 

message: When was Markdown first introduced? --Abdull (talk) 21:21, 29 June 2012 (UTC)
replies: text: Good question! That would be interesting to establish. The mailing list dates back to at least 2006 (http://six.pairlist.net/pipermail/markdown-discuss/2006-April/thread.html), the wayback machine gives us 2003 however: http://web.archive.org/web/20040407164207/http://six.pairlist.net/pipermail/markdown-discuss/ - where it seems the language was in development. The latest markdown release is 1.0.1 and was released on 17 dec 2004. The license also dates back to 2004. The wayback machine goes all the way to march 2004, where the page indicates 1.0b4: http://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ . The wayback machine finds the first hit on daringfireball.net in 2002, and on the april post, it is mentionned that the software is in use since november 2003, so I guess that's your answer! I'll just throw that in the page. :) TheAnarcat (talk) 01:37, 20 April 2013 (UTC)

text: well, seems like i wasted a little time with that research, the information you were looking for was already in the article! i made some clarifications however, as to the exact date. it may be interesting to make a specific "history" section, especially when the standards get underway... but we'll see. TheAnarcat (talk) 01:47, 20 April 2013 (UTC)

text: However, at least some of the conventions used in markdown are much older than the program(s) discussed in this topic.  None of that is reflected in the sources for the topic, it is written as though it was a completely original thing (I'm thinking of the sections on emphasized text, and horizontal rules which are at least ten years older than the 2004 date which you mention). TEDickey (talk) 08:30, 20 April 2013 (UTC)
replies: text:  Got a source for that? :) TheAnarcat (talk) 14:06, 20 April 2013 (UTC)

text: Perhaps (it was a convention which I've used in development that long, since it was explained to me in that era).  Examples are easy to find.  A quote-unquote source giving the origin would be hard.  Depends on what you're trying to prove. TEDickey (talk) 14:26, 20 April 2013 (UTC)
thread_title:  History 

message: I've been using Markdown for years - today I discovered the "as-is" philosophy of the syntax while reading about PanDoc (http://johnmacfarlane.net/pandoc/demo/example9/pandocs-markdown.html) 
I think this is a very useful piece of information for understanding the intent of Markdown. I checked to see if the "as-is" philosophy is mentioned here. Since it wasn't mentioned here, I thought it would improve the article to add a brief mention of it, with a link to the source by John Gruber.  — Preceding unsigned comment added by Elseanyo (talk • contribs) 13:11, 13 June 2013 (UTC)
thread_title:  Including As-Is Philiosophy 

message: I prefered the version with the "manual" since the language's syntax seems to be its best description to me. However, the "manual" may be shortened. Perhaps a compromise between the old and the current version (e. g. a table like in the German version) could be the best? Best, --Marsupium (talk) 10:05, 16 October 2013 (UTC)
thread_title:  "Manual" 

message: The source given does not agree with the use made of it here, as any reader can verify TEDickey (talk) 21:19, 23 January 2014 (UTC)
thread_title:  Statement by creator John Gruber 

message: I don't see why the stub on extensions isn't just a section in here (the main article) which only has a bullet list on the topic of extensions in the see also section. 188.27.81.64 (talk) 02:05, 24 June 2014 (UTC)
replies: text: — Christoph Päper 15:05, 25 June 2014 (UTC)
thread_title:  Merge Extensions page 

message: No where on the github markdown page that is cited does the "Task List" syntax exist. Further more I cannot seem to find any project on github that has task lists in their readme's. I vote for removing the "Task lists" from added syntax in the git section. Primis (talk) 05:19, 4 July 2014 (UTC)
replies: text: I added a reference verifying task lists in GFM. --Mark viking (talk) 19:50, 9 July 2014 (UTC)
thread_title:  Github flavored markdown, Dubious "Task List" 

message: I removed a  tag from the "Implementations" section, as every entry in the list there is for the markdown implementation in some notable OS, scripting language, library, editor, or other thing about which we have an actual article.  I also removed the incorrect  tag, which is for WP:EL-violating use of inline external links like this one, in article prose, or the inclusion of things in the "External links" section that do not belong there (or belong in the article at all, per WP:SPAM). PS: See WP:OVERTAG and consider how ironic it is to unnecessarily tag a section with what amounts to a list of redundant cleanup templates, including with a tag that doesn't belong there, when one's complaint is about a list of things the relevance one disputes. It's remarkably like complaining repetitively in a really whiny voice about how often your co-worker whines.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  01:15, 23 October 2015 (UTC)
thread_title:  "Linkfarm" 

message: Markdown Extra is a very short article; it could be added below CommonMark. One PHP Markdown reference could go to this merged section. 2A03:2267:0:0:7884:1732:BF45:81CD (talk) 16:45, 7 July 2016 (UTC)
replies: text: Support.  This looks like a very reasonable idea given that the information about this extension is quite short.  Best wishes.  RobbieIanMorrison (talk) 12:12, 23 December 2016 (UTC)
thread_title:  Merge Markdown Extra 

message: The MOS template refers to a rule which has an explicit exception for the usage of code in this article: to show succinct examples of a coding language. The examples of this section can in no way be described as complete algorithms. Therefore the MOS template was applied in error. I removed it. Before considering reverting my change, please read the relevant rule and its exceptions very carefully. Dlw20070716 (talk) 18:15, 22 October 2016 (UTC)
thread_title:  MOS template removed. Was improperly and unfairly applied. 

message: The ReText editor uses .mkd as its file extension by default and will also look for .md, .mkdn, .mdwn, .mdown, and .markdown.  Perhaps, at a minimum, .mkd could be added to the infobox?  Or is this not standard enough to warrant a mention there?  Best wishes.  RobbieIanMorrison (talk) 23:42, 18 December 2016 (UTC)
thread_title:  File extension .mkd 

message: The table showing the syntax could be improved, by adding:
* rows for each type of markup (currently it is just three long uninterrupted columns)
* information on code blocks (to create, simply indent every line of the block by at least 4 spaces or 1 tab)
* the backslash escapes for \ ` * _ {} [] () # + - . !
I am too focused on writing at the moment to make the changes.  But someone else might like to?  Best wishes.  RobbieIanMorrison (talk) 12:57, 23 December 2016 (UTC)
thread_title:  Syntax table needs development 

message: Hello fellow Wikipedians,
I have just modified 2 external links on Markdown. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ to http://daringfireball.net/projects/markdown/
*Added archive https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ to http://daringfireball.net/projects/markdown/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 17:04, 3 June 2017 (UTC)
thread_title:  External links modified 

message: In marketing, a markdown is a price reduction on a collection of products, usually from past fashion seasons. Should we just create the article Markdown (marketing)? --Qwacker (talk) 16:43, 15 January 2018 (UTC)
replies: text: We already have Price markdown as a stub. I've created a redirect from your link to that article, and added a hatnote at this article for disambiguation. Diego (talk) 16:59, 15 January 2018 (UTC)
replies: text: Good stuff, thanks ! --Qwacker (talk) 17:22, 15 January 2018 (UTC)
thread_title:  Markdown in marketing 

message: User:Ajguyot provided two edits making quite radical changes to the Standardization section.  While I think the previous version of the section had issues and the edits made some improvements, I think the fact that Markdown parsing is defined only by the behaviour of a not terribly clean piece of Perl code together with the issues that the CommonMark team identified show that Markdown does not have a clearly defined syntax.   Thoughts and edits welcome before I find time to rework this section. — Charles Stewart (talk) 18:50, 9 March 2018 (UTC)
replies: text: I think it would be good to encourage  to discuss such changes first with other interested editors here on the talkpage. Eric talk 19:57, 9 March 2018 (UTC)
thread_title:  Markdown as having a clearly defined syntax 

message: A section on MultiMarkdown could be added?  Or at least a sentence in the introduction on this variant?  With best wishes.  RobbieIanMorrison (talk) 11:45, 26 December 2018 (UTC)
thread_title:  MultiMarkdown section required 

message: Tools list should be added, because it's handy for people, interested in Markdown. — Preceding unsigned comment added by 80.92.31.29 (talk) 15:43, 10 September 2021 (UTC)
thread_title:  Tools 

message: I'm pretty sure that Youtube has a variant of Markdown on it's site. It's system works just like Markdown with a few exceptions:
* YouTube uses only one pair of asterisks for bold instead of two. 
* only bold, italics, underline, and strikethrough is allowed.
Maybe we should mention YouTube in the article? beepborp (talk) 18:31, 4 October 2021 (UTC)
replies: text: That's not Markdown, though. It's more like Slack and Whatsapp syntax mentioned in lightweight markup language. — Christoph Päper 08:38, 8 October 2021 (UTC)
thread_title:  Youtube Markdown variant? 

message: What is the relationship between editing Wikipedia and using Markdown? Can that be noted herein with a link to the Wikipedia syntax? Jimgettman (talk) 17:44, 15 October 2021 (UTC)
replies: text: Wikipedia's syntax is not Markdown, but instead MediaWiki markup. There is a comparison in the Lightweight markup language article. I don't know that we need a mention here, since Wikipedia doesn't use Markdown. - Dyork (talk) 23:35, 17 October 2021 (UTC)
thread_title:  Wikipedia Markdown? 

message: no tengo ni la menor idea que es un repositorio mucho menos se como crear uno, todo empezo cuando quise agarrar un curso para aprender sobre computacion me pidieron que instalara prcharm y de ahi surgio mi aventura y tuve mas dicho tengo muchos problemas para instalar pycharm en mi chromebook ingresos comandos en la terminal pero de ahi ya no se que hacer, 2601:201:4200:CA20:4DE5:9B22:5EAF:5577 (talk) 03:14, 6 November 2022 (UTC)
thread_title:  principiante 

message: — Assignment last updated by BCMisc (talk) 22:49, 18 October 2023 (UTC)
thread_title: Wiki Education assignment: Technical Writing

message: Perhaps Misskey-flavored Markdown should be in the Variants section due to how much it extends the standard spec, iirc is not 100% compatible (for example links are autodetected) with it and is of a pretty notable significance for the couple hundred thousand users of the microblogging platforms that support it? Sladniebieskiego (talk) 07:33, 24 April 2024 (UTC)
thread_title:  Move MFM to the Variants section