Re: Inactive translations

[Luca Fascione]

Jonas,
Would it makes sense to automatically reset this at every release round?

I'm thinking it should be the translators that certify the liveness of
their work.
So I'm wondering what if when 2.<even>.0 is getting close, all translations
that don't have a commit since 3months (say, or that miss important changes
or new features or whatever similar criterion) are put in a parking space,
where it's easy for translators to unpark them, but otherwise are clearly
marked as not current.

It seems the amount of grief this would cause is minimal (roughly a couple
emails saying "could you re-liven my language?") and it would give a
stronger sense that the available material is current.

Very agreed that English and current is far better than "my language" and
stale. Also agreed that the web version is the most important to have in a
good state

L

On Sun, 22 Jan 2023, 13:58 Jonas Hahnfeld via Discussions on LilyPond
development, <lilypond-devel@gnu.org> wrote:

> On Wed, 2023-01-04 at 14:41 +0100, Jonas Hahnfeld via Discussions on
> LilyPond development wrote:
> >  * endangered: hu (translation of Essay in 2021; last fixes before that
> > in 2017; last real changes in 2016?); pt (added in 2018, translation
> > fixes in 2019, technical fixes in 2020)
> >  * outdated: cs (last update by Pavel in 2012; some passages copied
> > from German manual!), nl (last update by Jan in 2012)
> >
> > Especially the last category is bad and I would like to propose that we
> > delete these translations; I think it is better to have the community
> > use the English version instead of a translation from more than 10
> > years ago. If somebody wants to update them, I guess they are better
> > off starting from scratch based on the English version anyway.
> >
> > For Hungarian and Portuguese, I'm not so sure: On the one hand, they
> > have seen "recent" updates, but the most important "document", that is
> > web being served on lilypond.org, is heavily outdated. Overall, I
> > personally think it would also be better to remove them. If somebody
> > wants to update and maintain them, it would be easy to bring them back
> > from git history.
>
> The removal of these four translations is now in
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1820
>