Re: [dconf-editor] String freeze break request
- From: Arnaud Bonatti <arnaud bonatti gmail com>
- To: GNOME i18n <gnome-i18n gnome org>
- Cc: GNOME Release Team <release-team gnome org>, GNOME Documentation Team <gnome-doc-list gnome org>
- Subject: Re: [dconf-editor] String freeze break request
- Date: Fri, 17 Aug 2018 21:42:25 +0200
I pushed the patch with the two strings addition. Thanks everyone for
your fast answers!
2018-08-17 19:54 UTC+02:00, Daniel Mustieles García
<daniel mustieles gmail com>:
2/2 from i18n.
Regards
El jue., 16 ago. 2018 10:28, Claude Paroz <claude 2xlibre net> escribió:
Le 16. 08. 18 à 10:05, Arnaud Bonatti via gnome-i18n a écrit :
Hello everybody!
There’s a string freeze running, but I’ve spotted a mistake of my own
in the dconf-editor module I maintain. There’s a new information about
“forced range,” as the range of a numeral key can be forced or not,
and I’ve used an already existing translation for the “forced or not
forced” (“True” / “False”) info. But, this existing translation was
from a completely different context, and the result looks stupid in
some translations (Chinese where I’ve spotted the bug, but that is
probably not specific).
I’d like to correct that by pushing to new strings, “Yes” and “No,”
that would be even better in English and that would solve the
contextual translations problems. Is that doable?
Fine with me at this stage. i18n approval 1 of 2.
Claude
--
www.2xlibre.net
_______________________________________________
gnome-i18n mailing list
gnome-i18n gnome org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
--
Arnaud Bonatti
________________________________
courriel : arnaud bonatti gmail com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]