On 1/9/22 11:53, Gavin Smith wrote:
It's certainly more elegant, but we are not generating documentation
to be served as part of some large information processing service,
like Wikipedia or other websites which don't use .html extensions.
We're generating a self-contained set of files that repres
On Sun, Jan 09, 2022 at 08:52:59PM +, Gavin Smith wrote:
> I was looking at the TODO file for Texinfo, and reading this again:
>
> > - Monitor and improve the dir categories in existing manuals,
> >following the Free Software Directory categories. Much mail to
> >developers has alrea
I was looking at the TODO file for Texinfo, and reading this again:
> - Monitor and improve the dir categories in existing manuals,
>following the Free Software Directory categories. Much mail to
>developers has already been sent, what's needed now is to check new
>releases and make
On 1/9/22 11:01, Gavin Smith wrote:
It can't be, I'm afraid as we are not going to demand that users
use JavaScript in their browsers to access web documentation.
No, but I think it is reasonable that people who won't use JavaScript
get a clunkier user interface.
Navigating within a manual
On Sun, Jan 09, 2022 at 11:19:03AM -0800, Per Bothner wrote:
> > Can this be done without JavaScript or is it only for info.js?
>
> If the manual is not split, then JavaScript would not be needed.
> Otherwise, JavaScript would be needed to resolve a fragment id
> to load the correct page. However
> From: Gavin Smith
> Date: Sun, 9 Jan 2022 19:02:58 +
> Cc: Per Bothner , bug-texinfo@gnu.org
>
> > AFAIU, it does. This is a long-standing problem with Texinfo. It was
> > solved at some point, but the solution was lost when we moved to
> > texi2any from the C implementation of makeinfo.
On 1/9/22 10:28, Gavin Smith wrote:
On Sun, Jan 09, 2022 at 09:32:38AM -0800, Per Bothner wrote:
An idea I've been mulling: Currently, we handle changes in node structure
by generating extra stub pages that redirect to the correct location.
This works, but it's a bit clunky. For one thing, i
On Sun, Jan 09, 2022 at 08:50:23PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 9 Jan 2022 10:30:18 -0800
> > Cc: bug-texinfo@gnu.org
> > From: Per Bothner
> >
> > I don't know what we do if case-folding leads to a name clash,
>
> AFAIU, it does. This is a long-standing problem with Texinfo. It
> On 1/9/22 09:47, Eli Zaretskii wrote:
> > > For example, the Keys chapter in the Emacs manual would still be in the
> > > file Keys.html, and you can still browse to
> > > "https://whatever/emacs/Keys.html";.
> > > However, the "perma-link" would be "https://whatever/emacs#Keys";, and that
> > >
> Date: Sun, 9 Jan 2022 10:44:27 -0800
> Cc: bug-texinfo@gnu.org
> From: Per Bothner
>
>
>
> On 1/9/22 09:47, Eli Zaretskii wrote:
> >> For example, the Keys chapter in the Emacs manual would still be in the
> >> file Keys.html, and you can still browse to
> >> "https://whatever/emacs/Keys.htm
> Date: Sun, 9 Jan 2022 10:30:18 -0800
> Cc: bug-texinfo@gnu.org
> From: Per Bothner
>
> I don't know what we do if case-folding leads to a name clash,
AFAIU, it does. This is a long-standing problem with Texinfo. It was
solved at some point, but the solution was lost when we moved to
texi2any
On 1/9/22 09:47, Eli Zaretskii wrote:
For example, the Keys chapter in the Emacs manual would still be in the
file Keys.html, and you can still browse to "https://whatever/emacs/Keys.html";.
However, the "perma-link" would be "https://whatever/emacs#Keys";, and that
is what would show in the l
On Sun, Jan 09, 2022 at 09:32:38AM -0800, Per Bothner wrote:
> 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 ot
On 1/9/22 09:45, Eli Zaretskii wrote:
Date: Sun, 9 Jan 2022 09:32:38 -0800
From: Per Bothner
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 spa
On Sun, Jan 09, 2022 at 09:32:38AM -0800, Per Bothner wrote:
> An idea I've been mulling: Currently, we handle changes in node structure
> by generating extra stub pages that redirect to the correct location.
> This works, but it's a bit clunky. For one thing, it doesn't update
> the location bar
> Date: Sun, 9 Jan 2022 09:32:38 -0800
> From: Per Bothner
>
> An idea I've been mulling: Currently, we handle changes in node structure
> by generating extra stub pages that redirect to the correct location.
> This works, but it's a bit clunky. For one thing, it doesn't update
> the location ba
> Date: Sun, 9 Jan 2022 09:32:38 -0800
> From: Per Bothner
>
> 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
An idea I've been mulling: Currently, we handle changes in node structure
by generating extra stub pages that redirect to the correct location.
This works, but it's a bit clunky. For one thing, it doesn't update
the location bar (though that could be fixed). Worse, it highlights a
two-level name
On Sat, Jan 08, 2022 at 07:02:19PM +, Gavin Smith wrote:
> On Fri, Jan 07, 2022 at 03:43:52PM +0100, Patrice Dumas wrote:
> > Hello,
> >
> > I would like to setup rules on class names used in HTML attributes, with
> > the final aim to make it easier for users to do CSS, javascript or HTML
> >
19 matches
Mail list logo
