From: David S. <dav...@gm...> - 2005-11-29 15:18:44
|
Gidday all, I have posted a couple of blog entries about 3rd party module internationalization over at edevelop. 3rd party Module Internationalization - Overview http://edevelop.org/node/1853 3rd party Module Internationalization - Proof of concept http://edevelop.org/node/1860 My autotools knowledge is rudimentary, but hopefully this can be useful for other 3rd party module developers wanting to internationalize :-) If anyone has suggestions for improvement please let me know. Regards! David |
From: Carsten H. (T. R. <ra...@ra...> - 2005-12-01 07:17:06
|
On Wed, 30 Nov 2005 00:18:37 +0900 David Stevenson <dav...@gm...> babbled: > Gidday all, > > I have posted a couple of blog entries about 3rd party module > internationalization over at edevelop. > > 3rd party Module Internationalization - Overview > http://edevelop.org/node/1853 > 3rd party Module Internationalization - Proof of concept > http://edevelop.org/node/1860 > > My autotools knowledge is rudimentary, but hopefully this can be useful for > other 3rd party module developers wanting to internationalize :-) > If anyone has suggestions for improvement please let me know. very nice write up man! ganbatte! -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 Tokyo, Japan (東京 日本) |
From: David S. <dav...@gm...> - 2005-12-01 16:37:50
|
On 12/1/05, The Rasterman Carsten Haitzler <ra...@ra...> wrote: > > On Wed, 30 Nov 2005 00:18:37 +0900 David Stevenson <dav...@gm...= > > babbled: > > > Gidday all, > > > > I have posted a couple of blog entries about 3rd party module > > internationalization over at edevelop. > > > > 3rd party Module Internationalization - Overview > > http://edevelop.org/node/1853 > > 3rd party Module Internationalization - Proof of concept > > http://edevelop.org/node/1860 > > > > My autotools knowledge is rudimentary, but hopefully this can be useful > for > > other 3rd party module developers wanting to internationalize :-) > > If anyone has suggestions for improvement please let me know. > > very nice write up man! ganbatte! minna ganbaro-! Actually I had an idea for an improvement to this Using the d_ macro in e_intl.h involves writing d_("some string to translate", "") which is obviously a pita to do for every string so instead I am thinking 3rd party modules, as they are built independently from e, could simply redefine the _ macro in their e_mod_main.h: #ifdef _ #undef _ #endif _ #define _str dgettext(PACKAGE, str) So then strings in 3rd party modules can be wrapped as usual with just _("some string to translate") ...which should be less of a hassle :) David |
From: Carsten H. (T. R. <ra...@ra...> - 2005-12-02 00:21:24
|
On Fri, 2 Dec 2005 01:37:34 +0900 David Stevenson <dav...@gm...> babbled: > On 12/1/05, The Rasterman Carsten Haitzler <ra...@ra...> wrote: > > > > On Wed, 30 Nov 2005 00:18:37 +0900 David Stevenson <dav...@gm...> > > babbled: > > > > > Gidday all, > > > > > > I have posted a couple of blog entries about 3rd party module > > > internationalization over at edevelop. > > > > > > 3rd party Module Internationalization - Overview > > > http://edevelop.org/node/1853 > > > 3rd party Module Internationalization - Proof of concept > > > http://edevelop.org/node/1860 > > > > > > My autotools knowledge is rudimentary, but hopefully this can be useful > > for > > > other 3rd party module developers wanting to internationalize :-) > > > If anyone has suggestions for improvement please let me know. > > > > very nice write up man! ganbatte! > > > > minna ganbaro-! > > Actually I had an idea for an improvement to this > Using the d_ macro in e_intl.h involves writing > d_("some string to translate", "") > which is obviously a pita to do for every string so instead I am thinking > 3rd party modules, as they are built independently from e, could simply > redefine the _ macro in their e_mod_main.h: > > #ifdef _ > #undef _ > #endif _ > #define _str dgettext(PACKAGE, str) > > So then strings in 3rd party modules can be wrapped as usual with just > _("some string to translate") > > ...which should be less of a hassle :) yes.... and no... yes. good idea. handy. no - because... a 3rd party module COULD recycle already translated strings like "OK" "Cancel" etc. known to be translated and thus the module will get partly translated "for free" :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 Tokyo, Japan (東京 日本) |
From: David S. <dav...@gm...> - 2005-12-02 13:58:34
|
On 12/2/05, The Rasterman Carsten Haitzler <ra...@ra...> wrote: > > On Fri, 2 Dec 2005 01:37:34 +0900 David Stevenson <dav...@gm...> > babbled: > > > On 12/1/05, The Rasterman Carsten Haitzler <ra...@ra...> wrote= : > > > > > > On Wed, 30 Nov 2005 00:18:37 +0900 David Stevenson < > dav...@gm...> > > > babbled: > > > > > > > Gidday all, > > > > > > > > I have posted a couple of blog entries about 3rd party module > > > > internationalization over at edevelop. > > > > > > > > 3rd party Module Internationalization - Overview > > > > http://edevelop.org/node/1853 > > > > 3rd party Module Internationalization - Proof of concept > > > > http://edevelop.org/node/1860 > > > > > > > > My autotools knowledge is rudimentary, but hopefully this can be > useful > > > for > > > > other 3rd party module developers wanting to internationalize :-) > > > > If anyone has suggestions for improvement please let me know. > > > > > > very nice write up man! ganbatte! > > > > > > > > minna ganbaro-! > > > > Actually I had an idea for an improvement to this > > Using the d_ macro in e_intl.h involves writing > > d_("some string to translate", "") > > which is obviously a pita to do for every string so instead I am > thinking > > 3rd party modules, as they are built independently from e, could simply > > redefine the _ macro in their e_mod_main.h: > > > > #ifdef _ > > #undef _ > > #endif _ > > #define _str dgettext(PACKAGE, str) > > > > So then strings in 3rd party modules can be wrapped as usual with just > > _("some string to translate") > > > > ...which should be less of a hassle :) > > yes.... and no... > > yes. good idea. handy. no - because... a 3rd party module COULD recycle > already > translated strings like "OK" "Cancel" etc. known to be translated and thu= s > the > module will get partly translated "for free" :) True, I didn't think of that... you are very much in "string share" mode! Anyway I guess module writers can just define their own macros instead #define D_(str) dgettext(PACKAGE, str) or something similar to achieve the same level of laziness. David |