> [...] I can't help the impression that we have, for several
> languages, people who feel responsible for maintaining the
> translations but are unaware that many translations are severely
> outdated and not really all that useful any more for working with
> the current version of LilyPond: partly because they describe things
> that don't even work in the described manner any more, partly
> because the English documentation has seen a lot of improvements
> making things much clearer.
I wonder what's the best way to update outdated documentation.
Reading the whole documentation and checking the translation is
probably quite hard and needs a lot of time. Would it be better
instead to use a git repository viewer, walking over the English
documentation commits and translating them commit by commit? Or do
you recommend to check the differences between development releases?
Werner
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
