[Nagiosplug-devel] Translations and gettext

[Karl DeBisschop]

Yves wrote:
> Just finished to internationalize (and made bad translation into French) our project
> Perfparse...
> Below, some comments from my experience with i18n on other projects.
> 
> 
>>Message: 2
>>Cc: nagiosplug-devel at lists.sourceforge.net
>>From: Ton Voon <tonvoon at mac.com>
>>Subject: Re: [Nagiosplug-devel] Translations and gettext
>>Date: Fri, 19 Nov 2004 13:16:25 +0000
>>To: Andreas Ericsson <ae at op5.se>
>>
>>
>>On 19 Nov 2004, at 10:18, Andreas Ericsson wrote:
>>
>>
>>>2. It's always a pain to keep such things up to date. Wouldn't it be
>>>wiser to concentrate on code development instead?
>>
>>That's why I would like some volunteers to keep translations up to date
>>- they can be given CVS access for the necessary files only. From my
>>experience with gettext so far, it doesn't get too much in the way of
>>development.
> 
> 
> For the projects I internationalized, I always updated the code for i18n, provide some
> bad translation to French (as an example for contributors) and then let people translate
> what they want.
> This takes a little time at the beginning for the programmer, but when the code is
> internationalized, there is no more work for him.
> 
> With gettext and C programs, there are 3 lines to add in main(), and #include
> <gettext.h> to write at the beginning of all the source files. That takes less than 5
> minutes.
> Then you have to change "string" with _("string") everywhere. Except in a particular
> case (html output), it is very fast, and editors even provide macros for that.

This is already done for the core plugins

-- 
K