From: Ori <email@example.com>
To: Bastien <firstname.lastname@example.org>
Subject: Re: Possible bug report: URL capitalization in online manual
Date: Sat, 8 Feb 2020 14:25:57 -0500 [thread overview]
Message-ID: <CACyCJqW_kQNwLbJ3xPxHeHSA29rL=Xv8MtqwKygxwD2email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
I'm not sure which repo this all lives in but I believe since information
has been added to the paths, this should be easy. The other direction would
be trickier and would need the old scheme.
Wherever the current filename has capital letters after the first
character, make an alias using the sentence-case version.
Happy to take a stab at this if you can point me to the repo!
On Sat, Feb 8, 2020 at 2:15 PM Bastien <firstname.lastname@example.org> wrote:
> Hi Ori,
> Ori Barbut <email@example.com> writes:
> > Not sure if this was intentional?
> Yes -- old html manual pages where still around and I deleted them,
> because they confused people.
> > If so would it make sense to alias the old URLs for people who have
> > linked to the manual over the years?
> Yes, such aliases would make sense at the web server level.
> Can you track back on when the new scheme has been output when
> exporting the manual and provide an alias list I should add to
> the web server?
> That would really help a lot!
[-- Attachment #2: Type: text/html, Size: 1555 bytes --]
next prev parent reply other threads:[~2020-02-08 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 18:51 Possible bug report: URL capitalization in online manual Ori Barbut
2020-02-08 19:15 ` Bastien
2020-02-08 19:25 ` Ori [this message]
2020-02-08 19:56 ` Bastien
2020-02-09 18:49 ` Ori
2020-02-10 6:48 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).