<mcatanz...@gnome.org> schrieb am Mo., 18. März 2019, 15:17: > Please keep gnome-i18n@gnome.org CCed > > On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti > <arnaud.bona...@gmail.com> wrote: > > Hi Jeremy and Michael, hi release-team, > > > > 2019-03-17 17:01 UTC+01:00, mcatanz...@gnome.org > > <mcatanz...@gnome.org>: > >> I see: > >> > >> > >> > https://gitlab.gnome.org/GNOME/dconf-editor/commits/maintainer-only-3-32/po > >> > >> which seems pretty excessive. You probably wouldn't be very happy if > >> translators starting introducing unexpected changes outside of po/, > >> right? In the same way, the translators would prefer you to not make > >> changes under po/. > > > > That’s my role as a maintainer to ensure that the product that is > > taggued as stable does not look broken. > > > Your role as a maintainer doesn't include unauthorized changes of po files, which aren't approved by the translation teams and get released secretly via a "maintainer only" Git branch. As I already wrote one year ago: Never touch po files, really never! If you don't stop with your willful "fixes" and "improvements", we should consider to remove dconf-editor (and any other software maintained by you) from the Damned Lies pages.
Best Regards, Mario > If translations are breaking the application layout, by translating > > the word “Translators” as something crediting translators on a > > long > > multiline string (the said “translator-credits” string from the > > About > > dialog), it’s my role to not tag a stable release without these > > translations fixed. > > > > If a translation contains a web link to what is currently an > > hypnotherapist website, it’s my role to remove that link before it > > hits the stable release. Even if I didn’t had the time to join the > > translator or its team to fix it in l10n. (Yes, it’s a true story. > > Not > > a big issue, but a real life one.) > > > >> Why is this necessary? They can't maintain their translations if you > >> have your own separate translations that never make it into > >> l10n.gnome.org. > > > > My goal is of course to upstream these changes is l10n, not to > > maintain a out of tree patchset indefinitely. > > > > But this upstreaming takes time: sometimes translators do not answer > > (see > > > https://bugzilla.gnome.org/buglist.cgi?quicksearch=product:l10n%20dconf-editor > > for long-time bugs without answers), sometimes translators take time > > to understand the problem, and I have to tag a stable release by the > > time. > > > > But that should not be a surprise if the last commit before the 3.32 > > dconf-editor release (8d0fa918) is fixing in one translation a problem > > I discovered and temporarily fixed in other po files, that’s part of > > my work with translators on these issues. > > > > As opposed to what Jeremy Bicha says, my current workflow is not > > breaking the translators one; that was not the case with my previous > > attempts (sorry again with that). And it is fixing translations for > > real life users. And that’s the important part of this story. > > > > Regards, > > Arnaud > > > > -- > > Arnaud Bonatti > > ________________________________ > > courriel : arnaud.bona...@gmail.com > > > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n >
_______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
