[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs manuals: make docs (html) issue with the index.html output

From: Jean-Christophe Helary
Subject: Re: emacs manuals: make docs (html) issue with the index.html output
Date: Wed, 22 Dec 2021 16:19:09 +0900

> On Dec 22, 2021, at 4:00, Gavin Smith <gavinsmith0123@gmail.com> wrote:
> On Tue, Oct 19, 2021 at 08:30:59PM +0900, Jean-Christophe Helary wrote:
>>>> When running "make docs" to produce the emacs manuals HTML sets with the 
>>>> following options:
>>>> HTML_OPTS = --split=chapter --html
>>>> There are issues with the ToC files and index files in
>>>> 1) the elisp reference set
>>>> 2) the lisp intro set
>>>> In both cases, the issue seems to be that the ToC is output as 
>>>> "index.html#SEC_Contents" and is then overwritten by the index which is 
>>>> output as "Index.html" (notice the change in case).
>>>> The navigation HTML reads:
>>>> [<a href="index.html#SEC_Contents" title="Table of contents" 
>>>> rel="contents">Contents</a>][<a href="Index.html" title="Index" 
>>>> rel="index">Index</a>]
>>> Can you link to an online manual where the problem occurs as I couldn't find
>>> one (I checked three of the emacs manuals before giving up).
>> https://doublet.jp/gnu/
>> https://doublet.jp/gnu/elisp/elisp.html/index.html
>> https://doublet.jp/gnu/lispintro/emacs-lisp-intro.html/index.html
>>>> It looks like (I have not checked for all the manuals) when a manual only 
>>>> has 1 index it is output as Index.html and the ToC is output as 
>>>> index.html, but on case-insensitive systems (macOS) the files conflict and 
>>>> only the index is kept (presumably after overwriting the ToC).
>>> Have you actually tested this on macOS?
>> Yes. That's my machine.
> I'm trying to catch up with Texinfo mail.
> I saw the problem with the Top node not being present in the links you sent 
> above.
> There appears to be code to check a CASE_INSENSITIVE_FILENAMES configuration
> value in Texinfo/Common.pm, now in set_tree_unit_file.  Could you try
> building your manuals with texi2any -c CASE_INSENSITIVE_FILENAMES=1 and see
> if that makes a difference?

Thank you Gavin for looking into this.

I've checked where the manuals creation process calls texi2any and failed to 
find anything. It looks like makeinfo is an alias to texi2any to what I did is 
add the option to the various makefiles:

for ex:

MAKEINFO_OPTS = --force --enable-encoding -I $(srcdir) -c 

checking right now it that works...

Jean-Christophe Helary @brandelune

reply via email to

[Prev in Thread] Current Thread [Next in Thread]