Starting to see some trees in the forrest of links that require
updating...
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/documentation_hacking.xml: Move sourceforge.net
links to https.
* doc/html/manual/documentation_hacking.html: Regenerate.
---
libstdc++-v3/doc/html/manual/documentation_hacking.html | 4 ++--
libstdc++-v3/doc/xml/manual/documentation_hacking.xml | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/libstdc++-v3/doc/html/manual/documentation_hacking.html
b/libstdc++-v3/doc/html/manual/documentation_hacking.html
index bd44b61010d..4e415c32389 100644
--- a/libstdc++-v3/doc/html/manual/documentation_hacking.html
+++ b/libstdc++-v3/doc/html/manual/documentation_hacking.html
@@ -362,7 +362,7 @@
by a vendor package like <code class="filename">libxml2</code> and
<code class="filename">docbook5-schemas-5.0-4</code>
</p><p>
For PDF output, something that transforms valid Docbook XML to PDF is
- required. Possible solutions include <a class="link"
href="http://dblatex.sourceforge.net"; target="_top">dblatex</a>,
+ required. Possible solutions include <a class="link"
href="https://dblatex.sourceforge.net"; target="_top">dblatex</a>,
<span class="command"><strong>xmlto</strong></span>, or <span
class="command"><strong>prince</strong></span>. Of
these, <span class="command"><strong>dblatex</strong></span> is the
default.
Please consult the <code class="email"><<a class="email"
href="mailto:libstd...@gcc.gnu.org";>libstd...@gcc.gnu.org</a>></code> list
when
@@ -370,7 +370,7 @@
suggestions.
</p><p>
For Texinfo output, something that transforms valid Docbook
- XML to Texinfo is required. The default choice is <a class="link"
href="http://docbook2x.sourceforge.net/"; target="_top">docbook2X</a>.
+ XML to Texinfo is required. The default choice is <a class="link"
href="https://docbook2x.sourceforge.net/"; target="_top">docbook2X</a>.
</p><p>
For epub output, the <a class="link"
href="https://sourceforge.net/projects/docbook/files/epub3/";
target="_top">stylesheets</a> for EPUB3 are required. These stylesheets are
still in development. To validate the created file, <a class="link"
href="https://github.com/w3c/epubcheck"; target="_top">epubcheck</a> is
necessary.
</p></div><div class="section"><div class="titlepage"><div><div><h4
class="title"><a id="docbook.rules"></a>Generating the DocBook
Files</h4></div></div></div><p>
diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
index 44672f6e26d..8a1cba92506 100644
--- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
+++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
@@ -779,7 +779,7 @@
<para>
For PDF output, something that transforms valid Docbook XML to PDF is
- required. Possible solutions include <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://dblatex.sourceforge.net";>dblatex</link>,
+ required. Possible solutions include <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://dblatex.sourceforge.net";>dblatex</link>,
<command>xmlto</command>, or <command>prince</command>. Of
these, <command>dblatex</command> is the default.
Please consult the <email>libstd...@gcc.gnu.org</email> list when
@@ -789,7 +789,7 @@
<para>
For Texinfo output, something that transforms valid Docbook
- XML to Texinfo is required. The default choice is <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://docbook2x.sourceforge.net/";>docbook2X</link>.
+ XML to Texinfo is required. The default choice is <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://docbook2x.sourceforge.net/";>docbook2X</link>.
</para>
<para>
--
2.39.1
