diff --git a/Markdown.pl b/Markdown.pl index 186fd57..73e796a 100755 --- a/Markdown.pl +++ b/Markdown.pl @@ -194,7 +194,7 @@ if ($_haveMT) { my $plugin = new MT::Plugin({ name => "Markdown", description => "A plain-text-to-HTML formatting plugin. (Version: $VERSION)", - doc_link => 'http://daringfireball.net/projects/markdown/' + doc_link => 'https://daringfireball.net/projects/markdown/' }); MT->add_plugin( $plugin ); } @@ -216,7 +216,7 @@ if ($_haveMT) { MT->add_text_filter('markdown' => { label => 'Markdown', - docs => 'http://daringfireball.net/projects/markdown/', + docs => 'https://daringfireball.net/projects/markdown/', on_format => sub { my $text = shift; my $ctx = shift; @@ -252,7 +252,7 @@ if ($_haveMT) { if ($smartypants) { MT->add_text_filter('markdown_with_smartypants' => { label => 'Markdown With SmartyPants', - docs => 'http://daringfireball.net/projects/markdown/', + docs => 'https://daringfireball.net/projects/markdown/', on_format => sub { my $text = shift; my $ctx = shift; @@ -2836,7 +2836,7 @@ sub _EncodeEmailAddress { # @example.com # # Based on a filter by Matthew Wickline, posted to the BBEdit-Talk -# mailing list: +# mailing list: # my ($addr, $prefix, $suffix) = @_; @@ -2903,7 +2903,7 @@ sub _TokenizeHTML { # # # Derived from the _tokenize() subroutine from Brad Choate's MTRegex plugin. -# +# # my $str = shift; @@ -3627,9 +3627,9 @@ Z<> See the F file for detailed release notes for this version. =item John Gruber -=item L +=item L -=item L +=item L =item E<160> @@ -3639,7 +3639,7 @@ Z<> See the F file for detailed release notes for this version. =item PHP port and other contributions by Michel Fortin -=item L +=item L =item E<160> diff --git a/README b/README index e92daeb..1298346 100644 --- a/README +++ b/README @@ -66,7 +66,7 @@ MT 3.0 or later). option is the same as the regular "Markdown" formatter, except that automatically uses SmartyPants to create typographically correct curly quotes, em-dashes, and ellipses. See the SmartyPants web page - for more information: + for more information: 4. To make Markdown (or "Markdown with SmartyPants") your default text formatting option for new posts, go to Weblog Config -> @@ -96,7 +96,7 @@ Markdown works with Blosxom version 2.x. rather than all of them, see Jason Clark's instructions for using Markdown in conjunction with Blosxom's Meta plugin: - + BBEdit @@ -453,7 +453,7 @@ Version History + Fixed problem for links defined with urls that include parens, e.g.: - [1]: http://sources.wikipedia.org/wiki/Middle_East_Policy_(Chomsky) + [1]: https://sources.wikipedia.org/wiki/Middle_East_Policy_(Chomsky) "Chomsky" was being erroneously treated as the URL's title. diff --git a/basics.md b/basics.md index f5925d4..6cebb09 100644 --- a/basics.md +++ b/basics.md @@ -251,15 +251,15 @@ you define elsewhere in your document: I get 10 times more traffic from [Google][1] than from [Yahoo][2] or [MSN][3]. - [1]: http://google.com/ "Google" - [2]: http://search.yahoo.com/ "Yahoo Search" - [3]: http://search.msn.com/ "MSN Search" + [1]: https://google.com/ "Google" + [2]: https://search.yahoo.com/ "Yahoo Search" + [3]: https://search.msn.com/ "MSN Search" Output: -

I get 10 times more traffic from Google than from Yahoo or I get 10 times more traffic from Google than from Yahoo or MSN.

The title attribute is optional. Link names may contain letters, @@ -268,12 +268,12 @@ numbers and spaces, but are *not* case sensitive: I start my morning with a cup of coffee and [The New York Times][NY Times]. - [ny times]: http://www.nytimes.com/ + [ny times]: https://www.nytimes.com/ Output:

I start my morning with a cup of coffee and - The New York Times.

+ The New York Times.

~~~~~~ diff --git a/syntax.md b/syntax.md index c1d08b5..4d277f2 100644 --- a/syntax.md +++ b/syntax.md @@ -58,11 +58,11 @@ filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [Grutatext] [5], and [EtText] [6] -- the single biggest source of inspiration for Markdown's syntax is the format of plain text email. - [1]: http://docutils.sourceforge.net/mirror/setext.html + [1]: https://docutils.sourceforge.io/mirror/setext.html [2]: http://www.aaronsw.com/2002/atx/ - [3]: http://textism.com/tools/textile/ - [4]: http://docutils.sourceforge.net/rst.html - [5]: http://www.triptico.com/software/grutatxt.html + [3]: https://www.booked.net/textism.html + [4]: https://docutils.sourceforge.io/rst.html + [5]: https://triptico.com/software/grutatxt.html [6]: http://ettext.taint.org/doc/ To this end, Markdown's syntax is comprised entirely of punctuation @@ -139,11 +139,11 @@ Ampersands in particular are bedeviling for web writers. If you want to write about 'AT&T', you need to write '`AT&T`'. You even need to escape ampersands within URLs. Thus, if you want to link to: - http://images.google.com/images?num=30&q=larry+bird + https://images.google.com/images?num=30&q=larry+bird you need to encode the URL as: - http://images.google.com/images?num=30&q=larry+bird + https://images.google.com/images?num=30&q=larry+bird in your anchor tag `href` attribute. Needless to say, this is easy to forget, and is probably the single most common source of HTML validation @@ -924,7 +924,7 @@ Or even just this: And then define the link: - [Google]: http://google.com/ + [Google]: https://google.com/ Because link names may contain spaces, this shortcut even works for multiple words in the link text: @@ -933,7 +933,7 @@ multiple words in the link text: And then define the link: - [Daring Fireball]: http://daringfireball.net/ + [Daring Fireball]: https://daringfireball.net/ Text inside square brackets is left completely unchanged (including the surrounding brackets) _unless_ it matches a link definition. Furthermore, @@ -977,32 +977,32 @@ Here's an example of reference links in action: I get 10 times more traffic from [Google] [1] than from [Yahoo] [2] or [MSN] [3]. - [1]: http://google.com/ "Google" - [2]: http://search.yahoo.com/ "Yahoo Search" - [3]: http://search.msn.com/ "MSN Search" + [1]: https://google.com/ "Google" + [2]: https://search.yahoo.com/ "Yahoo Search" + [3]: https://search.msn.com/ "MSN Search" Using the implicit link name shortcut, you could instead write: I get 10 times more traffic from [Google] than from [Yahoo] or [MSN]. - [google]: http://google.com/ "Google" - [yahoo]: http://search.yahoo.com/ "Yahoo Search" - [msn]: http://search.msn.com/ "MSN Search" + [google]: https://google.com/ "Google" + [yahoo]: https://search.yahoo.com/ "Yahoo Search" + [msn]: https://search.msn.com/ "MSN Search" Both of the above examples will produce the following HTML output: -

I get 10 times more traffic from I get 10 times more traffic from Google than from - Yahoo - or MSN.

+ Yahoo + or MSN.

For comparison, here is the same paragraph written using Markdown's inline link style: - I get 10 times more traffic from [Google](http://google.com/ "Google") - than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or - [MSN](http://search.msn.com/ "MSN Search"). + I get 10 times more traffic from [Google](https://google.com/ "Google") + than from [Yahoo](https://search.yahoo.com/ "Yahoo Search") or + [MSN](https://search.msn.com/ "MSN Search"). The point of reference-style links is not that they're easier to write. The point is that with reference-style links, your document