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*<obj>, const char*<part_name>, const char* <string>); to set the text part by making use of I18N support of elementary(using gettext). Pros/Cons: This again depends in C Code, Theme extendibility is lost. Approach 2: Having separate Attibutes to TEXT/TEXTBLOCK part for each of the languages being supported. e.g. text.text_enGB:"<string in english"; text_ko:"<string in korean"; and so on... Pros/Cons: No reusability and makes the block definition bulky and complex. Approach 3: Edje lib can do the translation with gettext package support. TEXT/TEXTBLOCK can have additional attribute pkg_name to locate the gettext package. e.g. text.pkg_name: "edje";// package name in this example is elementary. text.text: "string"; and PO files can be packed as part of EDJ. This approach will have backward compatibility with the existing edc files. Appreciate your valuable comments. Thank You. Regards, Rajeev ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
