I will probably define a function like '_p()' that is used in the code
instead of '_()' to do all the translation of annotations etc. You can
then either use the supplied internal function of p.mapper or map it to
the gettext _() function like
function _p($string)
{
return _($string);
}
I hope this should tackle all expectations, the ones who want to use the
gettext native function and thenones thatw ant to stay with the approach
of p.mapper. I defined the function by my own bacuse not everybody is
willing to dive into the setting up of gettext.
armin
Alessandro Pasotti wrote:
> Il 16:20, luned? 23 gennaio 2006, Silke Reimer ha scritto:
>> Hi Armin and all the other p.mapper users,
>>
>> I18N:
>> - full support for gettext instead of the p.mapper internal way to
>> define text strings.
>>
>
> This would be great!
>
> I really hope Armin will accept this contribution.
>
> I use gettext for all my multilanguage projects and I also will need a
> gettext
> patch for pmapper integration.
>
>
> Many thanks.
>
