Re: Improving documentation & I18N

Greetings,

I'll make it unanimous because I prefer the GTK approach as well.

Dan

Adrian E. Feiguin wrote:
> Hi all,
>
> I believe that we should go with the gtk approach. Seems easier to 
> maintaine, besides the gtk guys are pretty smart and I trust they did 
> the right thing.
>
> Saludos,
> <ADRIAN>
> PS: (Smart is a relative concept these days, I'm sure there are a lot 
> of smart people in Wall Street ;-) )
>
>
>
> Victor Mierla wrote:
>> There are different ways for internationalizing your messages :
>>
>> For example GTK-source-code-way : there must file called gtkintl.h in 
>> gtkextra directory which must be included by all *.c files and 
>> translation is made using this macro P_().For example.
>>  P_("The pack direction of the menubar"),
>>
>>
>> Or we could use simple gettext way : #include <libintl.h>
>> #include <locale.h>
>>
>> #define  _(x)  gettext (x)
>> #define P_(x)  x
>> nd translation is made  using this macro P_().For example.
>> P_("/_Edit/Find...")
>>
>> I propose we use GTK way , i think it's more portable.
>> What do you say Dan , do you agree?
>>
>>
>> Best regards
>> Victor
>>
>>
>>
>> --------------------------------------------------
>>
>> Flash.ro - Best free webmail service hosted by Idilis
>> .........................................................
>> Idilis - Internet Provider :: www.idilis.net
>> Inchiriem conexiuni radio si in zone neracordate la coloana - 
>> Broadband Wireless Idilis -
>>
>>
>>
>>
>>   
>


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/