Re: [evolution-data-server] GSettings key description typo correction

2018-02-26 11:26 GMT+01:00 Milan Crha <[email protected]>:
>         Hello,
> I committed a change for bug [793728] last week, where the reporter
> claims a typo in a description of one of the GSettings key description.
> I've been warned that I've been supposed to ask for a permission to do
> the change at this late stage of the release cycle, but I hope it's
> understandable to have the typo fixed, instead of giving users false
> and/or confusing information.
>
> I'm sending this email as a late heads-up.
>
> I'm not sure how to proceed in the future. I know that the rules are
> important and I believe I do my best to support translators work and
> not waste their time. I also try to do my best for the users, but I
> also do mistakes and typos like this, where the need for the
> translators and the need for accurate information given to the users
> intersects and causes trouble (and some paperwork overhead) now. I do
> not know, would it make sense to just correct typos in such late time
> and just give a heads up? After all, the translation in the sources is
> used by the users too. I know I should not touch translator's files,
> but there's an option to correct the typo there as well, thus such
> changes might not cause 'fuzzy' translations (okay, this particular
> change is easy, having other kind of typos, which may eventually change
> meaning of the text, is definitely better to be dealt by the
> translators, not by the coders). It's understandable that most of the
> translators begin translation when the string-freeze period begins,
> while they find such typos or issues in the translations only after the
> string should not be changed, but it looks odd to have the default
> translation wrong and wait for the next release to have it corrected.
>
> I do not know, it's hard to make everyone happy, even when we are on
> the same side, trying to provide as best user experience as possible.
>

Hi Milan,

I don’t quite understand your concerns. I’m sure you would get timely
approvals for a string freeze break. We don’t want confused users as
well.

Best regards,

-- 
Piotr Drąg
https://piotrdrag.fedorapeople.org
_______________________________________________
gnome-i18n mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-i18n