From gerald.bauer at gmail.com Fri Jun 7 16:40:31 2013 From: gerald.bauer at gmail.com (Gerald Bauer) Date: Fri, 7 Jun 2013 22:40:31 +0200 Subject: Slide Deck - Using Markdown for Websites, Presentations, or Books Message-ID: Hello, FYI: If anyone is interested I've prepared a talk on Markdown for the vienna.rb meetup last night with the title "Using Markdown for Websites, Presentations, or Books" [1]. Use the left/right cursor keys (or space bar) to browse the slides. Or check the all-in-one-page markdown source [2]. Slides include: * What's Markdown? * Syntax - Text Formatting * Syntax - Header Formatting * Syntax - Hyperlink * What is Markdown good for? * Example - Website * Example - Presentation * Example - Book * Markdown Parsers in Ruby * What's the `markdown` Gem? * Tooling - Websites * Tooling - Presentations * Tooling - Books * That's it. Thank you. * Appendix: What's EPUB? * Appendix: Zen Writing - Zen Text Editor * Appendix: What's Markdown Extra? * Appendix: What's Babelmark2? What's Markdown Dingus? All content is public domain. Feel free to reuse as you please. Cheers. [1] http://slideshow-s9.github.io/markdown.html [2] https://github.com/vienna-rb/slides/blob/master/13-06-06/markdown.md From icefront at yahoo.com Sat Jun 15 22:29:59 2013 From: icefront at yahoo.com (Szasz-Fabian Jozsef) Date: Sun, 16 Jun 2013 05:29:59 +0300 Subject: target=_blank in urls Message-ID: <51BD2327.4000309@yahoo.com> Hi! Suggestions can be posted here? I made a change to the code - markdown.php (included in the Yii framework) to support target="_blank" in urls. This change doesn't affect the existing markdown texts. Regards, From lbloom at gmx.net Thu Jun 20 14:48:45 2013 From: lbloom at gmx.net (Alexander Veit) Date: Thu, 20 Jun 2013 20:48:45 +0200 Subject: Problem with links in Markdown Message-ID: <00a201ce6de6$cba38500$62ea8f00$@net> Hi, recently I stumbled over a problem with the Markdown link syntax[1] This is [an example](http://example.com/ "Title") inline link. RFC 2396[2], section 2.3 defines left and right parentheses to be mark characters, and thus unreserved characters in URIs. This means that left and right parentheses do not need to be percent encoded in URIs. >From this definition it follows that the above inline link syntax cannot be parsed correctly in all cases. This can e.g. be shown with the online converter at Daring Fireball[3] and the source The book of [Life](https://en.wikipedia.org/wiki/Life_(textbook) "Life textbook"). which is converted to

The book of Life "Life textbook").

However, there's probably a solution to this problem. RFC 2396, 2.4.3 defines the left and right angle brackets as delimiters and explains that > The angle-bracket "<" and ">" and double-quote (") characters are > excluded because they are often used as the delimiters around URI in > text documents and protocol fields. This means that left and right angle brackets will never occur as part of an URI. So deprecating parentheses, and replacing the parentheses with angle brackets in Markdown's inline link syntax would resolve the problem described. As an additional benefit, this would unify Markdown inline link syntax and reference-style link syntax, and simplify link parsing. Any thoughts on this? -- Regards, Alexander Veit [1]: [2]: [3]: (Markdown 1.0.2b7) From michel.fortin at michelf.ca Thu Jun 20 16:16:33 2013 From: michel.fortin at michelf.ca (Michel Fortin) Date: Thu, 20 Jun 2013 16:16:33 -0400 Subject: Problem with links in Markdown In-Reply-To: <00a201ce6de6$cba38500$62ea8f00$@net> References: <00a201ce6de6$cba38500$62ea8f00$@net> Message-ID: <6ED2C831-7360-4A98-9D3D-3747FAE6285C@michelf.ca> Le 20-juin-2013 ? 14:48, Alexander Veit a ?crit : > The book of [Life](https://en.wikipedia.org/wiki/Life_(textbook) "Life textbook"). > > which is converted to > >

The book of Life "Life textbook").

Most Markdown implementations out there do the right thing: matching opening and closing parenthesis. It's just sad that Markdown.pl doesn't. http://johnmacfarlane.net/babelmark2/?normalize=1&text=The+book+of+%5BLife%5D(https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FLife_(textbook)+%22Life+textbook%22).%0A > However, there's probably a solution to this problem. RFC 2396, 2.4.3 defines the left and right angle brackets as delimiters and explains that > >> The angle-bracket "<" and ">" and double-quote (") characters are >> excluded because they are often used as the delimiters around URI in >> text documents and protocol fields. > > This means that left and right angle brackets will never occur as part of an URI. So deprecating parentheses, and replacing the parentheses with angle brackets in Markdown's inline link syntax would resolve the problem described. As an additional benefit, this would unify Markdown inline link syntax and reference-style link syntax, and simplify link parsing. Angle brackets surrounding the URL are supported by most Markdown parsers, but the URL must be kept inside the parens. Unfortunately, only some parsers correctly use them to disambiguate: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%5BBrackets%5D(%3Chttps%3A%2F%2Fen.wikipedia.org%2Fwiki%2F)%3E+%22Brackets%22).%0A -- Michel Fortin michel.fortin at michelf.ca http://michelf.ca From pagaltzis at gmx.de Thu Jun 20 23:44:08 2013 From: pagaltzis at gmx.de (Aristotle Pagaltzis) Date: Fri, 21 Jun 2013 05:44:08 +0200 Subject: Problem with links in Markdown In-Reply-To: <00a201ce6de6$cba38500$62ea8f00$@net> References: <00a201ce6de6$cba38500$62ea8f00$@net> Message-ID: <20130621034408.GA4702@fernweh.plasmasturm.org> * Alexander Veit [2013-06-20 20:50]: > recently I stumbled over a problem with the Markdown link syntax[1] > > This is [an example](http://example.com/ "Title") inline link. > > RFC 2396[2], section 2.3 defines left and right parentheses to be mark > characters, and thus unreserved characters in URIs. This means that > left and right parentheses do not need to be percent encoded in URIs. I?ve run into this as well. The easiest solution (which, since you?re already writing the link inline, is not much of a loss) is to work around it by falling back to HTML for the link in question, i.e. write it as . It?s a wart, but can be lived with. Regards, -- Aristotle Pagaltzis // From sendiulo at gmx.net Fri Jun 21 10:40:51 2013 From: sendiulo at gmx.net (sendiulo at gmx.net) Date: Fri, 21 Jun 2013 16:40:51 +0200 Subject: Problem with links in Markdown In-Reply-To: <20130621034408.GA4702@fernweh.plasmasturm.org> References: <00a201ce6de6$cba38500$62ea8f00$@net> <20130621034408.GA4702@fernweh.plasmasturm.org> Message-ID: <7F918C64-8A73-4B02-9B1E-664871C8B1E8@gmx.net> Am 21.06.2013 um 05:44 schrieb Aristotle Pagaltzis : > * Alexander Veit [2013-06-20 20:50]: >> recently I stumbled over a problem with the Markdown link syntax[1] >> >> This is [an example](http://example.com/ "Title") inline link. >> >> RFC 2396[2], section 2.3 defines left and right parentheses to be mark >> characters, and thus unreserved characters in URIs. This means that >> left and right parentheses do not need to be percent encoded in URIs. > > I?ve run into this as well. > > The easiest solution (which, since you?re already writing the link > inline, is not much of a loss) is to work around it by falling back > to HTML for the link in question, i.e. write it as . > > It?s a wart, but can be lived with. > > Regards, > -- > Aristotle Pagaltzis // > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss at six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss I guess a more elegant workaround would be to use reference style since there is no need for [brackets][1] [1]: example.com/wiki/(brackets) From michel.fortin at michelf.ca Fri Jun 21 11:00:15 2013 From: michel.fortin at michelf.ca (Michel Fortin) Date: Fri, 21 Jun 2013 11:00:15 -0400 Subject: Problem with links in Markdown In-Reply-To: <7F918C64-8A73-4B02-9B1E-664871C8B1E8@gmx.net> References: <00a201ce6de6$cba38500$62ea8f00$@net> <20130621034408.GA4702@fernweh.plasmasturm.org> <7F918C64-8A73-4B02-9B1E-664871C8B1E8@gmx.net> Message-ID: <2894ADF0-26EA-4069-9BFA-BE149C1DE47D@michelf.ca> Le 21-juin-2013 ? 10:40, sendiulo at gmx.net a ?crit : > Am 21.06.2013 um 05:44 schrieb Aristotle Pagaltzis : > > I guess a more elegant workaround would be to use reference style since there is no need for [brackets][1] > > [1]: example.com/wiki/(brackets) Another idea is to backlash-escape those parenthesis: [example](example.com/wiki/$brackets$ "title") Seems to work for most implementations, including Markdown.pl: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%5Bexample%5D(example.com%2Fwiki%2F%5C(brackets%5C)+%22title%22) -- Michel Fortin michel.fortin at michelf.ca http://michelf.ca From bowerbird at aol.com Fri Jun 21 12:10:00 2013 From: bowerbird at aol.com (bowerbird) Date: Fri, 21 Jun 2013 12:10:00 -0400 (EDT) Subject: dead skunk in the middle of the road Message-ID: <8D03CB0EA08DCE3-1FB8-C1B2@webmail-d257.sysops.aol.com> well yes, it's easy enough to go around a dead skunk in the middle of the road, once you know that the thing is there... the problem is that all of the new drivers on this increasingly heavily traveled road hit the darn corpse, over and over again, and the smell just gets worse and worse. but none of the people on the road crew seem to want to move it off of the road... "just drive around it", they say. yeah, right. -bowerbird From tom at maynard.com Fri Jun 21 14:23:36 2013 From: tom at maynard.com (Tom Maynard) Date: Fri, 21 Jun 2013 13:23:36 -0500 Subject: dead skunk in the middle of the road In-Reply-To: <8D03CB0EA08DCE3-1FB8-C1B2@webmail-d257.sysops.aol.com> References: <8D03CB0EA08DCE3-1FB8-C1B2@webmail-d257.sysops.aol.com> Message-ID: <51C49A28.8000405@maynard.com> On 21-Jun-13 11:10, bowerbird wrote: I was a bit disappointed when this little posting didn't rhyme. With apologies to the author, I've touched it up a bit: > well yes, it's easy enough to go 'round > a dead skunk in the middle of the road, > once you know where the thing is found... > > the problem is that all of the cars > on each and e'vry traverse > hit the darn corpse, over and over again, > and the smell gets worse and worse. > > but none of the folks on the road crew > seem to know what they must do... > > "just drive around it", they say. Oh, PEW! > > -bowerbird [ed. Tom Maynard] From bowerbird at aol.com Fri Jun 21 16:54:50 2013 From: bowerbird at aol.com (bowerbird) Date: Fri, 21 Jun 2013 16:54:50 -0400 (EDT) Subject: dead skunk in the middle of the road In-Reply-To: <8D03CB0EA08DCE3-1FB8-C1B2@webmail-d257.sysops.aol.com> References: <8D03CB0EA08DCE3-1FB8-C1B2@webmail-d257.sysops.aol.com> Message-ID: <8D03CD8B50160CB-1814-E6EE@webmail-d259.sysops.aol.com> tom said: > I was a bit disappointed when this little posting didn't rhyme. > With apologies to the author, I've touched it up a bit: no apologies necessary, tom. you've done an extremely fine job! except for those ugly uppercase letters, i accept all of your edits. :+) -bowerbird p.s. ok, i'd rather have "every" spelled-out, but that's a little quibble, and i don't intend to look this gift-horse in the mouth any further... ;+) p.p.s. as the old saying goes: "i didn't have time, to make it rhyme." From lbloom at gmx.net Sun Jun 23 15:36:54 2013 From: lbloom at gmx.net (Alexander Veit) Date: Sun, 23 Jun 2013 21:36:54 +0200 Subject: Problem with links in Markdown In-Reply-To: <6ED2C831-7360-4A98-9D3D-3747FAE6285C@michelf.ca> References: <00a201ce6de6$cba38500$62ea8f00$@net> <6ED2C831-7360-4A98-9D3D-3747FAE6285C@michelf.ca> Message-ID: <000001ce7049$044d4760$0ce7d620$@net> Michel Fortin wrote: > -----Original Message----- > From: markdown-discuss-bounces at six.pairlist.net [mailto:markdown- > discuss-bounces at six.pairlist.net] On Behalf Of Michel Fortin > Sent: Thursday, June 20, 2013 10:17 PM > To: Discussion related to Markdown. > Subject: Re: Problem with links in Markdown > > Le 20-juin-2013 ? 14:48, Alexander Veit a ?crit : > > > The book of [Life](https://en.wikipedia.org/wiki/Life_(textbook) > "Life textbook"). > > > > which is converted to > > > >

The book of href="https://en.wikipedia.org/wiki/Life_(textbook">Life "Life > textbook").

> > Most Markdown implementations out there do the right thing: matching > opening and closing parenthesis. It's just sad that Markdown.pl > doesn't. > http://johnmacfarlane.net/babelmark2/?normalize=1&text=The+book+of+%5BL > ife%5D(https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FLife_(textbook)+%22Life+ > textbook%22).%0A OK, but matching opening and closing parens is nothing more than the attempt to make an educated guess. Even though the approach reduces the number of failures, it does not make a correct algorithm for parsing arbitrary links. > [...] > > Angle brackets surrounding the URL are supported by most Markdown > parsers, but the URL must be kept inside the parens. OK, agreed. Even though additional parens are required, it seems to me that this is in better accordance with the reference-style link syntax. > Unfortunately, only some parsers correctly use them > to disambiguate: > http://johnmacfarlane.net/babelmark2/?normalize=1&text=%5BBrackets%5D(% > 3Chttps%3A%2F%2Fen.wikipedia.org%2Fwiki%2F)%3E+%22Brackets%22).%0A Imho, these are bugs: showdown 0.3.1 Markdown.pl 1.0.1 RDiscount 1.6.8 marked 0.2.6 RedCarpet 2.1.1: Opening angle-bracket ignored, https://en.wikipedia.org/wiki/ rendered as a link. Markdown.pl 1.0.2b8: Invalid URI syntax in generated link. peg-markdown 0.4.14 Maruku 0.6.1 Maruku (Math-Enabled) 0.7.1.beta1: Non-URI character HTML-escaped, wrong link generated. -- Just my two cents Alex From wolfgangmcq at gmail.com Fri Jun 28 11:55:41 2013 From: wolfgangmcq at gmail.com (Wolfgang Faust) Date: Fri, 28 Jun 2013 11:55:41 -0400 Subject: Mysterious MD5ification under very specific circumstances Message-ID: I was building a markdown document today when my document suddenly went blank. When I looked at the HTML source, I found that all my codeblocks had been MD5ified. The following is a minimal document which reproduces the error: # Header # This is a codeblock. **Bold text** In particular, there must be: - A header - A comment containing the sequence NEWLINE TAB followed by at least two greater-than signs - At least one codeblock - Bold text - Another comment at the end of the document. Changing even the smallest detail in the markdown results in a correct HTML document, as expected. When I run this through markdown v.1.0.1, I get:

Header

What on earth is going on here, and who do I report this bug to? -------------- next part -------------- An HTML attachment was scrubbed... URL: From waylan at gmail.com Fri Jun 28 12:32:39 2013 From: waylan at gmail.com (Waylan Limberg) Date: Fri, 28 Jun 2013 12:32:39 -0400 Subject: Mysterious MD5ification under very specific circumstances In-Reply-To: References: Message-ID: Wolfgang, Which implementation of the markdown parser are you using? Perl, php, ruby, python, javascript, ... (and many more) and which version specificly? Ask to an explaination, some implementations of the parser use MD5 Hashes as placeholders for the already parsed pieces of the document. My guess is that you found an edge case which tripps up the code that swaps out the placeholders for the parsed html. Waylan Limberg waylan at gmail.com On Jun 28, 2013 11:55 AM, "Wolfgang Faust" wrote: > I was building a markdown document today when my document suddenly went > blank. When I looked at the HTML source, I found that all my codeblocks had > been MD5ified. The following is a minimal document which reproduces the > error: > > # Header # > > > This is a codeblock. > > **Bold text** > > In particular, there must be: > > - A header > - A comment containing the sequence NEWLINE TAB followed by at least > two greater-than signs > - At least one codeblock > - Bold text > - Another comment at the end of the document. > > Changing even the smallest detail in the markdown results in a correct > HTML document, as expected. > > When I run this through markdown v.1.0.1, I get: >

Header

>> >> >> >> What on earth is going on here, and who do I report this bug to? >> >> _______________________________________________ >> Markdown-Discuss mailing list >> Markdown-Discuss at six.pairlist.net >> http://six.pairlist.net/mailman/listinfo/markdown-discuss >> > > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss at six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fletcher at fletcherpenney.net Fri Jun 28 12:44:38 2013 From: fletcher at fletcherpenney.net (Fletcher Penney) Date: Fri, 28 Jun 2013 12:44:38 -0400 Subject: Mysterious MD5ification under very specific circumstances In-Reply-To: References: Message-ID: <376896F5-E9AE-4A20-8315-1CF84B15DB50@fletcherpenney.net> By "markdown v.1.0.1" I'm guessing he meant Gruber's Perl Markdown.pl 1.0.1. As for whom to report the bug, Gruber's Markdown.pl is presumably not going to be updated further, and has not been updated in years (also known as an eternity in internet time... ;). Certainly someone on this list may have an interest in finding the bug and posting a fix, but you may be better off switching to a variant of Markdown that is still undergoing active development. As Waylan hinted, there are lots, and I'm sure everyone on the list has their favorites. Heck, many people on this list have written their own (myself included)..... When choosing a variant, some things to consider: * What languages (if any) are you comfortable with if you want to change anything? If you're not changing anything, this may not matter. * Are you using Markdown in a larger project where the choice of language will have a significant impact on ease of use? * How important is performance --- there can be several orders of magnitude difference between implementations? * Do you need extensions to the basic Markdown syntax (e.g. footnotes, tables, etc.)? My own implementation, for example is [MultiMarkdown](http://fletcherpenney.net/multimarkdown/). It is written in C and is designed to compile on pretty much anything. Once installed, you have a simple binary that is extremely fast and easy to use, and offers a few command line options. It's easily used in shell scripts, and most languages offer the equivalent of a "system()" call so you can use external utilities inside of Perl, ruby, etc. It offers a bunch of extra features that many believe were missing from the original Markdown, but you can turn those off with the compatibility mode to imitate the output from "standard markdown", minus most of the bugs. ;) Fletcher On Jun 28, 2013, at 12:32 PM, Waylan Limberg wrote: > Wolfgang, > > Which implementation of the markdown parser are you using? Perl, php, ruby, python, javascript, ... (and many more) and which version specificly? > > Ask to an explaination, some implementations of the parser use MD5 Hashes as placeholders for the already parsed pieces of the document. My guess is that you found an edge case which tripps up the code that swaps out the placeholders for the parsed html. > > Waylan Limberg > waylan at gmail.com > > On Jun 28, 2013 11:55 AM, "Wolfgang Faust" wrote: > I was building a markdown document today when my document suddenly went blank. When I looked at the HTML source, I found that all my codeblocks had been MD5ified. The following is a minimal document which reproduces the error: > > # Header # > > > This is a codeblock. > > **Bold text** > > In particular, there must be: > ? A header > ? A comment containing the sequence NEWLINE TAB followed by at least two greater-than signs > ? At least one codeblock > ? Bold text > ? Another comment at the end of the document. > Changing even the smallest detail in the markdown results in a correct HTML document, as expected. > > When I run this through markdown v.1.0.1, I get: >

Header

> > > > What on earth is going on here, and who do I report this bug to? > > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss at six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss > > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss at six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss -- Fletcher T. Penney fletcher at fletcherpenney.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4899 bytes Desc: not available Url : From wolfgangmcq at gmail.com Fri Jun 28 13:17:51 2013 From: wolfgangmcq at gmail.com (Wolfgang Faust) Date: Fri, 28 Jun 2013 13:17:51 -0400 Subject: Mysterious MD5ification under very specific circumstances In-Reply-To: <376896F5-E9AE-4A20-8315-1CF84B15DB50@fletcherpenney.net> References: <376896F5-E9AE-4A20-8315-1CF84B15DB50@fletcherpenney.net> Message-ID: I happened across http://www.cforcoding.com/2010/01/markdown-musings-on-unintended.html as I was looking for information on why it was doing this. The comments are rather interesting: > Fred Blasdel said... > The PHP Markdown changelog should give you at least a hundred bugs in Markdown.pl to test against ? he started with a straight transliteration (much like MarkdownSharp), and gradually made it less shitty. > Gruber's design 'escapes' blocks by replacing them with their hashcodes, but if the original input contains the same hashcodes ? welcome to XSS city! Lesson learned: Just because markdown.pl is the implementation listed on the 'official' markdown page, and just because I can do `sudo apt-get install markdown` and get it, does *not* mean that it's the best implementation! I've switched to markdown_py (next one down on the list) and everything is working fine now. On Fri, Jun 28, 2013 at 12:44 PM, Fletcher Penney < fletcher at fletcherpenney.net> wrote: > By "markdown v.1.0.1" I'm guessing he meant Gruber's Perl Markdown.pl > 1.0.1. > > > As for whom to report the bug, Gruber's Markdown.pl is presumably not > going to be updated further, and has not been updated in years (also known > as an eternity in internet time... ;). Certainly someone on this list may > have an interest in finding the bug and posting a fix, but you may be > better off switching to a variant of Markdown that is still undergoing > active development. As Waylan hinted, there are lots, and I'm sure > everyone on the list has their favorites. Heck, many people on this list > have written their own (myself included)..... > > When choosing a variant, some things to consider: > > * What languages (if any) are you comfortable with if you want to change > anything? If you're not changing anything, this may not matter. > > * Are you using Markdown in a larger project where the choice of language > will have a significant impact on ease of use? > > * How important is performance --- there can be several orders of > magnitude difference between implementations? > > * Do you need extensions to the basic Markdown syntax (e.g. footnotes, > tables, etc.)? > I appreciate the suggestions; frankly, I'm just looking for something that will take basic markdown and HTMLify it so that I can make sure I got the syntax right. I'm actually embedding python unit tests in a markdown document via the doctest module, which is how I ran across this bug. I was trying to comment out some initialization that didn't need to be shown in the documentation, and suddenly my document went all funny. My own implementation, for example is [MultiMarkdown]( > http://fletcherpenney.net/multimarkdown/). It is written in C and is > designed to compile on pretty much anything. Once installed, you have a > simple binary that is extremely fast and easy to use, and offers a few > command line options. It's easily used in shell scripts, and most > languages offer the equivalent of a "system()" call so you can use external > utilities inside of Perl, ruby, etc. It offers a bunch of extra features > that many believe were missing from the original Markdown, but you can turn > those off with the compatibility mode to imitate the output from "standard > markdown", minus most of the bugs. ;) > > > Fletcher > > > > > On Jun 28, 2013, at 12:32 PM, Waylan Limberg wrote: > > > Wolfgang, > > > > Which implementation of the markdown parser are you using? Perl, php, > ruby, python, javascript, ... (and many more) and which version specificly? > > > > Ask to an explaination, some implementations of the parser use MD5 > Hashes as placeholders for the already parsed pieces of the document. My > guess is that you found an edge case which tripps up the code that swaps > out the placeholders for the parsed html. > > > > Waylan Limberg > > waylan at gmail.com > > > > On Jun 28, 2013 11:55 AM, "Wolfgang Faust" > wrote: > > I was building a markdown document today when my document suddenly went > blank. When I looked at the HTML source, I found that all my codeblocks had > been MD5ified. The following is a minimal document which reproduces the > error: > > > > # Header # > > > > > > This is a codeblock. > > > > **Bold text** > > > > In particular, there must be: > > ? A header > > ? A comment containing the sequence NEWLINE TAB followed by at > least two greater-than signs > > ? At least one codeblock > > ? Bold text > > ? Another comment at the end of the document. > > Changing even the smallest detail in the markdown results in a correct > HTML document, as expected. > > > > When I run this through markdown v.1.0.1, I get: > >

Header

> > > > > > > > What on earth is going on here, and who do I report this bug to? > Thank you, Fletcher and Waylan, for your help! -------------- next part -------------- An HTML attachment was scrubbed... URL: