On Fri, 18 Mar 2011 19:57:16 +0530 Rajeev Ranjan said:
ok. right now.. approach 1 is what is done because po's and text comes FROM the
app. they define label contents etc. etc.
approach 2 is a bit much... but approach 3 doesnt solve a problem.
i'm a designer. i design an edje and ADD an extra b
Cedric BAIL, il 18/03/2011 16:12, ha scritto:
> Now what is my current idea. It's easy : implement gettext like
> interface in eet. Reason, not only edje will benefit from this
> capability. For example you could add translation support to eyelight
> easily if it was done at eet level.
maybe not
Em 18-03-2011 15:12, Cedric BAIL escreveu:
> In fact, Edje file format already provide the possibility to do so.
> Look inside edje/src/lib/edje_util.c in both functions edje_string_get
> and edje_string_id_get. This is where this should be done imho. And
> edje_cc parser should be extended by beei
Hi,
On Fri, Mar 18, 2011 at 3:27 PM, Rajeev Ranjan wrote:
> TEXT/TEXTBLOCK supports setting a string directly in edc. So how to
> internationalize this string?
I will first point you to my old proposal that I didn't get time nor
urgency to do :
http://lists.enlightenment.fr/enlightenment-devel
Hi,
TEXT/TEXTBLOCK supports setting a string directly in edc. So how to
internationalize this string?
We thought of few approaches. I am listing down them here.
Approach 1:
Widgets/Applications based on elementary can use API
edje_object_part_text_set(Evas_Object*, const char*,
