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?
Regards,
Arnaud
--
Arnaud Bonatti
________________________________
courriel : arnaud.bona...@gmail.com
From f1babaa64d97e82eba145d53bd6b5167434e7aac Mon Sep 17 00:00:00 2001
From: Arnaud Bonatti <arnaud.bona...@gmail.com>
Date: Thu, 16 Aug 2018 09:00:00 +0200
Subject: [PATCH] Use Yes/No for Forced range.
---
editor/registry-info.vala | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/editor/registry-info.vala b/editor/registry-info.vala
index 3d5df44..7de6350 100644
--- a/editor/registry-info.vala
+++ b/editor/registry-info.vala
@@ -159,7 +159,7 @@ private class RegistryInfo : Grid, BrowsableView
|| type_code == "x" || type_code == "t") // signed and unsigned 64 bits
{
range_type_is_range = ((RangeType) range_type) == RangeType.RANGE;
- add_row_from_label (_("Forced range"), Key.cool_boolean_text_value (range_type_is_range));
+ add_row_from_label (_("Forced range"), range_type_is_range ? _("Yes") : _("No"));
}
}
--
2.17.1
_______________________________________________
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
