emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@gnu.org>
To: Max Nikulin <manikulin@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Some links in online manual do not work
Date: Wed, 12 Oct 2022 06:11:47 +0200	[thread overview]
Message-ID: <87a661he9o.fsf@gnu.org> (raw)
In-Reply-To: <b7c8d23b-79d1-b864-cdc5-a2f0afc4e811@gmail.com> (Max Nikulin's message of "Wed, 12 Oct 2022 10:06:14 +0700")

Max Nikulin <manikulin@gmail.com> writes:

> Unfortunately some redirection targets still respond with 301
>
> 301 https://orgmode.org/manual/Dates-and-Times.html
> 301 https://orgmode.org/manual/Deadlines-and-Scheduling.html
> 301 https://orgmode.org/manual/Emphasis-and-Monospace.html
> 301 https://orgmode.org/manual/Export-in-Foreign-Buffers.html
> 301 https://orgmode.org/manual/HTML-export-commands.html
> 301 https://orgmode.org/manual/Properties-and-Columns.html

Fixed, thanks.

> If redirection directives were included as separate files then it
> would be possible to just check them by a command like
>
>     awk '{ if ($NF >= 3) print $3; }' /tmp/manual.txt  |
>         xargs --replace -- \
>         curl --head --write-out '%{http_code} %{url_effective}\n' \
>             --silent --show-error --output /dev/null \
>             'https://orgmode.org/manual/{}'

https://git.sr.ht/~bzg/worg/tree/master/item/nginx.conf contains the
list of redirections -- the checks could be done from here, right?

> Original proposal to add redirections contained an s-expression with
> mappings. I would consider tracking it in the main Org repository. I
> believe, list of info nodes in the released manual should be added to
> it as known names. 

I'm not sure I understand.  Nothing should be added to the main Org
repository to fix a problem with the orgmode.org website, even if it
is a problem with the HTML manual as produced from org-mode.git.

> The idea is to make it easier to add redirections
> before new release. With such list as an input, a simple script could
> detect nodes absent in new release but existed in the earlier
> one. Another case is names appeared again making redirection rules
> obsolete.

I'm not in favor of going into this direction.

So far we provide an easy fix via rewrite rules to the problem created
with the change in the way Texinfo produces URLs.

Such rewrite rules are fine when they are like "rewrite THIS-URL.html
this-url.html" because stumbling on a dead link just because of lower
vs upper case letters is way too frustrating.

But more complex rewrite rules (from old manual nodes to new ones) is
IMHO calling for trouble. What if we split the "Properties and Column"
manual page into "Properties" and "Columns"?  Where to redirect?

-- 
 Bastien


  reply	other threads:[~2022-10-12  4:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 20:00 Some links in online manual do not work Tim Landscheidt
2022-10-02 21:04 ` Tim Cross
2022-10-03  3:52   ` Ihor Radchenko
2022-10-05 17:48   ` Tim Landscheidt
2022-10-06  4:17     ` Ihor Radchenko
2022-10-06 12:14       ` Tim Landscheidt
2022-10-07 15:33       ` Bastien Guerry
2022-10-07 19:50         ` Tim Landscheidt
2022-10-08  6:28           ` Ihor Radchenko
2022-10-08 12:37           ` Max Nikulin
2022-10-11  5:37             ` Bastien
2022-10-11  6:57               ` Max Nikulin
2022-10-11  7:57                 ` Bastien
2022-10-11  8:33                   ` Max Nikulin
2022-10-11  9:09                     ` Bastien
2022-10-11 16:51                       ` Max Nikulin
2022-10-11 17:06                         ` Bastien Guerry
2022-10-12  3:06                           ` Max Nikulin
2022-10-12  4:11                             ` Bastien Guerry [this message]
2022-10-12  5:14                               ` Max Nikulin
2022-10-16 12:11                           ` Tim Landscheidt

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://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87a661he9o.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    /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/emacs/org-mode.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).