Re: No table of contents in split HTML output

2020-01-15 Thread Jean-Christophe Helary



> On Jan 15, 2020, at 20:37, Gavin Smith  wrote:
> 
> On Fri, Dec 27, 2019 at 12:49 AM Jean-Christophe Helary
>  wrote:
>> 
>> Apologies.
>> 
>> The behavior is only seen in the Elisp Reference.
>> 
>> The split Emacs Manual has Contents that points at
>> emacs.html/index.html#SEC_Contents
>> 
>> and Index that points at
>> emacs.html/Key-Index.html#Key-Index
>> 
>> And both files exist.
>> 
>> So, maybe there is a naming conflict in the Elisp generation process where 
>> index.html#SEC_Contents is later overwritten by index.html#Index and since 
>> the html file exists (even if not the node name), the browser just points at 
>> it without generating an error.
>> 
> 
> I haven't tried building the elisp manual myself, but
> https://www.gnu.org/software/emacs/manual/html_node/elisp/index.html#Top
> doesn't have any Contents or Index links at all. I don't know how
> those pages were generated as there is no comment in the files saying
> "Generated by texi2any version" or similar.

Would you mind trying to build locally with just "make docs" ?


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune





Re: No table of contents in split HTML output

2020-01-15 Thread Gavin Smith
On Fri, Dec 27, 2019 at 12:49 AM Jean-Christophe Helary
 wrote:
>
> Apologies.
>
> The behavior is only seen in the Elisp Reference.
>
> The split Emacs Manual has Contents that points at
> emacs.html/index.html#SEC_Contents
>
> and Index that points at
> emacs.html/Key-Index.html#Key-Index
>
> And both files exist.
>
> So, maybe there is a naming conflict in the Elisp generation process where 
> index.html#SEC_Contents is later overwritten by index.html#Index and since 
> the html file exists (even if not the node name), the browser just points at 
> it without generating an error.
>

I haven't tried building the elisp manual myself, but
https://www.gnu.org/software/emacs/manual/html_node/elisp/index.html#Top
doesn't have any Contents or Index links at all. I don't know how
those pages were generated as there is no comment in the files saying
"Generated by texi2any version" or similar.



Re: No table of contents in split HTML output

2019-12-27 Thread Patrice Dumas
On Fri, Dec 27, 2019 at 09:49:41AM +0900, Jean-Christophe Helary wrote:
> Apologies.
> 
> The behavior is only seen in the Elisp Reference.
> 
> The split Emacs Manual has Contents that points at
> emacs.html/index.html#SEC_Contents
> 
> and Index that points at
> emacs.html/Key-Index.html#Key-Index
> 
> And both files exist.
> 
> So, maybe there is a naming conflict in the Elisp generation process where 
> index.html#SEC_Contents is later overwritten by index.html#Index and since 
> the html file exists (even if not the node name), the browser just points at 
> it without generating an error.

I don't really understand the issue.  What I can say is that I think that
SEC_Contents target is used even when there is no table of content.  It
is not supposed to match any node (and I think that it cannot, given
that _ is probably transformed in node tragets), but rather to point to
the table of content anchor.  The index target is supposed to point to
the first node with @printindex.  I have not checked an example, but
reading the code, I would assume that there is no target generated if
there is no @printindex.

-- 
Pat



Re: No table of contents in split HTML output

2019-12-26 Thread Jean-Christophe Helary
Apologies.

The behavior is only seen in the Elisp Reference.

The split Emacs Manual has Contents that points at
emacs.html/index.html#SEC_Contents

and Index that points at
emacs.html/Key-Index.html#Key-Index

And both files exist.

So, maybe there is a naming conflict in the Elisp generation process where 
index.html#SEC_Contents is later overwritten by index.html#Index and since the 
html file exists (even if not the node name), the browser just points at it 
without generating an error.

JC


> On Dec 26, 2019, at 23:26, Jean-Christophe Helary 
>  wrote:
> 
> I guess it's a bug but I'd like confirmation...
> 
> When I create a split HTML version of the gnu manuals (currently working on 
> improving their CSS) I get the following behavior:
> 
> The [Contents] and [Index] links respectively point at:
> 
> elisp.html.html/index.html#SEC_Contents
> 
> and 
> 
> elisp.html.html/index.html#Index
> 
> But index.html does not have a SEC_Contents section...
> 
> That section is present when creating an unsplit HTML document, though...
> 
> Can anybody confirm that it's not only my machine/configuration ?
> 
> 
> Jean-Christophe Helary
> ---
> http://mac4translators.blogspot.com @brandelune
> 
> 

Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune