Public-Mirrors
/
markdown
mirror of https://github.com/mackyle/markdown.git
1
0
Fork 0
Code Releases Activity
Browse Source

various: update links to https where possible 

Additionally, update a few that now redirect elsewhere.

Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
master
Kyle J. McKay 5 years ago
parent
4174281293
commit
18d217abe3
4 changed files with 39 additions and 39 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 16
      Markdown.pl
  2. 6
      README
  3. 16
      basics.md
  4. 40
      syntax.md

16
Markdown.pl
View File

@ -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 {
# &#64;&#101;x&#x61;&#109;&#x70;&#108;&#x65;&#x2E;&#99;&#111;&#109;</a>
#
# Based on a filter by Matthew Wickline, posted to the BBEdit-Talk
# mailing list: <http://tinyurl.com/yu7ue>
# mailing list: <https://tinyurl.com/yu7ue>
#
my ($addr, $prefix, $suffix) = @_;
@ -2903,7 +2903,7 @@ sub _TokenizeHTML {
#
#
# Derived from the _tokenize() subroutine from Brad Choate's MTRegex plugin.
# <http://www.bradchoate.com/past/mtregex.php>
# <https://web.archive.org/web/20041215155739/http://bradchoate.com/weblog/2002/07/27/mtregex>
#
my $str = shift;
@ -3627,9 +3627,9 @@ Z<> See the F<README> file for detailed release notes for this version.
=item John Gruber
=item L<http://daringfireball.net>
=item L<https://daringfireball.net>
=item L<http://daringfireball.net/projects/markdown/>
=item L<https://daringfireball.net/projects/markdown/>
=item E<160>
@ -3639,7 +3639,7 @@ Z<> See the F<README> file for detailed release notes for this version.
=item PHP port and other contributions by Michel Fortin
=item L<http://michelf.com>
=item L<https://michelf.ca>
=item E<160>

6
README
View File

@ -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: <http://daringfireball.net/projects/smartypants/>
for more information: <https://daringfireball.net/projects/smartypants/>
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:
<http://jclark.org/weblog/WebDev/Blosxom/Markdown.html>
<https://jclark.org/weblog/WebDev/Blosxom/Markdown.html>
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.

16
basics.md
View File

@ -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:
<p>I get 10 times more traffic from <a href="http://google.com/"
title="Google">Google</a> than from <a href="http://search.yahoo.com/"
title="Yahoo Search">Yahoo</a> or <a href="http://search.msn.com/"
<p>I get 10 times more traffic from <a href="https://google.com/"
title="Google">Google</a> than from <a href="https://search.yahoo.com/"
title="Yahoo Search">Yahoo</a> or <a href="https://search.msn.com/"
title="MSN Search">MSN</a>.</p>
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:
<p>I start my morning with a cup of coffee and
<a href="http://www.nytimes.com/">The New York Times</a>.</p>
<a href="https://www.nytimes.com/">The New York Times</a>.</p>
~~~~~~

40
syntax.md
View File

@ -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&amp;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&amp;q=larry+bird
https://images.google.com/images?num=30&amp;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:
<p>I get 10 times more traffic from <a href="http://google.com/"
<p>I get 10 times more traffic from <a href="https://google.com/"
title="Google">Google</a> than from
<a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a>
or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>
<a href="https://search.yahoo.com/" title="Yahoo Search">Yahoo</a>
or <a href="https://search.msn.com/" title="MSN Search">MSN</a>.</p>
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

Write Preview
Loading…
Cancel
Save