On Tue, Jul 08, 2025 at 12:19:58PM +0000, 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
>
> ```
> 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.
>
>
> Werner
>
>
> PS: LilyPond provides the script `convert-ly`, which does exactly what
> I've suggest above, namely to update syntax changes in different
> LilyPond versions.
>
>
> https://lilypond.org/doc/v2.25/Documentation/usage/updating-files-with-convert_002dly
>
I guess this is the change in 7.0 (2022-11-07):
. systematic addition of classes attribute in HTML elements based on the
Texinfo @-command names. renaming of class attributes to avoid
confusion with @-commands formatting and describe the role in the
document rather than the formatting style.
(from NEWS).
I don't have the appetite to develop or maintain such a script. Hopefully
we are not looking at changing the classes again in any major way.
I had a look at the CSS files referenced by
https://lilypond.org/doc/v2.25/Documentation/usage/updating-files-with-convert_002dly
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 afraid I don't have much
knowledge of what the changes in classes were (I don't think use of HTML
element classes was ever documented anywhere). I don't think there would
be very much in there that would need to change. Hopefully Patrice can
remember if any of these classes (or tags) changed?
