Re: Unauthorized translation changes in dconf-editor
- From: Arnaud Bonatti <arnaud bonatti gmail com>
- To: Alexandre Franke <afranke gnome org>
- Cc: gnome-i18n <gnome-i18n gnome org>, GNOME release team <release-team gnome org>
- Subject: Re: Unauthorized translation changes in dconf-editor
- Date: Tue, 19 Mar 2019 16:39:48 +0100
Hi Alexandre,
2019-03-19 11:06 UTC+01:00, Alexandre Franke <afranke gnome org>:
Sadly whether we translate it or not, it will still be seen as “GNOME
software” (it lives in GNOME/ on gitlab) and his behaviour will hurt
the good reputation of our translation work. If he’s not up to the
task of maintaining that piece of software correctly then he should be
handled in an appropriate way.
Honestly, I though at the opposite that this way to do things would
please both translators and users.
Users, because it brings to them fixes to translations in a fast way
(with some errors –I’m human, and do not write all languages on Earth–
but mostly with improvements), and with less regressions also, as my
patches are “saving” some old strings from not being applied.
Translators, because I was giving back to them my suggestions, so that
they could apply it or dismiss it in the main po/ files, a good way to
improve their translations faster than before, and a real quality
assurance, as I’m reading translations with a completely different
vision of the application and with a complete knowledge on what each
string does and where it goes (in the same logic, I also tried by the
way to help translators here by adding comments in the code).
We’re now beyond the honest mistake
that a beginner would make and this qualifies as hostile since he was
already warned and he created that branch to work around us. Can the
release team give him back his training wheels, please?
In last year debate, what I understood was that editing po/ files in
the main branches (“master” and “gnome-3-xx”) was causing problems, as
translators would not always be made aware of the change; here, what
I’ve done is with a completely different logic, as translators have
the final decision in the end, with every change.
Honestly, I didn’t imagined that translators would see something wrong
with me using this new workflow, and I never thought of it as being
“hostile” or “to work around [translators]”. Of course, I will stop
pushing changed translations to users starting for now (and I hope I
understood correctly the problem this time; are we at least ok on the
words used?).
Regards,
Arnaud
--
Arnaud Bonatti
________________________________
courriel : arnaud bonatti gmail com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]