Update URLs in the docs.

Mostly http: -> https:, based on a patch by Adam Turner Remove/update some dead links. git-svn-id: https://svn.code.sf.net/p/docutils/code/trunk@8959 929543f6-e4f2-0310-98a6-ba3bd3dd1d04
author: milde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04> 2022-01-21 13:45:42 +0000
committer: milde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04> 2022-01-21 13:45:42 +0000
commit: 35605d7eeed80fd02678f709e85cfe2341edca16 (patch)
tree: 910eb91a045c6c98b9ec1ca195c9c9d37418c6d4 /docutils/docs/dev
parent: b59783bd350f805751f03efb1793a1366929bfb8 (diff)
download: docutils-35605d7eeed80fd02678f709e85cfe2341edca16.tar.gz
9 files changed, 94 insertions, 106 deletions
diff --git a/docutils/docs/dev/distributing.txt b/docutils/docs/dev/distributing.txt
index a42ff477a..e9801e9f5 100644
--- a/docutils/docs/dev/distributing.txt
+++ b/docutils/docs/dev/distributing.txt
@@ -46,7 +46,7 @@ Docutils has the following dependencies:
 .. _Python Imaging Library: 
     https://en.wikipedia.org/wiki/Python_Imaging_Library
 .. _Pillow: https://pypi.org/project/Pillow/
-.. _Pygments: http://pygments.org/
+.. _Pygments: https://pygments.org/
 .. _recommonmark: https://pypi.org/project/recommonmark/
 
 .. _code directives: ../ref/rst/directives.html#code
diff --git a/docutils/docs/dev/hacking.txt b/docutils/docs/dev/hacking.txt
index 9b724a660..17f7d7106 100644
--- a/docutils/docs/dev/hacking.txt
+++ b/docutils/docs/dev/hacking.txt
@@ -32,7 +32,7 @@ Consider the following reStructuredText file::
 
     My *favorite* language is Python_.
 
-    .. _Python: http://www.python.org/
+    .. _Python: https://www.python.org/
 
 Using the ``rst2html.py`` front-end tool, you would get an HTML output
 which looks like this::
@@ -40,7 +40,7 @@ which looks like this::
     [uninteresting HTML code removed]
     <body>
     <div class="document">
-    <p>My <em>favorite</em> language is <a class="reference" href="http://www.python.org/">Python</a>.</p>
+    <p>My <em>favorite</em> language is <a class="reference" href="https://www.python.org/">Python</a>.</p>
     </div>
     </body>
     </html>
@@ -84,7 +84,7 @@ might need to type ``python quicktest.py test.txt``)::
             <reference name="Python" refname="python">
                 Python
             .
-        <target ids="python" names="python" refuri="http://www.python.org/">
+        <target ids="python" names="python" refuri="https://www.python.org/">
 
 Let us now examine the node tree:
 
@@ -106,7 +106,7 @@ Transforming the Document
 -------------------------
 
 In the node tree above, the ``reference`` node does not contain the
-target URI (``http://www.python.org/``) yet.
+target URI (``https://www.python.org/``) yet.
 
 Assigning the target URI (from the ``target`` node) to the
 ``reference`` node is *not* done by the parser (the parser only
@@ -133,10 +133,10 @@ has changed after applying the Transforms, we use the
             <emphasis>
                 favorite
              language is
-            <reference name="Python" **refuri="http://www.python.org/"**>
+            <reference name="Python" **refuri="https://www.python.org/"**>
                 Python
             .
-        <target ids="python" names="python" ``refuri="http://www.python.org/"``>
+        <target ids="python" names="python" ``refuri="https://www.python.org/"``>
 
 For our small test document, the only change is that the ``refname``
 attribute of the reference has been replaced by a ``refuri``
@@ -160,8 +160,8 @@ For HTML output, we can test this using the ``rst2html.py`` tool::
 
     $ rst2html.py --link-stylesheet test.txt
     <?xml version="1.0" encoding="utf-8" ?>
-    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+    <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
     <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     <meta name="generator" content="Docutils 0.3.10: https://docutils.sourceforge.io/" />
@@ -170,7 +170,7 @@ For HTML output, we can test this using the ``rst2html.py`` tool::
     </head>
     <body>
     <div class="document">
-    <p>My <em>favorite</em> language is <a class="reference" href="http://www.python.org/">Python</a>.</p>
+    <p>My <em>favorite</em> language is <a class="reference" href="https://www.python.org/">Python</a>.</p>
     </div>
     </body>
     </html>
diff --git a/docutils/docs/dev/policies.txt b/docutils/docs/dev/policies.txt
index cbea8c491..8025cc75e 100644
--- a/docutils/docs/dev/policies.txt
+++ b/docutils/docs/dev/policies.txt
@@ -98,8 +98,8 @@ Conventions`_ PEPs, summarized, clarified, and extended as follows:
   quotes""" for docstrings.
 
 .. _Style Guide for Python Code:
-   http://www.python.org/peps/pep-0008.html
-.. _Docstring Conventions: http://www.python.org/peps/pep-0257.html
+   https://www.python.org/dev/peps/pep-0008
+.. _Docstring Conventions: https://www.python.org/dev/peps/pep-0257
 .. _Docutils Internationalization: ../howto/i18n.html#python-code
 
 
@@ -230,7 +230,7 @@ discussed on the `docutils-develop mailing list`_ and reviewed before
 being merged into the core.
 
 .. _docutils-develop mailing list:
-   http://lists.sourceforge.net/lists/listinfo/docutils-develop
+   https://lists.sourceforge.net/lists/listinfo/docutils-develop
 
 
 Review Criteria
@@ -534,15 +534,15 @@ snapshot" button in the head of the code listing table).
 
    TODO: do we have active maintenance branches?
    (the only branch looking like a maintenance branch is
-   http://sourceforge.net/p/docutils/code/HEAD/tree/branches/docutils-0.4)
+   https://sourceforge.net/p/docutils/code/HEAD/tree/branches/docutils-0.4)
 
 * `development branches`_, representing ongoing development efforts to bring
   new features into Docutils.
 
 .. _Docutils core:
-   http://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils
+   https://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils
 .. _development branches:
-   http://sourceforge.net/p/docutils/code/HEAD/tree/branches/
+   https://sourceforge.net/p/docutils/code/HEAD/tree/branches/
 
 
 Setting Up For Docutils Development
@@ -626,7 +626,7 @@ Docutils, may graduate to become `parallel projects`_.
 
 .. _sandbox README: https://docutils.sourceforge.io/sandbox/README.html
 .. _sandbox directory:
-   http://sourceforge.net/p/docutils/code/HEAD/tree/trunk/sandbox/
+   https://sourceforge.net/p/docutils/code/HEAD/tree/trunk/sandbox/
 
 
 .. _parallel project:
diff --git a/docutils/docs/dev/release.txt b/docutils/docs/dev/release.txt
index 1a1ed4eb4..4d07186b9 100644
--- a/docutils/docs/dev/release.txt
+++ b/docutils/docs/dev/release.txt
@@ -8,7 +8,7 @@
 :Revision: $Revision$
 :Copyright: This document has been placed in the public domain.
 
-.. _Docutils: http://docutils.sourceforge.io/
+.. _Docutils: https://docutils.sourceforge.io/
 
 Releasing (post 2020)
 ---------------------
diff --git a/docutils/docs/dev/repository.txt b/docutils/docs/dev/repository.txt
index fbe89f781..f1c500276 100644
--- a/docutils/docs/dev/repository.txt
+++ b/docutils/docs/dev/repository.txt
@@ -45,7 +45,7 @@ __ policies.html#subversion-repository
 .. _SVN:
 .. _Subversion: https://subversion.apache.org/
 .. _TortoiseSVN: https://tortoisesvn.net/
-.. _SourceForge.net: http://sourceforge.net/
+.. _SourceForge.net: https://sourceforge.net/
 .. _Git: http://git-scm.com/
 
 .. contents::
@@ -58,7 +58,7 @@ Web Access
 ----------
 
 The repository can be browsed and examined via the web at
-http://sourceforge.net/p/docutils/code.
+https://sourceforge.net/p/docutils/code.
 
 Alternatively, use the web interface at http://repo.or.cz/docutils.git.
 [#github-mirrors]_
@@ -237,7 +237,7 @@ changes to the repository.)
 
 Sourceforge SVN access is documented `here`__
 
-__ http://sourceforge.net/p/forge/documentation/svn/
+__ https://sourceforge.net/p/forge/documentation/svn/
 
 
 Ensure any changes comply with the `Docutils Project Policies`_
diff --git a/docutils/docs/dev/rst/alternatives.txt b/docutils/docs/dev/rst/alternatives.txt
index 885438a41..01af73248 100644
--- a/docutils/docs/dev/rst/alternatives.txt
+++ b/docutils/docs/dev/rst/alternatives.txt
@@ -31,8 +31,7 @@ The ideas are divided into sections:
   won't be implemented, but you never know.
 
 .. _Setext: https://docutils.sourceforge.io/mirror/setext.html
-.. _StructuredText:
-   http://www.zope.org/DevHome/Members/jim/StructuredTextWiki/FrontPage
+.. _StructuredText: https://zopestructuredtext.readthedocs.org/
 .. _Problems with StructuredText: problems.html
 .. _reStructuredText Markup Specification:
    ../../ref/rst/restructuredtext.html
@@ -155,7 +154,7 @@ implement the bibliographic elements explicitly.  For example, there
 would be no need for such a transformation for an XML-based markup
 syntax.
 
-.. _RFC822: http://www.rfc-editor.org/rfc/rfc822.txt
+.. _RFC822: https://www.rfc-editor.org/rfc/rfc822.txt
 
 
 Interpreted Text "Roles"
@@ -287,21 +286,21 @@ Alan Jaffray came up with this idea, along with the following syntax::
 
     Search the `Python DOC-SIG mailing list archives`{}_.
 
-    .. _: http://mail.python.org/pipermail/doc-sig/
+    .. _: https://mail.python.org/pipermail/doc-sig/
 
 The idea is sound and useful.  I suggested a "double underscore"
 syntax::
 
     Search the `Python DOC-SIG mailing list archives`__.
 
-    .. __: http://mail.python.org/pipermail/doc-sig/
+    .. __: https://mail.python.org/pipermail/doc-sig/
 
 But perhaps single underscores are okay?  The syntax looks better, but
 the hyperlink itself doesn't explicitly say "anonymous"::
 
     Search the `Python DOC-SIG mailing list archives`_.
 
-    .. _: http://mail.python.org/pipermail/doc-sig/
+    .. _: https://mail.python.org/pipermail/doc-sig/
 
 Mixing anonymous and named hyperlinks becomes confusing.  The order of
 targets is not significant for named hyperlinks, but it is for
@@ -696,7 +695,7 @@ Syntax alternatives for the definition:
        I had lunch with Jonathan_ today.  We talked about Zope_.
 
        .. _Jonathan: lj [user=jhl]
-       .. _Zope: http://www.zope.org/
+       .. _Zope: https://www.zope.dev/
 
    A problem with the proposed syntax is that URIs which look like
    simple reference names (alphanum plus ".", "-", "_") would be
@@ -706,7 +705,7 @@ Syntax alternatives for the definition:
        I had lunch with Jonathan_ today.  We talked about Zope_.
 
        .. _Jonathan: lj:: user=jhl
-       .. _Zope: http://www.zope.org/
+       .. _Zope: https://www.zope.dev/
 
    (``::`` after ``.. _Jonathan: lj``.)
 
@@ -748,7 +747,7 @@ allows us to click on an image-link::
 
     .. |biohazard| image:: biohazard.png
        [height=20 width=20]
-    .. _biohazard: http://www.cdc.gov/
+    .. _biohazard: https://www.cdc.gov/
 
 There have been several suggestions for the naming of these
 constructs, originally called "substitution references" and
@@ -829,9 +828,9 @@ Currently reStructuredText has two hyperlink syntax variations:
       a `phrase reference`_.  Phrase references may even cross `line
       boundaries`_.
 
-      .. _reference: http://www.example.org/reference/
-      .. _phrase reference: http://www.example.org/phrase_reference/
-      .. _line boundaries: http://www.example.org/line_boundaries/
+      .. _reference: https://www.example.org/reference/
+      .. _phrase reference: https://www.example.org/phrase_reference/
+      .. _line boundaries: https://www.example.org/line_boundaries/
 
   + Advantages:
 
@@ -853,9 +852,9 @@ Currently reStructuredText has two hyperlink syntax variations:
       `phrase reference`__.  Phrase references may even cross `line
       boundaries`__.
 
-      __ http://www.example.org/reference/
-      __ http://www.example.org/phrase_reference/
-      __ http://www.example.org/line_boundaries/
+      __ https://www.example.org/reference/
+      __ https://www.example.org/phrase_reference/
+      __ https://www.example.org/line_boundaries/
 
   + Advantages:
 
@@ -873,15 +872,15 @@ syntaxes for hyperlinks:
 
 * First, ``"reference text":URL``::
 
-      This is a "reference":http://www.example.org/reference/
+      This is a "reference":https://www.example.org/reference/
       of one word ("reference").  Here is a "phrase
-      reference":http://www.example.org/phrase_reference/.
+      reference":https://www.example.org/phrase_reference/.
 
-* Second, ``"reference text", http://example.com/absolute_URL``::
+* Second, ``"reference text", https://example.org/absolute_URL``::
 
-      This is a "reference", http://www.example.org/reference/
+      This is a "reference", https://www.example.org/reference/
       of one word ("reference").  Here is a "phrase reference",
-      http://www.example.org/phrase_reference/.
+      https://www.example.org/phrase_reference/.
 
 Both syntaxes share advantages and disadvantages:
 
@@ -905,14 +904,14 @@ A new type of "inline external hyperlink" has been proposed.
 1. On 2002-06-28, Simon Budig proposed__ a new syntax for
    reStructuredText hyperlinks::
 
-       This is a reference_(http://www.example.org/reference/) of one
+       This is a reference_(https://www.example.org/reference/) of one
        word ("reference").  Here is a `phrase
-       reference`_(http://www.example.org/phrase_reference/).  Are
+       reference`_(https://www.example.org/phrase_reference/).  Are
        these examples, (single-underscore), named?  If so, `anonymous
-       references`__(http://www.example.org/anonymous/) using two
+       references`__(https://www.example.org/anonymous/) using two
        underscores would probably be preferable.
 
-   __ http://mail.python.org/pipermail/doc-sig/2002-June/002648.html
+   __ https://mail.python.org/pipermail/doc-sig/2002-June/002648.html
 
    The syntax, advantages, and disadvantages are similar to those of
    StructuredText.
@@ -953,13 +952,13 @@ A new type of "inline external hyperlink" has been proposed.
    following compromise syntax::
 
        This is an anonymous reference__
-       __<http://www.example.org/reference/> of one word
+       __<https://www.example.org/reference/> of one word
        ("reference").  Here is a `phrase reference`__
-       __<http://www.example.org/phrase_reference/>.  `Named
-       references`_ _<http://www.example.org/anonymous/> use single
+       __<https://www.example.org/phrase_reference/>.  `Named
+       references`_ _<https://www.example.org/anonymous/> use single
        underscores.
 
-   __ http://mail.python.org/pipermail/doc-sig/2002-July/002670.html
+   __ https://mail.python.org/pipermail/doc-sig/2002-July/002670.html
 
    The syntax builds on that of the existing "inline internal
    targets": ``an _`inline internal target`.``
@@ -989,8 +988,8 @@ A new type of "inline external hyperlink" has been proposed.
    target to appear later, such as after the end of the sentence::
 
        This is a named reference__ of one word ("reference").
-       __<http://www.example.org/reference/>  Here is a `phrase
-       reference`__.  __<http://www.example.org/phrase_reference/>
+       __<https://www.example.org/reference/>  Here is a `phrase
+       reference`__.  __<https://www.example.org/phrase_reference/>
 
    Problem: this could only work for one reference at a time
    (reference/target pairs must be proximate [refA trgA refB trgB],
@@ -1030,9 +1029,9 @@ A new type of "inline external hyperlink" has been proposed.
    Here's an alternative syntax embedding the target URL in the
    reference::
 
-       This is an anonymous `reference <http://www.example.org
+       This is an anonymous `reference <https://www.example.org
        /reference/>`__ of one word ("reference").  Here is a `phrase
-       reference <http://www.example.org/phrase_reference/>`__.
+       reference <https://www.example.org/phrase_reference/>`__.
 
    Advantages and disadvantages are similar to those in (2).
    Readability is still an issue, but the syntax is a bit less
@@ -1045,7 +1044,7 @@ A new type of "inline external hyperlink" has been proposed.
    Problem: how to refer to a title like "HTML Anchors: <a>" (which
    ends with an HTML/SGML/XML tag)?  We could either require more
    syntax on the target (like ``"`reference text
-   __<http://example.com/>`__"``), or require the odd conflicting
+   __<https://example.org/>`__"``), or require the odd conflicting
    title to be escaped (like ``"`HTML Anchors: \<a>`__"``).  The
    latter seems preferable, and not too onerous.
 
@@ -1058,17 +1057,17 @@ A new type of "inline external hyperlink" has been proposed.
 Other syntax variations have been proposed (by Brett Cannon and Benja
 Fallenstein)::
 
-    `phrase reference`->http://www.example.com
+    `phrase reference`->https://www.example.org
 
-    `phrase reference`@http://www.example.com
+    `phrase reference`@https://www.example.org
 
-    `phrase reference`__ ->http://www.example.com
+    `phrase reference`__ ->https://www.example.org
 
-    `phrase reference` [-> http://www.example.com]
+    `phrase reference` [-> https://www.example.org]
 
-    `phrase reference`__ [-> http://www.example.com]
+    `phrase reference`__ [-> https://www.example.org]
 
-    `phrase reference` <http://www.example.com>_
+    `phrase reference` <https://www.example.org>_
 
 None of these variations are clearly superior to #3 above.  Some have
 problems that exclude their use.
@@ -1239,7 +1238,7 @@ There are several possibilities for the implementation:
 
 Solution 3 was chosen for incorporation into the document tree model.
 
-.. _HTML: http://www.w3.org/MarkUp/
+.. _HTML: https://www.w3.org/MarkUp/
 
 
 Syntax for Line Blocks
@@ -1288,7 +1287,7 @@ Syntax for Line Blocks
        | President, SuperDuper Corp.
        | jdoe@example.org
 
-  __ http://thread.gmane.org/gmane.text.docutils.devel/1187
+  __ https://thread.gmane.org/gmane.text.docutils.devel/1187
 
   This syntax is very natural.  However, these "plain lists" seem very
   similar to line blocks, and I see so little intrinsic "list-ness"
@@ -1807,7 +1806,7 @@ ugly or confusing (depending on which alternative is chosen).
    auto-numbered lists be limited to begin with ordinal-1 ("1", "A",
    "a", "I", or "i")?
 
-   __ http://sourceforge.net/tracker/index.php?func=detail&aid=548802
+   __ https://sourceforge.net/tracker/index.php?func=detail&aid=548802
       &group_id=38414&atid=422032
 
 4. Alternative proposed by Tony Ibbs::
@@ -1886,7 +1885,7 @@ b) full backwards compatibility
 .. _Inline markup recognition rules:
    ../../ref/rst/restructuredtext.html#inline-markup-recognition-rules
 .. _Unicode categories:
-   http://www.unicode.org/Public/5.1.0/ucd/UCD.html#General_Category_Values
+   https://www.unicode.org/Public/5.1.0/ucd/UCD.html#General_Category_Values
 
 
 -----------------
@@ -2006,12 +2005,12 @@ Syntax proposals:
   - Current syntax (footnote syntax)::
 
         .. [GVR2001] Python Documentation; van Rossum, Drake, et al.;
-           http://www.python.org/doc/
+           https://www.python.org/doc/
 
   - Possible new syntax::
 
         _[GVR2001] Python Documentation; van Rossum, Drake, et al.;
-                   http://www.python.org/doc/
+                   https://www.python.org/doc/
 
         _[DJG2002]
             Docutils: Python Documentation Utilities project; Goodger
@@ -2022,7 +2021,7 @@ Syntax proposals:
     alignment (I'd rather not)::
 
         _[GVR2001] Python Documentation; van Rossum, Drake, et al.;
-            http://www.python.org/doc/
+            https://www.python.org/doc/
 
 I proposed adopting the "minimal" syntax for footnotes and footnote
 references, and adding citations and citation references to
@@ -2209,7 +2208,7 @@ in RST markup`__.  Several arguments were made; the first argument
 begat later arguments.  Below, the arguments are paraphrased "in
 quotes", with responses.
 
-__ http://thread.gmane.org/gmane.text.docutils.devel/1386
+__ https://thread.gmane.org/gmane.text.docutils.devel/1386
 
 1. References and targets take this form::
 
@@ -2407,9 +2406,9 @@ mailing list messages should be referred to for details.
       inside what must be well thought out first though.
 
       .. _Ed Loper's 2001-03-21 post:
-         http://mail.python.org/pipermail/doc-sig/2001-March/001487.html
+         https://mail.python.org/pipermail/doc-sig/2001-March/001487.html
 
-      -- http://mail.python.org/pipermail/doc-sig/2001-October/002354.html
+      -- https://mail.python.org/pipermail/doc-sig/2001-October/002354.html
 
 * In a 2001-11-09 Doc-SIG post, I wrote:
 
@@ -2426,7 +2425,7 @@ mailing list messages should be referred to for details.
       markup. The first algorithm ("first identify the outer inline
       markup as we do now, then recursively scan for nested inline
       markup") won't work; counterexamples were given in my `last post
-      <http://mail.python.org/pipermail/doc-sig/2001-November/002363.html>`__.
+      <https://mail.python.org/pipermail/doc-sig/2001-November/002363.html>`__.
 
       The second algorithm makes my head hurt::
 
@@ -2457,7 +2456,7 @@ mailing list messages should be referred to for details.
       at least not now. If somebody codes up a consistent, working,
       general solution, I'll be happy to consider it.
 
-      -- http://mail.python.org/pipermail/doc-sig/2001-November/002388.html
+      -- https://mail.python.org/pipermail/doc-sig/2001-November/002388.html
 
 * In a `2003-05-06 Docutils-Users post`__ Paul Tremblay proposed a new
   syntax to allow for easier nesting.  It eventually evolved into
@@ -2468,7 +2467,7 @@ mailing list messages should be referred to for details.
   The duplication with the existing interpreted text syntax is
   problematic though.
 
-  __ http://article.gmane.org/gmane.text.docutils.user/317
+  __ https://article.gmane.org/gmane.text.docutils.user/317
 
 * Could the parser be extended to parse nested interpreted text? ::
 
@@ -2481,7 +2480,7 @@ mailing list messages should be referred to for details.
   ideas.  The implementation was flawed, however, by the change in
   semantics required for backslash escapes.
 
-  __ http://article.gmane.org/gmane.text.docutils.devel/795
+  __ https://article.gmane.org/gmane.text.docutils.devel/795
 
 * Docutils-develop threads between David Abrahams, David Goodger, and
   Mark Nodine (beginning 2004-01-16__ and 2004-01-19__) hashed out
@@ -2489,8 +2488,8 @@ mailing list messages should be referred to for details.
   described below.  David Abrahams checked in code to the "nesting"
   branch of CVS, awaiting thorough review.
 
-  __ http://thread.gmane.org/gmane.text.docutils.devel/1102
-  __ http://thread.gmane.org/gmane.text.docutils.devel/1125
+  __ https://thread.gmane.org/gmane.text.docutils.devel/1102
+  __ https://thread.gmane.org/gmane.text.docutils.devel/1125
 
 It may be possible to accomplish nested inline markup in general with
 a more powerful inline markup parser.  There may be some issues, but
@@ -2704,9 +2703,9 @@ See the `Doc-SIG discussion starting 2001-04-18`__ with Ed Loper's
 follow-ups, here__ and here__).  Also `docutils-users, 2003-02-17`__
 and `beginning 2003-08-04`__.
 
-__ http://mail.python.org/pipermail/doc-sig/2001-April/001776.html
-__ http://mail.python.org/pipermail/doc-sig/2001-April/001789.html
-__ http://mail.python.org/pipermail/doc-sig/2001-April/001793.html
+__ https://mail.python.org/pipermail/doc-sig/2001-April/001776.html
+__ https://mail.python.org/pipermail/doc-sig/2001-April/001789.html
+__ https://mail.python.org/pipermail/doc-sig/2001-April/001793.html
 __ https://sourceforge.net/mailarchive/message.php?msg_id=3838913
 __ https://sf.net/mailarchive/forum.php?thread_id=2957175&forum_id=11444
 
diff --git a/docutils/docs/dev/rst/problems.txt b/docutils/docs/dev/rst/problems.txt
index d6397dfa0..f44774263 100644
--- a/docutils/docs/dev/rst/problems.txt
+++ b/docutils/docs/dev/rst/problems.txt
@@ -847,8 +847,7 @@ reStructuredText's syntax (#4) is definitely the most readable.  The
 text is separated from the link URI and the footnote, resulting in
 cleanly readable text.
 
-.. _StructuredText:
-   http://www.zope.org/DevHome/Members/jim/StructuredTextWiki/FrontPage
+.. _StructuredText: https://zopestructuredtext.readthedocs.org/
 .. _Setext: https://docutils.sourceforge.io/mirror/setext.html
 .. _reStructuredText: https://docutils.sourceforge.io/rst.html
 .. _detailed description:
diff --git a/docutils/docs/dev/semantics.txt b/docutils/docs/dev/semantics.txt
index f56fccebf..38d19dab6 100644
--- a/docutils/docs/dev/semantics.txt
+++ b/docutils/docs/dev/semantics.txt
@@ -101,13 +101,13 @@ Other Ideas
   an attachment to his Doc-SIG post of 2001-05-30.
 
 
-.. _PEP 257: http://www.python.org/peps/pep-0257.html
+.. _PEP 257: https://www.python.org/dev/peps/pep-0257
 .. _JavaDoc: http://java.sun.com/j2se/javadoc/
 .. _pythondoc: http://starship.python.net/crew/danilo/pythondoc/
 .. _Grouch: http://www.mems-exchange.org/software/grouch/
 .. _epydoc: http://epydoc.sourceforge.net/
 .. _iPhrase Python documentation conventions:
-   http://mail.python.org/pipermail/doc-sig/2001-May/001840.html
+   https://mail.python.org/pipermail/doc-sig/2001-May/001840.html
 
 
 ..
diff --git a/docutils/docs/dev/todo.txt b/docutils/docs/dev/todo.txt
index 9966b4af3..7cace8b0c 100644
--- a/docutils/docs/dev/todo.txt
+++ b/docutils/docs/dev/todo.txt
@@ -19,17 +19,7 @@ the priority.  Items in question form (containing "?") are ideas which
 require more thought and debate; they are potential to-do's.
 
 Many of these items are awaiting champions.  If you see something
-you'd like to tackle, please do!  If there's something you'd like to
-see done but are unable to implement it yourself, please consider
-donating to Docutils: |donate|
-
-.. |donate| image:: http://images.sourceforge.net/images/project-support.jpg
-   :target: http://sourceforge.net/donate/index.php?group_id=38414
-   :align: middle
-   :width: 88
-   :height: 32
-   :alt: Support the Docutils project!
-
+you'd like to tackle, please do!
 Please see also the Bugs_ document for a list of bugs in Docutils.
 
 .. _bugs: ../../BUGS.html
@@ -971,7 +961,7 @@ Misc
 
 * Support generic hyperlink references to _`targets in other
   documents`?  Not in an HTML-centric way, though (it's trivial to say
-  ``http://www.example.com/doc#name``, and useless in non-HTML
+  ``https://www.example.org/doc#name``, and useless in non-HTML
   contexts).  XLink/XPointer?  ``.. baseref::``?  See Doc-SIG
   2001-08-10.
 
@@ -1025,7 +1015,7 @@ Misc
   Appendix E ("Recommendations for Delimiting URI in Context") of `RFC
   2396`_.
 
-  .. _RFC 2396: http://www.rfc-editor.org/rfc/rfc2396.txt
+  .. _RFC 2396: https://www.rfc-editor.org/rfc/rfc2396.txt
 
 * Use the vertical spacing of the source text to determine the
   corresponding vertical spacing of the output?
@@ -1156,7 +1146,7 @@ Misc
   grid tables inside XML comments.
 
   .. _feature request [6]:
-      http://sourceforge.net/p/docutils/feature-requests/6
+      https://sourceforge.net/p/docutils/feature-requests/6
   .. _list-table: ../ref/rst/directives.html#list-table
 
 
@@ -1428,7 +1418,7 @@ MathML_
   For an overview of MathML implementations and tests, see, e.g.,
   the `mathweb wiki`_ or the `ConTeXT MathML page`_.
 
-  .. _MathML: http://www.w3.org/TR/MathML2/
+  .. _MathML: https://www.w3.org/TR/MathML2/
   .. _mathweb wiki: http://www.mathweb.org/wiki/MathML
   .. _ConTeXT MathML page: http://wiki.contextgarden.net/MathML
 
@@ -1462,7 +1452,7 @@ ASCIIMath_
   .. _ASCIIMath tutorial:
      http://www.wjagray.co.uk/maths/ASCIIMathTutorial.html
   .. _ASCIIMathML: http://pypi.python.org/pypi/asciimathml/
-  .. _ASCIIMathPython: http://sourceforge.net/projects/asciimathpython/
+  .. _ASCIIMathPython: https://github.com/paulhtremblay/asciimathml
   __ http://fletcherpenney.net/multimarkdown/
 
 `Unicode Nearly Plain Text Encoding of Mathematics`_
@@ -1474,7 +1464,7 @@ ASCIIMath_
    the Unicode Consortium.)
 
    .. _Unicode Nearly Plain Text Encoding of Mathematics:
-      http://www.unicode.org/notes/tn28/
+      https://www.unicode.org/notes/tn28/
 
 itex
   See `the culmination of a relevant discussion in 2003
@@ -1539,7 +1529,7 @@ MathML_
     * the Unicode-Char <-> LaTeX mappings database unimathsymbols_
 
   __ http://msevior.livejournal.com/26377.html
-  .. _MathML: http://www.w3.org/TR/MathML2/
+  .. _MathML: https://www.w3.org/TR/MathML2/
   .. _ttm: http://hutchinson.belmont.ma.us/tth/mml/
   .. _TeX4ht: http://www.tug.org/applications/tex4ht/mn.html
   .. _MathToWeb:  http://www.mathtoweb.com/
@@ -1712,7 +1702,7 @@ when used in a document.
     - Add support for inclusion by URL? ::
 
           .. include::
-             :url: http://www.example.org/inclusion.txt
+             :url: https://www.example.org/inclusion.txt
 
     - Strip blank lines from begin and end of a literal included file or
       file section. This would correspond to the way a literal block is
@@ -1770,7 +1760,7 @@ when used in a document.
       "language by class attribute" does not change parsing (localized
       directives etc.), only supporting writers.
 
-    .. _BCP 47: http://www.rfc-editor.org/rfc/bcp/bcp47.txt
+    .. _BCP 47: https://www.rfc-editor.org/rfc/bcp/bcp47.txt
 
 
   - _`misc.settings`: Set any(?) Docutils runtime setting from within
@@ -2446,7 +2436,7 @@ Test and consider moving the better one into the docutils core.
 __ ../user/links.html#ePub
 .. _International Digital Publishing Forum: http://www.idpf.org/
 .. _electronic reading devices:
-   http://en.wikipedia.org/wiki/List_of_e-book_readers
+   https://en.wikipedia.org/wiki/List_of_e-book_readers
 
 
 LaTeX writer
@@ -2780,7 +2770,7 @@ but need to find a way to insert it as href argument.
 
 The following fails::
 
-    \href{http://www.w3.org/XML/Schema^^dev}{\fragileURLi}
+    \href{https://www.w3.org/XML/Schema^^dev}{\fragileURLi}
 
 Use %-replacement like http://nowhere/url_with%28parens%29 ?
 
@@ -2814,7 +2804,7 @@ This run will use the default stylesheet, a custom local stylesheet,
 and an external stylesheet:
 
     rstpep2html.py --add-stylesheet-path custom.css \
-        --add-stylesheet http://www.example.org/external.css ...
+        --add-stylesheet https://www.example.org/external.css ...
 
 This run will use only the second custom stylesheet:
author	milde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04>	2022-01-21 13:45:42 +0000
committer	milde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04>	2022-01-21 13:45:42 +0000
commit	35605d7eeed80fd02678f709e85cfe2341edca16 (patch)
tree	910eb91a045c6c98b9ec1ca195c9c9d37418c6d4 /docutils/docs/dev
parent	b59783bd350f805751f03efb1793a1366929bfb8 (diff)
download	docutils-35605d7eeed80fd02678f709e85cfe2341edca16.tar.gz