Markdown 1.0.1现已推出This release was primarily focused on fixing bugs and eliminating certain ambiguities and confusing edge cases in Markdown’s formatting syntax.
更改了代码块和跨度的语法规则Previously, backslash escapes for special Markdown characters were processed everywhere other than within inline HTML tagsNow, the contents of code blocks and spans are no longer processed for backslash escapesThis means that code blocks and spans are now treated literally, with no special rules to worry about regarding backslashes.
注意: This changes the syntax from all previous versions of MarkdownCode blocks and spans involving backslash characters will now generate different output than before.
Tweaked the rules for link definitions so that they must occur within three spaces of the left marginThus if you indent a link definition by four spaces or a tab, it will now be a code block.
注意: This may affect existing Markdown content if it contains link definitions indented by 4 or more spacesThis was never officially supported, but neither was it explicitly disallowed.
-to the list of backslash-escapable charactersThese should have been done when these characters were added as unordered list item markers.
<HR />tags are now ignored.
Added a bit of tolerance for trailing spaces and tabs after Markdown hr’s.
Sort-of fixed a bug where lines in the middle of hard-wrapped paragraphs, which lines look like the start of a list item, would accidentally trigger the creation of a list例如a paragraph that looked like this:
I recommend upgrading to version 8Oops, now this line is treated as a sub-list.
This is fixed for top-level lists, but it can still happen for sub-listsE.g., the following list item will not be parsed properly:
+ I recommend upgrading to version 8Oops, now this line is treated as a sub-list.
Given Markdown’s list-creation rules, I’m not sure this can be fixed.
Standalone HTML comments are now handled; previously, they’d get wrapped in a spurious
<HR>HTML tags in must occur within three spaces of left margin(With 4 spaces or a tab, they should be code blocks, but weren’t before this fix.)
Capitalized “With” in “Markdown With SmartyPants” for consistency with the same string label in SmartyPants.pl. (This fix is specific to the MT plug-in interface.)
Auto-linked email address can now optionally contain a ‘mailto:’ protocol即这些是等价的：
<至mailto：[email protected]> <[email protected]>
Fixed annoying bug where nested lists would wind up with spurious (and invalid)
HREFattributes. This should have worked before, but didn’t.
的<strong> <EM>此</ EM> </强>
的<strong> <EM>此</强> </ em>的
s/\$/$/g;This is only for the benefit of Blosxom users, because Blosxom (sometimes?) interpolates Perl scalars in your article bodies.
At some point during 1.0’s beta cycle, I changed every sub’s argument fetching from this idiom:
我的$ text = shift;
my $text = shift || return '';
The idea was to keep Markdown from doing any work in a sub if the input was emptyThis introduced a bug, though: if the input to any function was the single-character string “0”, it would also evaluate as false and return immediately. How silly现在修好了。