>> 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, reporting conversion problems that have to be
>> resolved manually? There could also be an option `--compatible` to
>> allow the CSS file work for both an older and a newer `texi2any`
>> version.
>
> I do not think that it is worth it, for two reasons. First, if I
> recall well, it is not a mere change of classes, but a redesign of
> how classes are associated to @-commands and associated HTML
> elements, such that there is (probably) no obvious mapping from the
> previous classes to the new classes or for some elements only.
OK.
> The second reason is that it requires doing or using a CSS parser,
> which would be a big investment.
I don't think so. LilyPond's `convert-ly` script simply uses regular
expressions, and it works OK. For everything more complicated it says
"I can't convert this, please do it manually".
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?
> So I think that a manual rewrite is the way to go.
Sigh.
> Hopefully, the CSS classes should not change much after 7.0, although
> the HTML elements could change (and have changed).
>
> Looking at this file, it seems to me that these are already the new
> classe names used?
Maybe partially – I guess the transition to new class names started
even before version 7.0 – but definitely not all. For example, we
currently have `pre.menu-comment` in `lilypond-manuals.css` for
Texinfo 6.8, which must be changed to `pre.menu-comment-preformatted`
for Texinfo 7.2.
Werner
