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

2021-10-18 Thread Jean-Christophe Helary
I am not sure whether this is an emacs "make" issue or a texinfo issue so I am sending this report to the 2 lists. 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

Re: Online manuals issues when read from mobile devices

2021-10-18 Thread Jean-Christophe Helary
> On Oct 19, 2021, at 8:41, Jean-Christophe Helary > wrote: > For the layout itself and the overall text width, @media directives are a > nice addition. They allow the menu to be turned into a column instead of > being a broken line as it would be today, etc. I wrote something in the past.

Re: Revisiting: @pxref does not always produce "see" in info reader

2021-10-18 Thread Jean-Christophe Helary
> On Oct 19, 2021, at 9:22, Gavin Smith wrote: > > On Tue, Oct 19, 2021 at 08:12:28AM +0900, Jean-Christophe Helary wrote: >> Also, with translators trying to work on texinfo documents, it is actually a >> problem to have such strings pop-up in sentences. And it is not practical to >> have c

Re: Revisiting: @pxref does not always produce "see" in info reader

2021-10-18 Thread Gavin Smith
On Tue, Oct 19, 2021 at 08:12:28AM +0900, Jean-Christophe Helary wrote: > Also, with translators trying to work on texinfo documents, it is actually a > problem to have such strings pop-up in sentences. And it is not practical to > have catalogs of translations of "see" that include the translati

Re: Online manuals issues when read from mobile devices

2021-10-18 Thread Jean-Christophe Helary
> On Oct 19, 2021, at 4:27, Gavin Smith wrote: > > On Mon, Oct 11, 2021 at 10:35 PM Carlos Pita > wrote: >> >> Hi, >> >> when read from a phone, there are some issues with the documentation >> of emacs, elisp and org-mode that is available online in html format: >> navigation links, subsec

Re: Revisiting: @pxref does not always produce "see" in info reader

2021-10-18 Thread Jean-Christophe Helary
> On Oct 19, 2021, at 4:46, Gavin Smith wrote: > > On Fri, Oct 15, 2021 at 8:36 AM Benno Schulenberg wrote: >> Today I noticed that when using emacs to view the nano.info file, the >> *note after an mdash does get a "see" before the crosslink. Would it >> be possible to make also 'info' cons

Re: Revisiting: @pxref does not always produce "see" in info reader

2021-10-18 Thread Gavin Smith
On Fri, Oct 15, 2021 at 8:36 AM Benno Schulenberg wrote: > Today I noticed that when using emacs to view the nano.info file, the > *note after an mdash does get a "see" before the crosslink. Would it > be possible to make also 'info' consider an mdash (plus possible space) > equivalent to an open

Re: Revisiting: @pxref does not always produce "see" in info reader

2021-10-18 Thread Gavin Smith
On Fri, Oct 15, 2021 at 8:36 AM Benno Schulenberg wrote: > By the way, in the last paragraph of 'info texinfo cross @p' there are: > > many circumstance > preferrable > > And elsewhere in the manual: > > defailed menu > conventionial > Thanks, fixed. (I haven't checked but I think I was r

Re: Online manuals issues when read from mobile devices

2021-10-18 Thread Gavin Smith
On Mon, Oct 11, 2021 at 10:35 PM Carlos Pita wrote: > > Hi, > > when read from a phone, there are some issues with the documentation > of emacs, elisp and org-mode that is available online in html format: > navigation links, subsection entries and code sections are barely > visible and not proport

Re: version 6.8 forces Table of Contents to top of HTML document

2021-10-18 Thread Benno Schulenberg
Op 17-10-2021 om 13:18 schreef Gavin Smith: > You can get the old behaviour back by specifying "-c FORMAT_MENU=menu". Thanks. Combining "-c CONTENTS_OUTPUT_LOCATION=inline" and "-c FORMAT_MENU=menu" brings back the old arrangement. Almost. Because now each menu item is followed by a colon.