>> Comparing the HTML of version 6.8 with version 7.2, I see that many
>> classes got new names. This means that we essentially have to
>> rewrite our custom CSS file, which is not fun.
>>
>> What about providing a script
>>
>> ```
>> texinfo-css-update --from 6.8 --to 7.2 < infile > outfile
>> ``
Hello Patrice and Gavin,
thanks for your answers.
>> Why ``? I consider this surprising since the item description
>> of a menu entry (i.e., the third part of an entry) is not output
>> with ``.
>
> The idea was that the users may have wanted to have the end lines
> and spaces to be signific
>> What must I do to always get a navigation panel in the footer
>> (i.e., `NODE_FOOTER_BUTTONS`)?
>
> texi2any --html -c FORMAT_MENU=menu -c WORDS_IN_PAGE=0 test.texi
>
> The setting of FORMAT_MENU is immaterial.
Thanks!
> This question has been asked so many times before that I wonder if
>
On Tue, Jul 08, 2025 at 10:53:39PM +0100, Gavin Smith wrote:
> and the one I found was this:
>
> https://lilypond.org/doc/v2.25/Documentation/css/lilypond-manuals.css
>
> If that is the only CSS file, then it seems plausible that we could work
> together on what would have to be updated. I'm afr
On Tue, Jul 08, 2025 at 12:19:58PM +, Werner LEMBERG wrote:
>
> Comparing the HTML of version 6.8 with version 7.2, I see that many
> classes got new names. This means that we essentially have to rewrite
> our custom CSS file, which is not fun.
>
> What about providing a script
>
> ```
> te
On Tue, Jul 08, 2025 at 12:19:58PM +, Werner LEMBERG wrote:
>
> Comparing the HTML of version 6.8 with version 7.2, I see that many
> classes got new names. This means that we essentially have to rewrite
> our custom CSS file, which is not fun.
>
> What about providing a script
>
> ```
> te
On Tue, Jul 08, 2025 at 07:42:13PM +, Werner LEMBERG wrote:
>
> [texi2any 6.8, 7.2]
>
>
> texi2any --html -c FORMAT_MENU=menu menu.texinfo
> ```
>
> There is only a header but no footer navigation panel.
>
> What must I do to always get a navigation panel in the footer (i.e.,
> `NODE_FOOT
On Tue, Jul 08, 2025 at 12:07:11PM +, Werner LEMBERG wrote:
>
> [texi2any 7.2]
>
>
> texi2any --html -c FORMAT_MENU=menu menu.texinfo
> ```
>
> the menu comment in output file `index.html` gets formatted like this:
>
> ```
>
>
>
> XXX yyy ZZZ
>
>
>
> ```
>
> Why ``? I consider thi
On Tue, Jul 08, 2025 at 12:07:11PM +, Werner LEMBERG wrote:
>
> [texi2any 7.2]
>
>
> Consider the following example file `menu.texinfo`.
>
> ```
> \input texinfo
>
> @node Top
> @top Top
>
> @menu
> * Foo:: Foo foo foo.
>
>
> XXX @var{yyy} ZZZ
>
>
> * Bar:: Bar bar bar.
> @end menu
>
On Tue, Jul 08, 2025 at 07:42:13PM +, Werner LEMBERG wrote:
> There is both a header and a footer navigation panel. However, the
> files `Foo.html` and `Bar.html` look like the following:
>
> ```
> Previous: Foo, Up: Top
> ---
>
> ...
>
> ```
>
> There is only a
On Mon, Jul 07, 2025 at 06:08:37PM +, Werner LEMBERG wrote:
> > I am not really sure which is better. There is more in chapter 17
> > and one argument is that it is better to start a new page for
> > chapter 17's contents listing.
>
> Both are OK to me. However, what I have a problem with ar
Comparing the HTML of version 6.8 with version 7.2, I see that many
classes got new names. This means that we essentially have to rewrite
our custom CSS file, which is not fun.
What about providing a script
```
texinfo-css-update --from 6.8 --to 7.2 < infile > outfile
```
that does the job, r
[texi2any 6.8, 7.2]
Consider the following example file `menu.texinfo`.
```
\input texinfo
@node Top
@top Top
@menu
* Foo:: Foo foo foo.
* Bar:: Bar bar bar.
@end menu
@node Foo
@chapter Foo
Foo
@node Bar
@chapter Bar
Baz
@bye
```
If I process this with
```
texi2any --html -c FORMAT_M
[texi2any 7.2]
Consider the following example file `menu.texinfo`.
```
\input texinfo
@node Top
@top Top
@menu
* Foo:: Foo foo foo.
XXX @var{yyy} ZZZ
* Bar:: Bar bar bar.
@end menu
@node Foo
@chapter Foo
Foo
@node Bar
@chapter Bar
Baz
@bye
```
If I process this with
```
texi2any -
14 matches
Mail list logo
