Hello Urs, > ... > >> Still needs to be tied into the translation process and means another > >> technology the translators need to master. > > > >Translators would edit the strings , then run 'make www' > > ...
> So that explains something.
> You think LilyPond's website and docs are maintained as HTML files? Not at
> all!
Nope, I never said the doc was written and maintained in 'html' :). You can
follow
the doc link on Guile's web-site, for example, which, as Guix, Guile-Gnome...,
also has its doc written in texinfo:
Guile -> Learn -> Reference Manuals -> Guile-2.0
and choose what ever format you prefer, for example
https://www.gnu.org/software/guile/manual/guile.html
I was talking about the source code of these web sites, and why, imo, this
approach
is a good candidate for a new lily web site. There would be no 'interference'
with
the lily doc and its translations. Guile's doc hasn't change, not even a single
modif, because of it's new web-site :)
David
pgpE5PnmWb5qr.pgp
Description: OpenPGP digital signature
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
