unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Gavin Smith <gavinsmith0123@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Texinfo <bug-texinfo@gnu.org>, 22651@debbugs.gnu.org
Subject: bug#22651: "Up (dir)" HTML link is 404
Date: Wed, 4 May 2016 19:07:20 +0100	[thread overview]
Message-ID: <CAKPWYQ3muG3nLo8yQJVhe9ueLQPohSUn9it3vq6s8JvWLfgSKw__29948.4702795327$1462385321$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <877ffaj20x.fsf_-_@gnu.org>

On 3 May 2016 at 21:54, Ludovic Courtès <ludo@gnu.org> wrote:
> Hello,
>
> Following the “Up (dir)” from:
>
>   https://www.gnu.org/software/guix/manual/html_node/index.html#Top
>
> leads to:
>
>   https://www.gnu.org/software/guix/manual/dir/index.html
>
> which is 404.
>
> Can htmlxref.cnf specify what the “dir” URL should be?

It could do, but am not sure if it is a good idea. For one thing, a
page with a list of manuals is not a Texinfo manual, so having an
htmlxref.cnf line for this is an exception, which is slightly
confusing and could cause problems. For example, if you refer to the
node "(dir)Top" this would tend to go to a page called "index.html",
which may not be what the page is called. A more important problem is
that a page with a list of GNU manuals on it would only be an
appropriate "Up" link for GNU manuals.

The way to deal with this broken link at the moment is to use the
TOP_NODE_UP customization variable, like

 makeinfo --html -c TOP_NODE_UP_URL=/manual/ ...

https://www.gnu.org/software/texinfo/manual/texinfo/html_node/First-Node.html#First-Node


>
> If so, what about hosting a “dir” somewhere on gnu.org and have the
> default htmlxref.cnf that comes with Texinfo point to that?
>
> Thanks,
> Ludo’.
>

  parent reply	other threads:[~2016-05-04 18:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-13 17:06 bug#22651: Up: GNU Guix doc produces 404 page not found myglc2
2016-02-15 19:49 ` Alex Kost
2016-02-15 20:06   ` carl hansen
2016-02-15 23:10     ` Thompson, David
2016-02-16  0:59       ` carl hansen
2016-02-16  1:22         ` Leo Famulari
2016-05-03 20:54   ` bug#22651: "Up (dir)" HTML link is 404 Ludovic Courtès
     [not found]   ` <877ffaj20x.fsf_-_@gnu.org>
2016-05-04 18:07     ` Gavin Smith [this message]
     [not found]     ` <CAKPWYQ3muG3nLo8yQJVhe9ueLQPohSUn9it3vq6s8JvWLfgSKw@mail.gmail.com>
2016-05-05 12:47       ` Ludovic Courtès
     [not found]       ` <87h9ecekn5.fsf@gnu.org>
2016-05-05 14:44         ` Gavin Smith
2016-05-07 17:25 ` bug#22651: [PATCH] gendocs.sh: Fix "dir" link in HTML output Ludovic Courtès
2016-09-27 16:53 ` bug#22651: fixed, please close ng0
2016-09-30 16:12   ` Ludovic Courtès
2016-09-27 18:51 ` bug#22651: ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKPWYQ3muG3nLo8yQJVhe9ueLQPohSUn9it3vq6s8JvWLfgSKw__29948.4702795327$1462385321$gmane$org@mail.gmail.com' \
    --to=gavinsmith0123@gmail.com \
    --cc=22651@debbugs.gnu.org \
    --cc=bug-texinfo@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).