>> Maybe you can provide a list of the most important CSS changes, or
>> maybe add a section that describes how to do the transition to
>> Texinfo 7.0 and newer?
>
> Here is what is in tta/TODO (which is more notes than TODO). We
> have not formally described that in the Texinfo manual because we
On Wed, Jul 09, 2025 at 06:36:08AM +, Werner LEMBERG wrote:
> Maybe you can provide a list of the most important CSS changes, or
> maybe add a section that describes how to do the transition to Texinfo
> 7.0 and newer?
Here is what is in tta/TODO (which is more notes than TODO). We have
not f
>> 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
>> ``
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
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
