Menu
▾
▴
[Docutils-checkins] SF.net SVN: docutils:[8959] trunk/docutils
|
From: <mi...@us...> - 2022-01-21 13:45:46
|
Revision: 8959
http://sourceforge.net/p/docutils/code/8959
Author: milde
Date: 2022-01-21 13:45:42 +0000 (Fri, 21 Jan 2022)
Log Message:
-----------
Update URLs in the docs.
Mostly http: -> https:, based on a patch by Adam Turner
Remove/update some dead links.
Modified Paths:
--------------
trunk/docutils/BUGS.txt
trunk/docutils/COPYING.txt
trunk/docutils/FAQ.txt
trunk/docutils/HISTORY.txt
trunk/docutils/README.txt
trunk/docutils/RELEASE-NOTES.txt
trunk/docutils/THANKS.txt
trunk/docutils/docs/dev/distributing.txt
trunk/docutils/docs/dev/hacking.txt
trunk/docutils/docs/dev/policies.txt
trunk/docutils/docs/dev/release.txt
trunk/docutils/docs/dev/repository.txt
trunk/docutils/docs/dev/rst/alternatives.txt
trunk/docutils/docs/dev/rst/problems.txt
trunk/docutils/docs/dev/semantics.txt
trunk/docutils/docs/dev/todo.txt
trunk/docutils/docs/howto/i18n.txt
trunk/docutils/docs/ref/doctree.txt
trunk/docutils/docs/ref/rst/definitions.txt
trunk/docutils/docs/ref/rst/directives.txt
trunk/docutils/docs/ref/rst/introduction.txt
trunk/docutils/docs/ref/rst/mathematics.txt
trunk/docutils/docs/ref/rst/restructuredtext.txt
trunk/docutils/docs/ref/rst/roles.txt
trunk/docutils/docs/user/config.txt
trunk/docutils/docs/user/emacs.txt
trunk/docutils/docs/user/html.txt
trunk/docutils/docs/user/latex.txt
trunk/docutils/docs/user/links.txt
trunk/docutils/docs/user/mailing-lists.txt
trunk/docutils/docs/user/odt.txt
trunk/docutils/docs/user/rst/demo.txt
trunk/docutils/docs/user/rst/quickref.html
trunk/docutils/docs/user/slide-shows.txt
trunk/docutils/docs/user/smartquotes.txt
trunk/docutils/docs/user/tools.txt
trunk/docutils/docutils/io.py
trunk/docutils/docutils/nodes.py
trunk/docutils/docutils/utils/__init__.py
trunk/docutils/docutils/utils/smartquotes.py
trunk/docutils/docutils/utils/urischemes.py
trunk/docutils/docutils/writers/html5_polyglot/plain.css
trunk/docutils/docutils/writers/html5_polyglot/responsive.css
trunk/docutils/docutils/writers/html5_polyglot/tuftig.css
trunk/docutils/docutils/writers/latex2e/__init__.py
trunk/docutils/licenses/gpl-3-0.txt
trunk/docutils/licenses/python-2-1-1.txt
trunk/docutils/tools/dev/create_unimap.py
trunk/docutils/tools/dev/generate_punctuation_chars.py
trunk/docutils/tools/dev/unicode2rstsubs.py
Modified: trunk/docutils/BUGS.txt
===================================================================
--- trunk/docutils/BUGS.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/BUGS.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -124,7 +124,7 @@
.. _mailing list archives: https://docutils.sourceforge.io/#mailing-lists
.. _Docutils-users: docs/user/mailing-lists.html#docutils-users
.. _SourceForge Bug Tracker:
- http://sourceforge.net/p/docutils/bugs/
+ https://sourceforge.net/p/docutils/bugs/
Known Bugs
Modified: trunk/docutils/COPYING.txt
===================================================================
--- trunk/docutils/COPYING.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/COPYING.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -28,9 +28,9 @@
The primary repository for the Work is the Internet World Wide Web
site <https://docutils.sourceforge.io/>. The Work consists of the
files within the "docutils" module of the Docutils project Subversion
-repository (Internet host docutils.svn.sourceforge.net, filesystem path
-/svnroot/docutils), whose Internet web interface is located at
-<http://docutils.svn.sourceforge.net/viewvc/docutils/>. Files dedicated to the
+repository (http://svn.code.sf.net/p/docutils/code/),
+whose Internet web interface is located at
+<https://sourceforge.net/p/docutils/code>. Files dedicated to the
public domain may be identified by the inclusion, near the beginning
of each file, of a declaration of the form::
@@ -143,10 +143,10 @@
.. _sandbox: https://docutils.sourceforge.io/sandbox/README.html
.. _licenses: licenses/
-.. _Python 2.1.1 license: http://www.python.org/2.1.1/license.html
-.. _GNU General Public License: http://www.gnu.org/copyleft/gpl.html
+.. _Python 2.1.1 license: https://docs.python.org/3/license.html
+.. _GNU General Public License: https://www.gnu.org/copyleft/gpl.html
.. _BSD 2-Clause License: http://opensource.org/licenses/BSD-2-Clause
.. _BSD 3-Clause License: https://opensource.org/licenses/BSD-3-Clause
.. _OSI-approved: http://opensource.org/licenses/
.. _license-list:
-.. _GPL-compatible: http://www.gnu.org/licenses/license-list.html
+.. _GPL-compatible: https://www.gnu.org/licenses/license-list.html
Modified: trunk/docutils/FAQ.txt
===================================================================
--- trunk/docutils/FAQ.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/FAQ.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -61,13 +61,13 @@
.. _Docutils: https://docutils.sourceforge.io/
.. _PEPs (Python Enhancement Proposals):
- http://www.python.org/peps/pep-0012.html
+ https://www.python.org/dev/peps/pep-0012
.. _can be used by client code: docs/api/publisher.html
.. _front-end tools: docs/user/tools.html
.. _test suite: docs/dev/testing.html
.. _documentation: docs/index.html
-.. _PEP 258: http://www.python.org/peps/pep-0258.html
-.. _Python: http://www.python.org/
+.. _PEP 258: https://www.python.org/dev/peps/pep-0258
+.. _Python: https://www.python.org/
Why is it called "Docutils"?
@@ -99,9 +99,9 @@
UTILitieS", with emphasis on the first syllable.
.. _An Introduction to reStructuredText: docs/ref/rst/introduction.html
-__ http://mail.python.org/pipermail/doc-sig/1999-December/000878.html
-__ http://mail.python.org/pipermail/doc-sig/2000-November/001252.html
-__ http://mail.python.org/pipermail/doc-sig/2000-November/001239.html
+__ https://mail.python.org/pipermail/doc-sig/1999-December/000878.html
+__ https://mail.python.org/pipermail/doc-sig/2000-November/001252.html
+__ https://mail.python.org/pipermail/doc-sig/2000-November/001239.html
__ http://homepage.ntlworld.com/tibsnjoan/docutils/STpy.html
@@ -154,7 +154,7 @@
.. _extensions and related projects:
docs/dev/policies.html#extensions-and-related-projects
.. _feature request tracker:
- http://sourceforge.net/p/docutils/feature-requests/
+ https://sourceforge.net/p/docutils/feature-requests/
reStructuredText
@@ -210,7 +210,7 @@
they overemphasize reStructuredText's predecessor, Zope's
StructuredText.
-__ http://en.wikipedia.org/wiki/Representational_State_Transfer
+__ https://en.wikipedia.org/wiki/Representational_State_Transfer
What's the standard filename extension for a reStructuredText file?
@@ -456,7 +456,7 @@
order:
* `Firedrop <http://www.voidspace.org.uk/python/firedrop2/>`__
-* `PyBloxsom <http://pyblosxom.sourceforge.net/>`__
+* `PyBloxsom <http://pyblosxom.github.io/>`__
* `Lino WebMan <http://lino.sourceforge.net/webman.html>`__
* `Pelican <http://blog.getpelican.com/>`__
(also listed `on PyPi <http://pypi.python.org/pypi/pelican>`__)
@@ -571,7 +571,7 @@
Here is an |emphasized hyperlink|_.
.. |emphasized hyperlink| replace:: *emphasized hyperlink*
- .. _emphasized hyperlink: http://example.org
+ .. _emphasized hyperlink: https://example.org
It is not possible for just a portion of the replacement text to be
a hyperlink; it's the entire replacement text or nothing.
@@ -588,7 +588,7 @@
.. |stuff| raw:: html
<em>emphasized text containing a
- <a href="http://example.org">hyperlink</a> and
+ <a href="https://example.org">hyperlink</a> and
<tt>inline literals</tt></em>
Raw LaTeX is supported for LaTeX output, etc.
@@ -781,7 +781,7 @@
a single base direction for the whole document (like Notepad, Vim and
text boxes in Firefox).
-.. _Unicode Bidi Algorithm: http://www.unicode.org/reports/tr9/
+.. _Unicode Bidi Algorithm: https://www.unicode.org/reports/tr9/
.. _geresh: http://www.typo.co.il/~mooffie/geresh/
.. _translate: docs/howto/i18n.html
@@ -1157,7 +1157,7 @@
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xht ml1/DTD/xhtml1-transitional.dtd">
+ "https://www.w3.org/TR/xht ml1/DTD/xhtml1-transitional.dtd">
But this is followed by::
@@ -1268,7 +1268,7 @@
.. _supported Python versions: README.html#requirements
.. _feature branch: docs/dev/policies.html#feature-branch
.. _Git: http://git-scm.com/
-.. _bug tracker: http://sourceforge.net/p/docutils/bugs/
+.. _bug tracker: https://sourceforge.net/p/docutils/bugs/
Modified: trunk/docutils/HISTORY.txt
===================================================================
--- trunk/docutils/HISTORY.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/HISTORY.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -945,9 +945,9 @@
To use, install the ``tox`` package via pip or easy_install and use
tox from the project root directory.
-.. _polyglot: http://www.w3.org/TR/html-polyglot/
-.. _HTML 5: http://www.w3.org/TR/html5/
-.. _XHTML 1.0: http://www.w3.org/TR/xhtml1/
+.. _polyglot: https://www.w3.org/TR/html-polyglot/
+.. _HTML 5: https://www.w3.org/TR/html5/
+.. _XHTML 1.0: https://www.w3.org/TR/xhtml1/
Release 0.12 (2014-07-06)
@@ -1180,8 +1180,8 @@
via ``import PIL`` as starting with PIL 1.2,
"PIL lives in the PIL namespace only" (announcement__).
-.. _Pygments: http://pygments.org/
-__ http://mail.python.org/pipermail/image-sig/2011-January/006650.html
+.. _Pygments: https://pygments.org/
+__ https://mail.python.org/pipermail/image-sig/2011-January/006650.html
* setup.py
@@ -1298,7 +1298,7 @@
- Some additions to the Docutils core are released under the 2-Clause BSD
license, see COPYING_ for details.
- .. _BCP 47: http://www.rfc-editor.org/rfc/bcp/bcp47.txt
+ .. _BCP 47: https://www.rfc-editor.org/rfc/bcp/bcp47.txt
.. _COPYING: COPYING.html
* reStructuredText:
Modified: trunk/docutils/README.txt
===================================================================
--- trunk/docutils/README.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/README.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -17,7 +17,7 @@
This is for those who want to get up & running quickly.
1. Docutils requires **Python**, available from
- http://www.python.org/.
+ https://www.python.org/.
See Dependencies_ below for details.
2. Install the latest stable release from PyPi with pip_::
@@ -62,7 +62,7 @@
* And others as discovered.
.. _PEPs (Python Enhancement Proposals):
- http://www.python.org/peps/pep-0012.html
+ https://www.python.org/dev/peps/pep-0012
Dependencies
@@ -75,7 +75,7 @@
* Docutils 0.16 to 0.18 require Python 2.7 or 3.5+.
* Docutils 0.14 dropped Python 2.4, 2.5, 3.1 and 3.2 support.
-.. _Python: http://www.python.org/.
+.. _Python: https://www.python.org/.
Optional Dependencies
@@ -193,7 +193,7 @@
required version. The last installed version will be used in the
`shebang line`_ of the `front-end scripts`_.
- .. _shebang line: http://en.wikipedia.org/wiki/Shebang_%28Unix%29
+ .. _shebang line: https://en.wikipedia.org/wiki/Shebang_%28Unix%29
Windows
-------
@@ -368,7 +368,7 @@
.. _Docutils Testing: https://docutils.sourceforge.io/docs/dev/testing.html
.. _open a bug report:
- http://sourceforge.net/p/docutils/bugs/
+ https://sourceforge.net/p/docutils/bugs/
.. _send an email: mailto:doc...@li...
?subject=Test%20suite%20failure
.. _web interface: https://sourceforge.net/p/docutils/mailman/
Modified: trunk/docutils/RELEASE-NOTES.txt
===================================================================
--- trunk/docutils/RELEASE-NOTES.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/RELEASE-NOTES.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -422,7 +422,7 @@
- New HTML writer generating `HTML 5`_.
- .. _HTML 5: http://www.w3.org/TR/html5/
+ .. _HTML 5: https://www.w3.org/TR/html5/
* tools/
@@ -567,7 +567,7 @@
by Pygments_.
- "code" option of the "include" directive.
- .. _Pygments: http://pygments.org/
+ .. _Pygments: https://pygments.org/
- Fix [ 3402314 ] allow non-ASCII whitespace, punctuation
characters and "international" quotes around inline markup.
@@ -625,7 +625,7 @@
``math`` and ``math_block`` doctree elements.
- Orphaned "python" reader and "newlatex2e" writer moved to the sandbox.
- .. _BCP 47: http://www.rfc-editor.org/rfc/bcp/bcp47.txt
+ .. _BCP 47: https://www.rfc-editor.org/rfc/bcp/bcp47.txt
* reStructuredText:
Modified: trunk/docutils/THANKS.txt
===================================================================
--- trunk/docutils/THANKS.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/THANKS.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -162,8 +162,8 @@
Thank you!
-Special thanks to `SourceForge <http://sourceforge.net>`__ and the
-`Python Software Foundation <http://www.python.org/psf/>`__.
+Special thanks to `SourceForge <https://sourceforge.net>`__ and the
+`Python Software Foundation <https://www.python.org/psf/>`__.
Hopefully I haven't forgotten anyone or misspelled any names;
apologies (and please let me know!) if I have.
Modified: trunk/docutils/docs/dev/distributing.txt
===================================================================
--- trunk/docutils/docs/dev/distributing.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/distributing.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -46,7 +46,7 @@
.. _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
Modified: trunk/docutils/docs/dev/hacking.txt
===================================================================
--- trunk/docutils/docs/dev/hacking.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/hacking.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -32,7 +32,7 @@
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 @@
[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 @@
<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 @@
-------------------------
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 @@
<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 @@
$ 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 @@
</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>
Modified: trunk/docutils/docs/dev/policies.txt
===================================================================
--- trunk/docutils/docs/dev/policies.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/policies.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -98,8 +98,8 @@
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 @@
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 @@
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 @@
.. _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:
Modified: trunk/docutils/docs/dev/release.txt
===================================================================
--- trunk/docutils/docs/dev/release.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/release.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -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)
---------------------
Modified: trunk/docutils/docs/dev/repository.txt
===================================================================
--- trunk/docutils/docs/dev/repository.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/repository.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -45,7 +45,7 @@
.. _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 @@
----------
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 @@
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`_
Modified: trunk/docutils/docs/dev/rst/alternatives.txt
===================================================================
--- trunk/docutils/docs/dev/rst/alternatives.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/rst/alternatives.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -31,8 +31,7 @@
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 @@
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,7 +286,7 @@
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::
@@ -294,7 +293,7 @@
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"::
@@ -301,7 +300,7 @@
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 @@
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 @@
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 @@
.. |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 @@
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 @@
`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 @@
* 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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
| President, SuperDuper Corp.
| jd...@ex...
- __ 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 @@
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 @@
.. _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 @@
- 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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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
Modified: trunk/docutils/docs/dev/rst/problems.txt
===================================================================
--- trunk/docutils/docs/dev/rst/problems.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/rst/problems.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -847,8 +847,7 @@
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:
Modified: trunk/docutils/docs/dev/semantics.txt
===================================================================
--- trunk/docutils/docs/dev/semantics.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/semantics.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -101,13 +101,13 @@
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
..
Modified: trunk/docutils/docs/dev/todo.txt
===================================================================
--- trunk/docutils/docs/dev/todo.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/dev/todo.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -19,17 +19,7 @@
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 @@
* 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 @@
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 @@
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 @@
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 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 @@
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 @@
* 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 @@
- 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 @@
"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 @@
__ ../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 @@
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 @@
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:
Modified: trunk/docutils/docs/howto/i18n.txt
===================================================================
--- trunk/docutils/docs/howto/i18n.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/howto/i18n.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -35,7 +35,7 @@
.. [#] If anything in Docutils is insufficiently parameterized, it
should be considered a bug. Please report bugs to the Docutils
project bug tracker on SourceForge at
- http://sourceforge.net/p/docutils/bugs/
+ https://sourceforge.net/p/docutils/bugs/
.. _Docutils: https://docutils.sourceforge.io/
.. _Introduction to i18n:
@@ -65,8 +65,8 @@
.. [#] Subtags are separated from primary tags by underscores instead
of hyphens, to conform to Python naming rules.
-.. _language tags: http://www.w3.org/International/articles/language-tags/
-.. _BCP 47: http://www.rfc-editor.org/rfc/bcp/bcp47.txt
+.. _language tags: https://www.w3.org/International/articles/language-tags/
+.. _BCP 47: https://www.rfc-editor.org/rfc/bcp/bcp47.txt
.. _ISO 639: http://www.loc.gov/standards/iso639-2/php/English_list.php
.. _ISO 3166: http://www.iso.ch/iso/en/prods-services/iso3166ma/
02iso-3166-code-lists/index.html
@@ -175,4 +175,4 @@
language modules, feel free to submit them via the `SourceForge patch
tracker`__.
-__ http://sourceforge.net/p/docutils/patches/
+__ https://sourceforge.net/p/docutils/patches/
Modified: trunk/docutils/docs/ref/doctree.txt
===================================================================
--- trunk/docutils/docs/ref/doctree.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/doctree.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -94,7 +94,7 @@
.. _HTML: https://www.w3.org/TR/html52/
.. _DocBook: https://tdg.docbook.org/tdg/5.1/
-.. _XMLSpec: http://www.w3.org/XML/1998/06/xmlspec-report.htm
+.. _XMLSpec: https://www.w3.org/XML/1998/06/xmlspec-report.htm
Structural Elements
@@ -1658,7 +1658,7 @@
library.
.. _doctest module:
- http://www.python.org/doc/current/lib/module-doctest.html
+ https://docs.python.org/3/library/doctest.html
Details
@@ -4676,7 +4676,7 @@
`reference names`_ or from the auto_id_prefix_, prepending the id_prefix_
and potentially appending numbers for disambiguation.
- __ http://www.w3.org/TR/html401/types.html#type-name
+ __ https://www.w3.org/TR/html401/types.html#type-name
__ https://www.w3.org/TR/html50/dom.html#the-id-attribute
__ https://www.w3.org/TR/html-polyglot/#id-attribute
__ https://tex.stackexchange.com/questions/18311/what-are-the-valid-names-as-labels
Modified: trunk/docutils/docs/ref/rst/definitions.txt
===================================================================
--- trunk/docutils/docs/ref/rst/definitions.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/rst/definitions.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -84,7 +84,7 @@
unicode.xml__, which is maintained as part of the MathML 2
Recommentation XML source.
-__ http://www.w3.org/2003/entities/xml/
+__ https://www.w3.org/2003/entities/xml/
=================== =================================================
Entity Set File Description
Modified: trunk/docutils/docs/ref/rst/directives.txt
===================================================================
--- trunk/docutils/docs/ref/rst/directives.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/rst/directives.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -532,11 +532,11 @@
For inline code, use the `"code" role`_.
-__ http://pygments.org/docs/cmdline/#generating-styles
+__ https://pygments.org/docs/cmdline/#generating-styles
__ https://docutils.sourceforge.io/sandbox/stylesheets/
-.. _Pygments: http://pygments.org/
+.. _Pygments: https://pygments.org/
.. _syntax_highlight: ../../user/config.html#syntax-highlight
-.. _supported languages and markup formats: http://pygments.org/languages/
+.. _supported languages and markup formats: https://pygments.org/languages/
.. _"code" role: roles.html#code
@@ -1284,7 +1284,7 @@
I recommend you try |Python|_.
.. |Python| replace:: Python, *the* best language around
- .. _Python: http://www.python.org/
+ .. _Python: https://www.python.org/
.. _unicode:
@@ -1700,7 +1700,7 @@
hyphens ("-"), underscores ("_"), colons (":"), and periods
(".").
- -- http://www.w3.org/TR/html401/types.html#type-name
+ -- https://www.w3.org/TR/html401/types.html#type-name
- The `CSS1 spec`_ defines identifiers based on the "name" token
("flex" tokenizer notation below; "latin1" and "escape" 8-bit
@@ -1729,8 +1729,8 @@
__ https://www.w3.org/TR/CSS22/syndata.html
__ https://www.w3.org/TR/css-syntax-3/#typedef-ident-token
- .. _HTML 4.01 spec: http://www.w3.org/TR/html401/
- .. _CSS1 spec: http://www.w3.org/TR/REC-CSS1
+ .. _HTML 4.01 spec: https://www.w3.org/TR/html401/
+ .. _CSS1 spec: https://www.w3.org/TR/REC-CSS1
.. _role:
@@ -1941,7 +1941,7 @@
https://html.spec.whatwg.org/multipage/semantics.html#the-meta-element
.. _ODT file properties:
https://en.wikipedia.org/wiki/OpenDocument_technical_specification#Metadata
-.. _hyperref: http://ctan.org/pkg/hyperref
+.. _hyperref: https://ctan.org/pkg/hyperref
.. _bibliographic fields: restructuredtext.html#bibliographic-fields
Modified: trunk/docutils/docs/ref/rst/introduction.txt
===================================================================
--- trunk/docutils/docs/ref/rst/introduction.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/rst/introduction.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -30,8 +30,7 @@
https://docutils.sourceforge.io/rst.html.
.. _reStructuredText: https://docutils.sourceforge.io/rst.html
-.. _StructuredText:
- http://www.zope.org/DevHome/Members/jim/StructuredTextWiki/FrontPage
+.. _StructuredText: https://zopestructuredtext.readthedocs.org/
.. _Setext: https://docutils.sourceforge.io/mirror/setext.html
.. _Docutils: https://docutils.sourceforge.io/
.. _A ReStructuredText Primer: ../../user/rst/quickstart.html
@@ -144,7 +143,7 @@
David Goodger (go...@py...), 2001-04-20
-.. _Doc-SIG: http://www.python.org/sigs/doc-sig/
+.. _Doc-SIG: https://www.python.org/sigs/doc-sig/
History
@@ -179,7 +178,7 @@
an exercise in frustration, as the complexity of the module had become
overwhelming.
-In 2000, development on StructuredTextNG_ ("Next Generation") began at
+In 2000, development on StructuredTextNG ("Next Generation") began at
`Zope Corporation`_ (then Digital Creations). It seems to have many
improvements, but still suffers from many of the problems of classic
StructuredText.
@@ -218,9 +217,9 @@
- `Problems With StructuredText`__
- `reStructuredText: Revised Structured Text Specification`__
-__ http://mail.python.org/pipermail/doc-sig/2000-November/001239.html
-__ http://mail.python.org/pipermail/doc-sig/2000-November/001240.html
-__ http://mail.python.org/pipermail/doc-sig/2000-November/001241.html
+__ https://mail.python.org/pipermail/doc-sig/2000-November/001239.html
+__ https://mail.python.org/pipermail/doc-sig/2000-November/001240.html
+__ https://mail.python.org/pipermail/doc-sig/2000-November/001241.html
In March 2001 a flurry of activity on the Doc-SIG spurred me to
further revise and refine my specification, the result of which you
@@ -269,10 +268,10 @@
- `Python Extensions to the reStructuredText Markup
Specification`__
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001858.html
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001859.html
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001860.html
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001861.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001858.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001859.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001860.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001861.html
.. [#peps-1] First drafts of the PEPs:
@@ -284,25 +283,23 @@
https://docutils.sourceforge.io/docs/peps/, and official versions
can be found in the `master PEP repository`_.
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001855.html
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001856.html
- __ http://mail.python.org/pipermail/doc-sig/2001-June/001857.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001855.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001856.html
+ __ https://mail.python.org/pipermail/doc-sig/2001-June/001857.html
.. _Zope Corporation: http://www.zope.com
-.. _ZOPE: http://www.zope.org
+.. _ZOPE: https://www.zope.dev
.. _reStructuredText SourceForge project:
http://structuredtext.sourceforge.net/
.. _pythondoc: http://starship.python.net/crew/danilo/pythondoc/
-.. _StructuredTextNG:
- http://www.zope.org/DevHome/Members/jim/StructuredTextWiki/StructuredTextNG
.. _project history file: ../../../HISTORY.html
.. _PEP 287: ../../peps/pep-0287.html
.. _Docstring Processing System framework: ../../peps/pep-0256.html
.. _comp.lang.python: news:comp.lang.python
-.. _Python-dev: http://mail.python.org/pipermail/python-dev/
+.. _Python-dev: https://mail.python.org/pipermail/python-dev/
.. _Docstring Processing System: http://docstring.sourceforge.net/
-.. _master PEP repository: http://www.python.org/peps/
+.. _master PEP repository: https://www.python.org/dev/peps/
..
Modified: trunk/docutils/docs/ref/rst/mathematics.txt
===================================================================
--- trunk/docutils/docs/ref/rst/mathematics.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/rst/mathematics.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -97,7 +97,7 @@
.. _hyperlink references:
../ref/rst/restructuredtext.html#hyperlink-references
.. _Short Math Guide:
- http://mirrors.ctan.org/info/short-math-guide/short-math-guide.pdf
+ https://mirrors.ctan.org/info/short-math-guide/short-math-guide.pdf
.. _math_output:
https://docutils.sourceforge.io/docs/user/config.html#math-output
.. _LaTeX package:
@@ -295,7 +295,7 @@
\varTheta\ \varUpsilon\ \varXi\ \varOmega`
-__ http://mirrors.ctan.org/macros/latex/contrib/isomath/isomath.html#table-2
+__ https://mirrors.ctan.org/macros/latex/contrib/isomath/isomath.html#table-2
Letterlike symbols
Modified: trunk/docutils/docs/ref/rst/restructuredtext.txt
===================================================================
--- trunk/docutils/docs/ref/rst/restructuredtext.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/rst/restructuredtext.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -67,7 +67,7 @@
Paragraphs contain text and may contain inline markup:
*emphasis*, **strong emphasis**, `interpreted text`, ``inline
- literals``, standalone hyperlinks (http://www.python.org),
+ literals``, standalone hyperlinks (https://www.python.org),
external hyperlinks (Python_), internal cross-references
(example_), footnote references ([1]_), citation references
([CIT2002]_), substitution references (|example|), and _`inline
@@ -187,7 +187,7 @@
- `Hyperlink targets`_::
- .. _Python: http://www.python.org
+ .. _Python: https://www.python.org
.. _example:
@@ -413,7 +413,7 @@
Want to learn about `my favorite programming language`_?
- .. _my favorite programming language: http://www.python.org
+ .. _my favorite programming language: https://www.python.org
Simple reference names may also optionally use backquotes.
@@ -1901,7 +1901,7 @@
.. _Python DOC-SIG mailing list archive:
.. _archive:
- .. _Doc-SIG: http://mail.python.org/pipermail/doc-sig/
+ .. _Doc-SIG: https://mail.python.org/pipermail/doc-sig/
An inline form of internal hyperlink target is available; see
`Inline Internal Targets`_.
@@ -1926,12 +1926,12 @@
`Write to me`_ with your questions.
- .. _Python: http://www.python.org
+ .. _Python: https://www.python.org
.. _Write to me: jd...@ex...
After processing into HTML, the hyperlinks might be expressed as::
- See the <a href="http://www.python.org">Python</a> home page
+ See the <a href="https://www.python.org">Python</a> home page
for info.
<a href="mailto:jd...@ex...">Write to me</a> with your
@@ -2047,12 +2047,12 @@
Anonymous targets begin with ".. __:"; no reference name is required
or allowed::
- .. __: http://www.python.org
+ .. __: https://www.python.org
As a convenient alternative, anonymous targets may begin with "__"
only::
- __ http://www.python.org
+ __ https://www.python.org
The reference name of the reference is not used to match the reference
to its target. Instead, the order of anonymous hyperlink references
@@ -2550,10 +2550,10 @@
Docutils 0.13 uses `Unicode version 5.2.0`_.
.. _Unicode categories:
- http://www.unicode.org/Public/5.1.0/ucd/UCD.html#General_Category_Values
-.. _Unicode version 5.2.0: http://www.unicode.org/Public/5.2.0/
+ https://www.unicode.org/Public/5.1.0/ucd/UCD.html#General_Category_Values
+.. _Unicode version 5.2.0: https://www.unicode.org/Public/5.2.0/
.. _quotation marks in international usage:
- http://en.wikipedia.org/wiki/Quotation_mark,_non-English_usage
+ https://en.wikipedia.org/wiki/Quotation_mark,_non-English_usage
The inline markup recognition rules were devised to allow 90% of non-markup
uses of "*", "`", "_", and "|" without escaping. For example, none of the
@@ -2818,7 +2818,7 @@
Docutils 0.11) a hyperlink reference within angle brackets ("<...>")
as follows::
- See the `Python home page <http://www.python.org>`_ for info.
+ See the `Python home page <https://www.python.org>`_ for info.
This `link <Python home page_>`_ is an alias to the link above.
@@ -2828,7 +2828,7 @@
This link_ is an alias to the link above.
- .. _Python home page: http://www.python.org
+ .. _Python home page: https://www.python.org
.. _link: `Python home page`_
The bracketed URI must be preceded by whitespace and be the last text
@@ -2840,8 +2840,8 @@
anonymous, and the target cannot be referred to again. These are
"one-off" hyperlinks. For example::
- `RFC 2396 <http://www.rfc-editor.org/rfc/rfc2396.txt>`__ and `RFC
- 2732 <http://www.rfc-editor.org/rfc/rfc2732.txt>`__ together
+ `RFC 2396 <https://www.rfc-editor.org/rfc/rfc2396.txt>`__ and `RFC
+ 2732 <https://www.rfc-editor.org/rfc/rfc2732.txt>`__ together
define the syntax of URIs.
Equivalent to::
@@ -2848,8 +2848,8 @@
`RFC 2396`__ and `RFC 2732`__ together define the syntax of URIs.
- __ http://www.rfc-editor.org/rfc/rfc2396.txt
- __ http://www.rfc-editor.org/rfc/rfc2732.txt
+ __ https://www.rfc-editor.org/rfc/rfc2396.txt
+ __ https://www.rfc-editor.org/rfc/rfc2732.txt
`Standalone hyperlinks`_ are treated as URIs, even if they end with an
underscore like in the example of a Python function documentation::
@@ -3014,11 +3014,11 @@
block is treated as a general external hyperlink with the URI itself
as the link's text. For example::
- See http://www.python.org for info.
+ See https://www.python.org for info.
would be marked up in HTML as::
- See <a href="http://www.python.org">http://www.python.org</a> for
+ See <a href="https://www.python.org">https://www.python.org</a> for
info.
Two forms of URI are recognized:
@@ -3039,7 +3039,7 @@
use slashes to separate hierarchical components of the path.
Examples are web pages and FTP sites::
- http://www.python.org
+ https://www.python.org
ftp://ftp.python.org/pub/python
@@ -3111,9 +3111,9 @@
specific documentation in the `user doc`__ for details.
.. _length units in CSS2:
- http://www.w3.org/TR/CSS2/syndata.html#length-units
+ https://www.w3.org/TR/CSS2/syndata.html#length-units
.. _length units in CSS3:
- http://www.w3.org/TR/css-values-3/#absolute-lengths
+ https://www.w3.org/TR/css-values-3/#absolute-lengths
.. _How to configure the size of a pixel:
../../user/latex.html#size-of-a-pixel
__ ../../user/
@@ -3143,26 +3143,26 @@
.. _transforms:
https://docutils.sourceforge.io/docutils/transforms/
.. _Grouch: http://www.mems-exchange.org/software/grouch/
-.. _RFC822: http://www.rfc-editor.org/rfc/rfc822.txt
+.. _RFC822: https://www.rfc-editor.org/rfc/rfc822.txt
.. _DocTitle transform:
.. _DocInfo transform:
https://docutils.sourceforge.io/docutils/transforms/frontmatter.py
.. _getopt.py:
- http://www.python.org/doc/current/lib/module-getopt.html
+ https://docs.python.org/3/library/getopt.html
.. _GNU libc getopt_long():
- http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html
+ https://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html
.. _doctest module:
- http://www.python.org/doc/current/lib/module-doctest.html
+ https://docs.python.org/3/library/doctest.html
.. _Emacs table mode: http://table.sourceforge.net/
.. _Official IANA Registry of URI Schemes:
http://www.iana.org/assignments/uri-schemes
.. _Retired Index of WWW Addressing Schemes:
- http://www.w3.org/Addressing/schemes.html
-.. _World Wide Web Consortium: http://www.w3.org/
+ https://www.w3.org/Addressing/schemes.html
+.. _World Wide Web Consortium: https://www.w3.org/
.. _HTML Techniques for Web Content Accessibility Guidelines:
- http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text
-.. _RFC2396: http://www.rfc-editor.org/rfc/rfc2396.txt
-.. _RFC2732: http://www.rfc-editor.org/rfc/rfc2732.txt
+ https://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text
+.. _RFC2396: https://www.rfc-editor.org/rfc/rfc2396.txt
+.. _RFC2732: https://www.rfc-editor.org/rfc/rfc2732.txt
.. _Zope: http://www.zope.com/
.. _PEP 258: ../../peps/pep-0258.html
.. _writers: ../../peps/pep-0258.html#writers
Modified: trunk/docutils/docs/ref/rst/roles.txt
===================================================================
--- trunk/docutils/docs/ref/rst/roles.txt 2022-01-21 09:58:00 UTC (rev 8958)
+++ trunk/docutils/docs/ref/rst/roles.txt 2022-01-21 13:45:42 UTC (rev 8959)
@@ -137,8 +137,8 @@
See `supported languages and markup formats`_ for recognized values.
.. _code directive: directives.html#code
-.. _Pygments: http://pygments.org/
-.. _supported languages and markup formats: http://pygments.org/languages/
+.. _Pygments: https://pygments.org/
+.. _supported languages and markup formats: https://pygments.org/languages/
``:math:``
@@ -185,7 +185,7 @@
See `PEP 287`__ for more information about reStructuredText.
- __ http://www.python.org/peps/pep-0287.html
+ __ https://www.python.org/dev/peps/pep-0287
``:rfc-reference:``
@@ -207,7 +207,7 @@
See `RFC 2822`__ for information about email headers.
- __ http://tools.ietf.org/html/rfc2822.html
+ __ https://tools.ietf.org/html/rfc2822.html
.. [#] You can link to a specific section by saying
``:rfc:`number#anchor```. (New in Docutils 0.15.)
Modified: trunk/docutils/docs/user/config.txt
=================...
[truncated message content] |
