On 12/2/05, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
On Fri, 2 Dec 2005 01:37:34 +0900 David Stevenson <[EMAIL PROTECTED]>
babbled:

> On 12/1/05, The Rasterman Carsten Haitzler < [EMAIL PROTECTED]> wrote:
> >
> > On Wed, 30 Nov 2005 00:18:37 +0900 David Stevenson <[EMAIL PROTECTED]>
> > 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" :)

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

Reply via email to