diff options
| 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 | |
| parent | b59783bd350f805751f03efb1793a1366929bfb8 (diff) | |
| download | docutils-35605d7eeed80fd02678f709e85cfe2341edca16.tar.gz | |
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
Diffstat (limited to 'docutils/docs')
29 files changed, 301 insertions, 324 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: diff --git a/docutils/docs/howto/i18n.txt b/docutils/docs/howto/i18n.txt index 6027b61f8..85f99c95f 100644 --- a/docutils/docs/howto/i18n.txt +++ b/docutils/docs/howto/i18n.txt @@ -35,7 +35,7 @@ support via a module in the PYTHONPATH root (e.g. the working directory). .. [#] 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 @@ is "en" for English. Examples of module names include ``en.py``, .. [#] 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 @@ If you do not have repository write access and want to contribute your language modules, feel free to submit them via the `SourceForge patch tracker`__. -__ http://sourceforge.net/p/docutils/patches/ +__ https://sourceforge.net/p/docutils/patches/ diff --git a/docutils/docs/ref/doctree.txt b/docutils/docs/ref/doctree.txt index 4d5fec1e5..ed25ca58d 100644 --- a/docutils/docs/ref/doctree.txt +++ b/docutils/docs/ref/doctree.txt @@ -94,7 +94,7 @@ occur at the same level. .. _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 @@ testing environment via the `doctest module`_ in the Python standard 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 @@ _`idrefs.type` `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 diff --git a/docutils/docs/ref/rst/definitions.txt b/docutils/docs/ref/rst/definitions.txt index 484bffae2..86f660a1d 100644 --- a/docutils/docs/ref/rst/definitions.txt +++ b/docutils/docs/ref/rst/definitions.txt @@ -84,7 +84,7 @@ the ``tools/dev/unicode2rstsubs.py`` program from the input file 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 diff --git a/docutils/docs/ref/rst/directives.txt b/docutils/docs/ref/rst/directives.txt index c6e89a963..7a5aae092 100644 --- a/docutils/docs/ref/rst/directives.txt +++ b/docutils/docs/ref/rst/directives.txt @@ -532,11 +532,11 @@ when Pygments_ is not installed or the language is not in the 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 @@ the "replace" directive:: 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 @@ For example ``"Rot.Gelb&Grün:+2008"`` becomes ``"rot-gelb-grun-2008"`` and 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 @@ For example ``"Rot.Gelb&Grün:+2008"`` becomes ``"rot-gelb-grun-2008"`` and __ 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 @@ HTML equivalent:: 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 diff --git a/docutils/docs/ref/rst/introduction.txt b/docutils/docs/ref/rst/introduction.txt index aedd647e3..e09df45df 100644 --- a/docutils/docs/ref/rst/introduction.txt +++ b/docutils/docs/ref/rst/introduction.txt @@ -30,8 +30,7 @@ ReStructuredText's web page is 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 @@ Author's note: David Goodger (goodger@python.org), 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 @@ Implementing the new syntax extensions from version 1.23 proved to be 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 @@ parts: - `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 @@ followed. - `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 @@ followed. 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/ .. diff --git a/docutils/docs/ref/rst/mathematics.txt b/docutils/docs/ref/rst/mathematics.txt index 52fd88e07..c6db8a9f5 100644 --- a/docutils/docs/ref/rst/mathematics.txt +++ b/docutils/docs/ref/rst/mathematics.txt @@ -97,7 +97,7 @@ The result is: .. _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 @@ letter name with ``var`` like ``\varPhi``: \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 diff --git a/docutils/docs/ref/rst/restructuredtext.txt b/docutils/docs/ref/rst/restructuredtext.txt index f1edf9979..e28a59466 100644 --- a/docutils/docs/ref/rst/restructuredtext.txt +++ b/docutils/docs/ref/rst/restructuredtext.txt @@ -67,7 +67,7 @@ Here are examples of `body elements`_: 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 @@ Here are examples of `body elements`_: - `Hyperlink targets`_:: - .. _Python: http://www.python.org + .. _Python: https://www.python.org .. _example: @@ -413,7 +413,7 @@ and treating the backquoted text as a reference name:: 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 @@ indirect. .. _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 @@ indirect. `Write to me`_ with your questions. - .. _Python: http://www.python.org + .. _Python: https://www.python.org .. _Write to me: jdoe@example.com 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:jdoe@example.com">Write to me</a> with your @@ -2047,12 +2047,12 @@ instead of one:: 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 @@ inline markup: 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 @@ A hyperlink reference may directly embed a target URI or (since 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 is exactly equivalent to:: 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,16 +2840,16 @@ With two trailing underscores, the reference and target are both 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:: `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 @@ A URI (absolute URI [#URI]_ or standalone email address) within a text 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 @@ Two forms of URI are recognized: 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 @@ default (e.g. "px" with HTML, "pt" with `latex2e`). See the writer 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 @@ Markup errors are handled according to the specification in `PEP .. _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 diff --git a/docutils/docs/ref/rst/roles.txt b/docutils/docs/ref/rst/roles.txt index 221bbc6a6..bc8a8a102 100644 --- a/docutils/docs/ref/rst/roles.txt +++ b/docutils/docs/ref/rst/roles.txt @@ -137,8 +137,8 @@ In addition to "class_", the following option is recognized: 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 @@ This is equivalent to:: 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 @@ This is equivalent to:: 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.) diff --git a/docutils/docs/user/config.txt b/docutils/docs/user/config.txt index e971e8dfa..fa104e16a 100644 --- a/docutils/docs/user/config.txt +++ b/docutils/docs/user/config.txt @@ -193,9 +193,9 @@ file. Some knowledge of Python_ is assumed for some attributes. .. _ConfigParser.py: - http://www.python.org/doc/current/lib/module-ConfigParser.html -.. _Python: http://www.python.org/ -.. _RFC 822: http://www.rfc-editor.org/rfc/rfc822.txt + https://docs.python.org/3/library/configparser.html +.. _Python: https://www.python.org/ +.. _RFC 822: https://www.rfc-editor.org/rfc/rfc822.txt .. _front-end tool: .. _Docutils application: tools.html @@ -696,7 +696,7 @@ pep_base_url ~~~~~~~~~~~~ Base URL for PEP references. -Default: "http://www.python.org/peps/". +Default: "https://www.python.org/dev/peps/". Option: ``--pep-base-url``. pep_file_url_template @@ -749,7 +749,7 @@ New in Docutils 0.10. .. _SmartQuotes: smartquotes.html __ smartquotes.html#localization .. _quote characters: - http://en.wikipedia.org/wiki/Non-English_usage_of_quotation_marks + https://en.wikipedia.org/wiki/Non-English_usage_of_quotation_marks smartquotes_locales @@ -795,10 +795,10 @@ Default: "long". Option: ``--syntax-highlight``. New in Docutils 0.9. -.. _Pygments: http://pygments.org/ +.. _Pygments: https://pygments.org/ .. _code: ../ref/rst/directives.html#code .. _Pygments-generated stylesheets: - http://pygments.org/docs/cmdline/#generating-styles + https://pygments.org/docs/cmdline/#generating-styles tab_width ~~~~~~~~~ @@ -1164,7 +1164,7 @@ New in Docutils 0.8. .. _math directive: ../ref/rst/directives.html#math .. _MathJax: http://www.mathjax.org/ .. _MathPlayer: http://www.dessci.com/en/products/mathplayer/ -.. _MathML: http://www.w3.org/TR/MathML/ +.. _MathML: https://www.w3.org/TR/MathML/ .. _blahtexml: http://gva.noekeon.org/blahtexml/ .. _LaTeXML: http://dlmf.nist.gov/LaTeXML/ .. _TtM: http://hutchinson.belmont.ma.us/tth/mml/ @@ -1319,7 +1319,7 @@ Writer Specific Defaults enabled (True) .. _HTML4/CSS1 Writer: html.html#html4css1 -.. _XHTML 1 Transitional: http://www.w3.org/TR/xhtml1/ +.. _XHTML 1 Transitional: https://www.w3.org/TR/xhtml1/ field_name_limit @@ -2275,8 +2275,8 @@ Default: stdin (None). No command-line options. -------------------------------------------------------------------------- -.. _language tag: http://www.w3.org/International/articles/language-tags/ -.. _BCP 47: http://www.rfc-editor.org/rfc/bcp/bcp47.txt +.. _language tag: 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 diff --git a/docutils/docs/user/emacs.txt b/docutils/docs/user/emacs.txt index 51878890d..84a9734ea 100644 --- a/docutils/docs/user/emacs.txt +++ b/docutils/docs/user/emacs.txt @@ -89,7 +89,7 @@ If you decided to install locally please follow these steps. #. Download ``rst.el`` Download the most recent published version of ``rst.el`` from - http://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils/tools/editors/emacs/rst.el + https://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils/tools/editors/emacs/rst.el #. Put ``rst.el`` to a directory in ``load-path`` @@ -939,7 +939,7 @@ Stefan Merten. Most of the code has been modified, enhanced and extended by Stefan Merten who also is the current maintainer of ``rst.el``. -.. _Emacs: http://www.gnu.org/software/emacs/emacs.html +.. _Emacs: https://www.gnu.org/software/emacs/emacs.html .. _reStructuredText: https://docutils.sourceforge.io/rst.html .. _Docutils: https://docutils.sourceforge.io/ diff --git a/docutils/docs/user/html.txt b/docutils/docs/user/html.txt index 0a37adb5a..76375cc3e 100644 --- a/docutils/docs/user/html.txt +++ b/docutils/docs/user/html.txt @@ -153,32 +153,32 @@ References _`HTML5` `HTML5, A vocabulary and associated APIs for HTML and XHTML`, W3C Recommendation, 28 October 2014. - http://www.w3.org/TR/html5/ + https://www.w3.org/TR/2014/REC-html5-20141028/ _`XHTML 1.1` `XHTML™ 1.1 - Module-based XHTML - Second Edition`, W3C Recommendation, 23 November 2010. - http://www.w3.org/TR/xhtml11/ + https://www.w3.org/TR/xhtml11/ _`XHTML 1 Transitional` `Transitional version`_ of: `XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)`, `A Reformulation of HTML 4 in XML 1.0`, W3C Recommendation, 26 January 2000, revised 1 August 2002. - http://www.w3.org/TR/xhtml1/ + https://www.w3.org/TR/xhtml1/ _`XHTML Basic` `XHTML™ Basic 1.1 - Second Edition`, W3C Recommendation, 23 November 2010. - http://www.w3.org/TR/xhtml-basic/ + https://www.w3.org/TR/xhtml-basic/ .. _transitional version: - http://www.w3.org/TR/xhtml1/#a_dtd_XHTML-1.0-Transitional + https://www.w3.org/TR/xhtml1/#a_dtd_XHTML-1.0-Transitional _`HTML 4.01 Transitional` Transitional version of: `HTML 4.01 Specification`, W3C Recommendation 24 December 1999. - http://www.w3.org/TR/html4/ + https://www.w3.org/TR/html4/ .. _`CSS 1`: @@ -188,23 +188,23 @@ _`CSS Level 1`: _`CSS 2.1` `Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification`, W3C Recommendation 07 June 2011. - http://www.w3.org/TR/CSS21/ + https://www.w3.org/TR/CSS21/ _`CSS 3`: CSS Level 3 builds on CSS Level 2 module by module, using the CSS2.1 specification as its core. - Specifications: http://www.w3.org/Style/CSS/specs.en.html + Specifications: https://www.w3.org/Style/CSS/specs.en.html Validator: http://jigsaw.w3.org/css-validator/ .. other references ---------------- -.. _HTML Compatibility Guidelines: http://www.w3.org/TR/xhtml1/#guidelines -.. _CSS: http://www.w3.org/TR/CSS/ -.. _CSS1 specification: http://www.w3.org/TR/2008/REC-CSS1-20080411/ -.. _polyglot HTML: http://www.w3.org/TR/html-polyglot/ +.. _HTML Compatibility Guidelines: https://www.w3.org/TR/xhtml1/#guidelines +.. _CSS: https://www.w3.org/TR/CSS/ +.. _CSS1 specification: https://www.w3.org/TR/2008/REC-CSS1-20080411/ +.. _polyglot HTML: https://www.w3.org/TR/html-polyglot/ .. Beware. This specification is no longer in active maintenance and the HTML Working Group does not intend to maintain it further. diff --git a/docutils/docs/user/latex.txt b/docutils/docs/user/latex.txt index 496d148a2..e6790a8b3 100644 --- a/docutils/docs/user/latex.txt +++ b/docutils/docs/user/latex.txt @@ -324,7 +324,7 @@ Stylesheet Repository There is a `repository of user-contributed style sheets`_ in the Docutils Sandbox_. -.. _clsguide: http://mirrors.ctan.org/macros/latex/base/clsguide.pdf +.. _clsguide: https://mirrors.ctan.org/macros/latex/base/clsguide.pdf .. _stylesheet: config.html#stylesheet-latex-writers .. _embed-stylesheet: config.html#embed-stylesheet-latex-writers .. _repository of user-contributed style sheets: @@ -355,7 +355,7 @@ Example: \usepackage[scaled=.92]{helvet} % Helvetica .. _latex-preamble: config.html#latex-preamble -.. _PDF standard fonts: http://en.wikipedia.org/wiki/PDF#Standard_Type_1_Fonts +.. _PDF standard fonts: https://en.wikipedia.org/wiki/PDF#Standard_Type_1_Fonts .. _Linux Libertine: http://www.linuxlibertine.org @@ -470,8 +470,8 @@ Example 3: ``\marginpar`` fails in some places or with some content. See also the environ_ and marginnote_ packages. -.. _environ: http://ctan.org/pkg/environ -.. _marginnote: http://ctan.org/pkg/marginnote +.. _environ: https://ctan.org/pkg/environ +.. _marginnote: https://ctan.org/pkg/marginnote .. _custom role: @@ -587,8 +587,8 @@ Popular document classes: Option: documentclass_ -.. _KOMA-script: http://ctan.org/pkg/koma-script -.. _memoir: http://ctan.org/pkg/memoir +.. _KOMA-script: https://ctan.org/pkg/koma-script +.. _memoir: https://ctan.org/pkg/memoir .. _documentclass: config.html#documentclass @@ -669,7 +669,7 @@ Example: The `KOMA-script`_ classes provide a similar environment under the name `labeling`. -.. _enumitem: http://ctan.org/pkg/enumitem +.. _enumitem: https://ctan.org/pkg/enumitem __ ../ref/rst/restructuredtext.html#field-lists @@ -691,8 +691,8 @@ Example \usepackage{caption} \captionsetup{justification=raggedleft,singlelinecheck=false} -.. _caption: http://ctan.org/pkg/caption -.. _chngcntr: http://ctan.org/pkg/chngcntr +.. _caption: https://ctan.org/pkg/caption +.. _chngcntr: https://ctan.org/pkg/chngcntr __ http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos @@ -730,8 +730,8 @@ Example 2: \floatplacement{figure}{tb} .. _figures: ../ref/rst/directives.html#figure -.. _float: http://ctan.org/pkg/float -.. _float.pdf: http://mirrors.ctan.org/macros/latex/contrib/float/float.pdf +.. _float: https://ctan.org/pkg/float +.. _float.pdf: https://mirrors.ctan.org/macros/latex/contrib/float/float.pdf .. _font setup: @@ -755,7 +755,7 @@ XeTeX/LuaTeX can use system fonts and provides access to the full feature set of modern OpenType_ fonts. -.. _OpenType: http://en.wikipedia.org/wiki/OpenType +.. _OpenType: https://en.wikipedia.org/wiki/OpenType The default font setup is done in the latex-preamble_: @@ -830,7 +830,7 @@ XeTeX/LuaTeX \setsansfont{DejaVu Sans} \setmonofont[HyphenChar=None]{DejaVu Sans Mono} -.. _fontspec: http://ctan.org/pkg/fontspec +.. _fontspec: https://ctan.org/pkg/fontspec .. _fontmatrix: http://fontmatrix.net/ .. _DejaVu: http://dejavu-fonts.org/ .. _documentoptions: config.html#documentoptions @@ -961,17 +961,17 @@ d) PSNFSS_ Postscript fonts .. _LaTeX Font Catalogue: http://www.tug.dk/FontCatalogue/ -.. _Latin Modern: http://ctan.org/pkg/lm -.. _CM-Super: http://ctan.org/pkg/cm-super -.. _bera: http://ctan.org/pkg/bera +.. _Latin Modern: https://ctan.org/pkg/lm +.. _CM-Super: https://ctan.org/pkg/cm-super +.. _bera: https://ctan.org/pkg/bera .. _TeX Gyre: http://www.gust.org.pl/projects/e-foundry/tex-gyre -.. _PSNFSS: http://ctan.org/pkg/psnfss +.. _PSNFSS: https://ctan.org/pkg/psnfss .. _Using common PostScript fonts with LaTeX: - http://mirrors.ctan.org/macros/latex/required/psnfss/psnfss2e.pdf + https://mirrors.ctan.org/macros/latex/required/psnfss/psnfss2e.pdf .. _TeX Live: http://tug.org/texlive/ -.. _txfonts: http://ctan.org/pkg/txfonts +.. _txfonts: https://ctan.org/pkg/txfonts .. _PDF Standard Font: - http://en.wikipedia.org/wiki/PDF#Standard_Type_1_Fonts + https://en.wikipedia.org/wiki/PDF#Standard_Type_1_Fonts .. _testflow: http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/testflow.html .. _Good Libre Fonts: http://typophile.com/node/18207 @@ -1014,9 +1014,9 @@ Example 2: --font-encoding=LGR,T1 --stylesheet=lmodern -.. _encguide: http://mirrors.ctan.org/macros/latex/base/encguide.pdf +.. _encguide: https://mirrors.ctan.org/macros/latex/base/encguide.pdf .. _font-encoding: config.html#font-encoding -.. _fontenc: http://ctan.org/pkg/fontenc +.. _fontenc: https://ctan.org/pkg/fontenc font size @@ -1026,7 +1026,7 @@ Add font size in points to the document options, e.g. ``--documentoptions=12``, use e.g. the document classes provided by extsizes_ for values other than [10,11,12]. -.. _extsizes: http://ctan.org/pkg/extsizes +.. _extsizes: https://ctan.org/pkg/extsizes footnotes @@ -1089,8 +1089,8 @@ Example 3: \hangpara{\parindent}{1}#4% } -.. _footmisc: http://ctan.org/pkg/footmisc -.. _hanging: http://ctan.org/pkg/hanging +.. _footmisc: https://ctan.org/pkg/footmisc +.. _hanging: https://ctan.org/pkg/hanging hyphenation @@ -1161,7 +1161,7 @@ Option: \usepackage{nohyperref,url} \urlstyle{same} -.. _hyperref: http://ctan.org/pkg/hyperref +.. _hyperref: https://ctan.org/pkg/hyperref line blocks ----------- @@ -1253,7 +1253,7 @@ Example: __ ../ref/rst/restructuredtext.html#literal-blocks .. _literal-block-env: config.html#literal-block-env .. _listings.pdf: - http://mirrors.ctan.org/macros/latex/contrib/listings/listings.pdf + https://mirrors.ctan.org/macros/latex/contrib/listings/listings.pdf lists @@ -1380,12 +1380,12 @@ Example 2: \geometry{hmargin={3cm,0.8in},height=8in} \geometry{height=10in}. -.. _typearea: http://ctan.org/pkg/typearea -.. _geometry: http://ctan.org/pkg/geometry +.. _typearea: https://ctan.org/pkg/typearea +.. _geometry: https://ctan.org/pkg/geometry .. _KOMA-Script Guide: - http://mirrors.ctan.org/macros/latex/contrib/koma-script/doc/scrguien.pdf + https://mirrors.ctan.org/macros/latex/contrib/koma-script/doc/scrguien.pdf .. _geometry manual: - http://mirrors.ctan.org/macros/latex/contrib/geometry/geometry.pdf + https://mirrors.ctan.org/macros/latex/contrib/geometry/geometry.pdf page headers and footers @@ -1423,9 +1423,9 @@ Example: See the `chappg documentation`_ for details. -.. _chappg: http://ctan.org/pkg/chappg +.. _chappg: https://ctan.org/pkg/chappg .. _chappg documentation: - http://mirrors.ctan.org/macros/latex/contrib/chappg/chappg.pdf + https://mirrors.ctan.org/macros/latex/contrib/chappg/chappg.pdf paper size @@ -1609,10 +1609,10 @@ Example: .. [#] The `CSS length unit ``px```_ defaults to 1/96 inch. -__ http://tex.stackexchange.com/questions/41370/ +__ https://tex.stackexchange.com/questions/41370/ what-are-the-possible-dimensions-sizes-units-latex-understands -.. _CSS length unit ``px``: http://www.w3.org/TR/css-values-3/#px -.. _reference pixel: http://www.w3.org/TR/css-values-3/#reference-pixel +.. _CSS length unit ``px``: https://www.w3.org/TR/css-values-3/#px +.. _reference pixel: https://www.w3.org/TR/css-values-3/#reference-pixel table style ------------ @@ -1697,9 +1697,9 @@ With use-latex-toc (default since release 0.6): .. _use-latex-toc: config.html#use-latex-toc .. _contents directive: ../ref/rst/directives.html#contents -.. _minitoc: http://ctan.org/pkg/minitoc +.. _minitoc: https://ctan.org/pkg/minitoc .. _minitoc documentation: - http://mirrors.ctan.org/macros/latex/contrib/minitoc/minitoc.pdf + https://mirrors.ctan.org/macros/latex/contrib/minitoc/minitoc.pdf title reference role @@ -1794,8 +1794,8 @@ Note: .. _LaTeX Unicode: http://www.unruh.de/DniQ/latex/unicode/ .. _output-encoding: config.html#output-encoding -.. _inputenc: http://ctan.org/pkg/inputenc -.. _ucs: http://ctan.org/pkg/unicode +.. _inputenc: https://ctan.org/pkg/inputenc +.. _ucs: https://ctan.org/pkg/unicode topic element @@ -1915,7 +1915,7 @@ Right: See also the `Link text doesn’t break at end line`_ LaTeX FAQ entry. -.. _breakurl: http://ctan.org/pkg/breakurl +.. _breakurl: https://ctan.org/pkg/breakurl .. _Link text doesn’t break at end line: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks @@ -1968,8 +1968,8 @@ can help. __ ../ref/rst/directives.html#images .. _grfguide.pdf: - http://mirrors.ctan.org/macros/latex/required/graphics/grfguide.pdf -.. _grffile: http://ctan.org/pkg/grffile + https://mirrors.ctan.org/macros/latex/required/graphics/grfguide.pdf +.. _grffile: https://ctan.org/pkg/grffile .. _graphicx-option: config.html#graphicx-option @@ -1985,7 +1985,7 @@ The CSS specification suggests: pixel on a device with a pixel density of 96 DPI and a distance from the reader of an arm's length. - -- http://www.w3.org/TR/CSS2/syndata.html#length-units + -- https://www.w3.org/TR/CSS2/syndata.html#length-units This is why pixmap images without size specification or objects with a size specified in ``px`` tend to come too large in the PDF. @@ -2056,9 +2056,9 @@ With "traditional" TeX engines (e.g. pdflatex_): Unfortunately, this defines only a subset of the characters (see pmboxdraw.pdf_ for a list). -.. _pmboxdraw: http://ctan.org/pkg/pmboxdraw +.. _pmboxdraw: https://ctan.org/pkg/pmboxdraw .. _pmboxdraw.pdf: - http://mirrors.ctan.org/macros/latex/contrib/pmboxdraw/pmboxdraw.pdf + https://mirrors.ctan.org/macros/latex/contrib/pmboxdraw/pmboxdraw.pdf Bugs and open issues -------------------- @@ -2120,7 +2120,7 @@ Figures * Wrapping text around figures is currently not supported. (Requires the `wrapfig`_ package.) -.. _wrapfig: http://ctan.org/pkg/wrapfig +.. _wrapfig: https://ctan.org/pkg/wrapfig Miscellaneous diff --git a/docutils/docs/user/links.txt b/docutils/docs/user/links.txt index f43353e7c..6c30936e5 100644 --- a/docutils/docs/user/links.txt +++ b/docutils/docs/user/links.txt @@ -20,7 +20,7 @@ something to publish, you can get write access, too! The most current version of this link list can always be found at https://docutils.sourceforge.io/docs/user/links.html. -.. _Docutils: http://docutils.sourceforge.io/ +.. _Docutils: https://docutils.sourceforge.io/ .. _Docutils Sandbox: https://docutils.sourceforge.io/sandbox/README.html @@ -31,27 +31,27 @@ Advanced text editors with reStructuredText support, IDEs, and docutils GUIs: * Emacs `rst mode <https://docutils.sourceforge.io/tools/editors/emacs>`__. -* `Vim <http://www.vim.org/index.php>`__: +* `Vim <https://www.vim.org/index.php>`__: - `reStructuredText syntax highlighting mode - <http://www.vim.org/scripts/script.php?script_id=973>`__, + <https://www.vim.org/scripts/script.php?script_id=973>`__, - - `VST <http://www.vim.org/scripts/script.php?script_id=1334>`__ (Vim + - `VST <https://www.vim.org/scripts/script.php?script_id=1334>`__ (Vim reStructuredText) plugin for Vim7 with folding. - - `VOoM <http://www.vim.org/scripts/script.php?script_id=2657>`__ + - `VOoM <https://www.vim.org/scripts/script.php?script_id=2657>`__ plugin for Vim that emulates two-pane outliner with support for reStructuredText (since version 4.0b2). - `Riv: Take notes in rst <https://github.com/Rykka/riv.vim>`__ Vim plugin to take notes in reStructured text. -* `JED <http://www.jedsoft.org/jed/>`__ programmers editor with - `rst mode <https://jedmodes.sourceforge.io/mode/rst/>`__ +* `JED <https://www.jedsoft.org/jed/>`__ programmers editor with + `rst mode <httpss://jedmodes.sourceforge.io/mode/rst/>`__ * `reStructuredText editor plug-in for Eclipse`__ - __ http://http://resteditor.sourceforge.net/ + __ http://resteditor.sourceforge.net/ * Gnome's gedit offers syntax highlighting and a reST preview pane. @@ -74,9 +74,9 @@ Advanced text editors with reStructuredText support, IDEs, and docutils GUIs: for literal programming, as a filing cabinet holding any kind of data and as `document editor`__ with outlines containing reStructuredText markup. - .. _Leo: http://leoeditor.com/ - .. _outliner: http://en.wikipedia.org/wiki/Outliner - __ http://leoeditor.com/tutorial-rst3.html + .. _Leo: https://leoeditor.com/ + .. _outliner: https://en.wikipedia.org/wiki/Outliner + __ https://leoeditor.com/tutorial-rst3.html * `NoTex <https://notex.ch>`_ is a browser-based reStructuredText editor with syntax highlighting and PDF/HTML export functionality using Sphinx. @@ -122,7 +122,7 @@ PDF * RinohType_ is a pure Python PDF Writer based on a document template and a style sheet (beta). - .. _RinohType: http://pypi.python.org/pypi/RinohType/0.2.1 + .. _RinohType: https://pypi.python.org/pypi/RinohType website generators and HTML variants ```````````````````````````````````` @@ -140,26 +140,25 @@ website generators and HTML variants * The Nikola_ static site generator, uses reStructuredText by default. - .. _nikola: http://getnikola.com/ + .. _nikola: https://getnikola.com/ * Pelican_ is a static site generator (mainly for blogs). Articles/pages can be written in reStructuredText or Markdown_ format. - .. _pelican: http://docs.getpelican.com + .. _pelican: https://docs.getpelican.com * tinkerer_ is a static bloggin framework based on Sphinx_. - .. _tinkerer: http://tinkerer.me + .. _tinkerer: https://pypi.org/project/Tinkerer/ * htmlnav_ by Gunnar Schwant, is an HTML writer which supports navigation bars. .. _htmlnav: https://docutils.sourceforge.io/sandbox/gschwant/htmlnav/ -* rest2web_, by Michael Foord, is a tool for creating web sites with - reStructuredText. - - .. _rest2web: http://www.voidspace.org.uk/python/rest2web/ +* rest2web, by Michael Foord, is a tool for creating web sites with + reStructuredText. Development stalled, there is a fork at + https://gitlab.com/wavexx/rest2web * `html4trans <https://docutils.sourceforge.io/sandbox/html4trans/>`__ produces XHTML conforming to the version 1.0 Transitional DTD that @@ -198,7 +197,7 @@ Others * An `XSLT script`__ by Ladislav Lhotka enables reStructuredText annotations to be included in RELAG NG XML schemas. - __ http://www.cesnet.cz/doc/techzpravy/2006/rngrest/ + __ https://www.cesnet.cz/doc/techzpravy/2006/rngrest/ * `DocBook Writer`_ by Oliver Rutherfurd. @@ -225,7 +224,7 @@ Others * For `confluence CMS`_ see https://github.com/netresearch/rst2confluence. - .. _confluence CMS: http://www.atlassian.com/software/confluence + .. _confluence CMS: https://www.atlassian.com/software/confluence * Deploying into wikis might be aided by deploy-rst_. @@ -244,14 +243,14 @@ Convert other formats to reStructuredText: around recommonmark. .. _recommonmark: https://github.com/rtfd/recommonmark - .. _Markdown: http://daringfireball.net/projects/markdown/syntax> - .. _CommonMark: http://commonmark.org/ + .. _Markdown: https://daringfireball.net/projects/markdown/syntax + .. _CommonMark: https://commonmark.org/ * sxw2rest_, by Trent W. Buck, converts StarOffice XML Writer (SXW) - files to reStructuredText. + files to reStructuredText. (link down) - .. _sxw2rest: http://twb.ath.cx/~twb/darcs/sxw2rest/ + .. _sxw2rest: https://twb.ath.cx/~twb/darcs/sxw2rest/ * xml2rst_, an XSLT stylesheet written by Stefan Merten, converts XML dumps of the document tree (e.g. created with rst2xml.py) back to @@ -270,7 +269,7 @@ Convert other formats to reStructuredText: .. _DashTable: https://github.com/gustavklopp/DashTable * Sphinx_ includes a `LaTeX to Rst converter - <http://svn.python.org/projects/doctools/converter/>`__ in its source code + <https://svn.python.org/projects/doctools/converter/>`__ in its source code (trimmed to importing the old Python docs). * Pandoc_ can read Markdown_ and (subsets of) HTML, and LaTeX and @@ -333,7 +332,7 @@ Applications using docutils/reStructuredText and helper applications. #are-there-any-wikis-that-use-restructuredtext-syntax .. _FAQ entry about Blogs: https://docutils.sourceforge.io/FAQ.html #are-there-any-weblog-blog-projects-that-use-restructuredtext-syntax -.. _Project Gutenberg: http://www.gutenberg.org +.. _Project Gutenberg: https://www.gutenberg.org Tools @@ -352,7 +351,7 @@ Tools rerender it. This is very convenient for previewing a document while you're editing it. - .. _restview: http://mg.pov.lt/restview/ + .. _restview: https://mg.pov.lt/restview/ Development @@ -364,19 +363,19 @@ Development The `Python documentation`_ is based on reStructuredText and Sphinx. - .. _Python documentation: http://docs.python.org/ + .. _Python documentation: https://docs.python.org/ * Trac_, a project management and bug/issue tracking system, supports `using reStructuredText - <http://trac.edgewall.org/wiki/WikiRestructuredText>`__ as an + <https://trac.edgewall.org/wiki/WikiRestructuredText>`__ as an alternative to wiki markup. - .. _Trac: http://trac.edgewall.org/ + .. _Trac: https://trac.edgewall.org/ * PyLit_ provides a bidirectional text <--> code converter for *literate programming with reStructuredText*. - .. _PyLit: http://repo.or.cz/pylit.git + .. _PyLit: https://repo.or.cz/pylit.git CMS Systems @@ -387,8 +386,8 @@ CMS Systems * ZReST_, by Richard Jones, is a "ReStructuredText Document for Zope_" application that is complete and ready to install. -.. _Plone: http://plone.org/ -.. _Zope: http://www.zope.org/ +.. _Plone: https://plone.org/ +.. _Zope: https://www.zope.dev/ .. _ZReST: https://docutils.sourceforge.io/sandbox/richard/ZReST/ diff --git a/docutils/docs/user/mailing-lists.txt b/docutils/docs/user/mailing-lists.txt index 7664d585b..20a8bd639 100644 --- a/docutils/docs/user/mailing-lists.txt +++ b/docutils/docs/user/mailing-lists.txt @@ -50,13 +50,6 @@ mailing lists; use the one you feel most comfortable with. __ `docutils-users mailing list`_ -.. * Using Gmane's `web interface`__. To post a message, click "post" or - "followup" in the drop-down menu on the right. (Gmane also has a - complete **archive** of the mailing list; use the search form at the - top of this page to search it.) - - __ http://news.gmane.org/gmane.text.docutils.user - * Use a newsreader with Gmane's `NNTP interface`__ (gmane.text.docutils.user on news.gmane.org). @@ -70,8 +63,8 @@ mailing lists; use the one you feel most comfortable with. receive copies [CCs] of any replies) or check for answers in the `Docutils-users Archives`_. -The first time you post a message without being subscribed (also when -posting via Gmane), you will receive an automatic response with the subject +The first time you post a message without being subscribed +you will receive an automatic response with the subject "Your message to Docutils-users awaits moderator approval"; this is done to prevent spam to the mailing lists. Your message will usually be approved within a few hours. To avoid duplicates, please do not resend your message @@ -98,7 +91,7 @@ To see the collection of prior postings to the list, visit the __ `Docutils-develop mailing list`_ __ nntp://news.gmane.org/gmane.text.docutils.devel -__ http://sourceforge.net/mailarchive/forum.php?forum_name=docutils-develop +__ https://sourceforge.net/mailarchive/forum.php?forum_name=docutils-develop Docutils-checkins ----------------- @@ -140,17 +133,17 @@ __ nntp://news.gmane.org/gmane.comp.python.documentation .. _Docutils-users mailing list: - http://lists.sourceforge.net/lists/listinfo/docutils-users + https://lists.sourceforge.net/lists/listinfo/docutils-users .. _Docutils-users Archives: - http://sourceforge.net/mailarchive/forum.php?forum_name=docutils-users + https://sourceforge.net/mailarchive/forum.php?forum_name=docutils-users .. _Docutils-develop mailing list: - http://lists.sourceforge.net/lists/listinfo/docutils-develop + https://lists.sourceforge.net/lists/listinfo/docutils-develop .. _Docutils-develop Archives: - http://sourceforge.net/mailarchive/forum.php?forum_name=docutils-develop + https://sourceforge.net/mailarchive/forum.php?forum_name=docutils-develop .. _Docutils-checkins list: - http://lists.sourceforge.net/lists/listinfo/docutils-checkins + https://lists.sourceforge.net/lists/listinfo/docutils-checkins .. _Doc-SIG: - http://mail.python.org/mailman/listinfo/doc-sig + https://mail.python.org/mailman/listinfo/doc-sig .. _Subversion repository: ../dev/repository.html .. _Docutils: https://docutils.sourceforge.io/ diff --git a/docutils/docs/user/odt.txt b/docutils/docs/user/odt.txt index 5dcc9ba8d..115c3250a 100644 --- a/docutils/docs/user/odt.txt +++ b/docutils/docs/user/odt.txt @@ -717,8 +717,8 @@ contain them, do the following: configuration file obeys the file format supported by the Python ConfigParser module: `ConfigParser -- Configuration file parser -- - http://docs.python.org/lib/module-ConfigParser.html - <http://docs.python.org/lib/module-ConfigParser.html>`_. + https://docs.python.org/3/library/configparser.html + <https://docs.python.org/3/library/configparser.html>`_. 2. In the "Formats" section of the configuration file, create one option (a name-value pair) for each custom style name that you @@ -1186,7 +1186,7 @@ pick up the default paper size on platforms where the program .. _`Pygments`: - http://pygments.pocoo.org/ + https://pygments.org/ .. _`Docutils`: https://docutils.sourceforge.io/ @@ -1195,7 +1195,7 @@ pick up the default paper size on platforms where the program https://en.wikipedia.org/wiki/Python_Imaging_Library .. _`Open Document at Wikipedia`: - http://en.wikipedia.org/wiki/OpenDocument + https://en.wikipedia.org/wiki/OpenDocument .. _`OASIS Open Document Format for Office Applications (OpenDocument) TC`: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office diff --git a/docutils/docs/user/rst/demo.txt b/docutils/docs/user/rst/demo.txt index 5e62dae34..cf36d1633 100644 --- a/docutils/docs/user/rst/demo.txt +++ b/docutils/docs/user/rst/demo.txt @@ -88,9 +88,9 @@ Inline Markup Paragraphs contain text and may contain inline markup: *emphasis*, **strong emphasis**, ``inline literals``, standalone hyperlinks -(http://www.python.org), external hyperlinks (Python_), internal +(https://www.python.org), external hyperlinks (Python_), internal cross-references (example_), external hyperlinks with embedded URIs -(`Python web site <http://www.python.org>`__), footnote references +(`Python web site <https://www.python.org>`__), footnote references (manually numbered [1]_, anonymous auto-numbered [#]_, labeled auto-numbered [#label]_, or symbolic [*]_), citation references ([CIT2002]_), substitution references (|example|), and _`inline @@ -370,7 +370,7 @@ Targets_, which is a subsection of `Body Elements`_. Explicit external targets are interpolated into references such as "Python_". -.. _Python: http://www.python.org/ +.. _Python: https://www.python.org Targets may be indirect and anonymous. Thus `this phrase`__ may also refer to the Targets_ section. @@ -521,7 +521,7 @@ Meta ```` The `“meta” directive`__ is used to specify metadata to be stored in, -e.g., HTML META tags or ODT file properties. +e.g., HTML META__ tags or ODT file properties. .. meta:: :keywords: reStructuredText, test, parser diff --git a/docutils/docs/user/rst/quickref.html b/docutils/docs/user/rst/quickref.html index 97168b452..11ae13ee9 100644 --- a/docutils/docs/user/rst/quickref.html +++ b/docutils/docs/user/rst/quickref.html @@ -731,7 +731,7 @@ unindented literal blocks: </table> <p>"The <a - href="http://www.python.org/doc/current/lib/module-doctest.html">doctest</a> + href="https://docs.python.org/3/library/doctest.html">doctest</a> module searches a module's docstrings for text that looks like an interactive Python session, then executes all such sessions to verify they still work exactly as shown." (From the doctest docs.) @@ -1069,12 +1069,12 @@ A transition marker is a horizontal line <td rowspan="2"> <samp>External hyperlinks, like Python_.</samp> - <p><samp>.. _Python: http://www.python.org/</samp> + <p><samp>.. _Python: https://www.python.org/</samp> <td> <table width="100%"> <tr bgcolor="#99CCFF"><td><em>Fold-in form</em> <tr><td>External hyperlinks, like - <a href="http://www.python.org/">Python</a>. + <a href="https://www.python.org/">Python</a>. </table> <tr valign="top"> <td> @@ -1086,7 +1086,7 @@ A transition marker is a horizontal line <p><table> <tr><td colspan="2"><hr> <tr><td><a name="labPython"><i>Python:</i></a> - <td> <a href="http://www.python.org/">http://www.python.org/</a> + <td> <a href="https://www.python.org/">https://www.python.org/</a> </table> </table> </table> @@ -1117,9 +1117,9 @@ A transition marker is a horizontal line <tr valign="top"> <td rowspan="2"> <samp>External hyperlinks, like `Python -<br><http://www.python.org/>`_.</samp> +<br><https://www.python.org/>`_.</samp> <td>External hyperlinks, like - <a href="http://www.python.org/">Python</a>. + <a href="https://www.python.org/">Python</a>. </table> <h4><a href="#contents" name="internal-hyperlink-targets" class="backref" @@ -1180,13 +1180,13 @@ A transition marker is a horizontal line <samp>Python_ is `my favourite <br>programming language`__.</samp> - <p><samp>.. _Python: http://www.python.org/</samp> + <p><samp>.. _Python: https://www.python.org/</samp> <p><samp>__ Python_</samp> <td> - <p><a href="http://www.python.org/">Python</a> is - <a href="http://www.python.org/">my favourite + <p><a href="https://www.python.org/">Python</a> is + <a href="https://www.python.org/">my favourite programming language</a>. </table> @@ -1341,7 +1341,7 @@ dispose of medical waste.</samp> reStructuredText should <a href="mailto:docutils-users@lists.sourceforge.net" >post a message</a> to the <a - href="http://lists.sourceforge.net/lists/listinfo/docutils-users" + href="https://lists.sourceforge.net/lists/listinfo/docutils-users" >Docutils-Users mailing list</a>. The <a href="https://docutils.sourceforge.io/" >Docutils project web site</a> has more information. diff --git a/docutils/docs/user/slide-shows.txt b/docutils/docs/user/slide-shows.txt index fdf481fab..054b11376 100644 --- a/docutils/docs/user/slide-shows.txt +++ b/docutils/docs/user/slide-shows.txt @@ -691,7 +691,7 @@ Making a Custom Theme Resources: - * W3C's `Learning CSS <http://www.w3.org/Style/CSS/learning>`__ + * W3C's `Learning CSS <https://www.w3.org/Style/CSS/learning>`__ * `Creating An S5 Theme <http://home.cogeco.ca/~ve3ll/s5themes.htm>`__ diff --git a/docutils/docs/user/smartquotes.txt b/docutils/docs/user/smartquotes.txt index 260f3073e..a186501ad 100644 --- a/docutils/docs/user/smartquotes.txt +++ b/docutils/docs/user/smartquotes.txt @@ -453,7 +453,7 @@ the source: .. _right single quotation mark: http://www.fileformat.info/info/unicode/char/2019/index.htm -.. _Unicode: http://www.unicode.org/charts/PDF/U2000.pdf +.. _Unicode: https://www.unicode.org/charts/PDF/U2000.pdf History ======= diff --git a/docutils/docs/user/tools.txt b/docutils/docs/user/tools.txt index 5b85e076d..b4dc776fb 100644 --- a/docutils/docs/user/tools.txt +++ b/docutils/docs/user/tools.txt @@ -352,10 +352,10 @@ For details, please see `Easy Slide Shows With reStructuredText & S5 <slide-shows.html>`_. -.. _HTML 5: http://www.w3.org/TR/html5/ -.. _HTML 4.1: http://www.w3.org/TR/html401/ -.. _XHTML 1.0 Transitional: http://www.w3.org/TR/xhtml1/ -.. _XHTML 1.1: http://www.w3.org/TR/xhtml1/ +.. _HTML 5: https://www.w3.org/TR/html5/ +.. _HTML 4.1: https://www.w3.org/TR/html401/ +.. _XHTML 1.0 Transitional: https://www.w3.org/TR/xhtml1/ +.. _XHTML 1.1: https://www.w3.org/TR/xhtml1/ LaTeX-Generating Tools |