path: root/src/lib/elementary/efl_ui_win.c
diff options
authorJean-Philippe Andre <>2017-09-22 15:13:16 +0900
committerJean-Philippe Andre <>2017-09-26 17:58:07 +0900
commit839c4ed395f4aa20c3d8089bad828f2ebdc95a4b (patch)
treee34298f4924fab9755e198b9f87ce2f5ca81f638 /src/lib/elementary/efl_ui_win.c
parent2b7f9b6dfd372af81fd691ac0a0a87b53f8cce34 (diff)
elm: Introduce interface Efl.Ui.Translatable
This will be used to replace the part translation API in Elm.Widget. It should work for both parts and non-parts (ie. the main text of a button, for instance). For now I'm taking the following approach: - All efl_text_set/get strings are untranslatable, i.e. get() returns the visible string, set replaces and can not be translated. - translatable_text_set/get needs to be used to enable automatic translation, which in turns calls efl_text_set to modify the visible string. Thus, translatable applications will have to use efl_ui_translatable_text_set a lot more than efl_text_set, unless they translate strings application-side. Note that some other frameworks take a simpler approach equivalent to calling efl_text_set() with an already translated text. This prevents runtime language changes of the application, unless the application handles them specifically.
Diffstat (limited to '')
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/elementary/efl_ui_win.c b/src/lib/elementary/efl_ui_win.c
index 30d4d3d492..1a94b70c2e 100644
--- a/src/lib/elementary/efl_ui_win.c
+++ b/src/lib/elementary/efl_ui_win.c
@@ -3679,7 +3679,7 @@ _elm_win_translate(void)
3679 Evas_Object *obj; 3679 Evas_Object *obj;
3680 3680
3681 EINA_LIST_FOREACH(_elm_win_list, l, obj) 3681 EINA_LIST_FOREACH(_elm_win_list, l, obj)
3682 elm_widget_translate(obj); 3682 efl_ui_translatable_translation_update(obj);
3683} 3683}
3684 3684
3685void 3685void