Re: permanent links using #fragment names

[Per Bothner]

On 1/9/22 09:45, Eli Zaretskii wrote:
> > Date: Sun, 9 Jan 2022 09:32:38 -0800
> > From: Per Bothner <per@bothner.com>
> >
> > A related change is that we should change how info node/anchor names are
> > mapped into URLs to use standard %-encoding.  This would make URL cleaner
> > and more readable.  For continuity, we could map space to '-', '-' to '%45',
> > and other characters as in standard percent-encoding.  An initial '-' could
> > be used for texinfo-internal ids such as the "-toc-foo" or "-def-printf".
>
> What does this mean for letter-case clashes on case-insensitive
> filesystems?  The most frequent case is Index.html vs index.html, but
> there are others.

Well, I was mostly focusing on fragment identifiers, not file names.
Fragment identifeirs of course don't care about file systems.
Currently, filenames are generated preserving the source case;
I don't know what we do if case-folding leads to a name clash,
but we can continue doing something similar.
--
        --Per Bothner
per@bothner.com   http://per.bothner.com/