Jan-Uwe Finck <[EMAIL PROTECTED]> writes:
> after looking a little bit in the source I found a file with french
> words in it, so I wonder if it is of any use if I make a german
> translation ?
> And how would that be applied afterwards ? (Couldn't find any way so
> far..)
Though I'm no internationalization expert, it's my impression that
gettext is the preferred solution these days. On the C side at least,
you just use some_func(_("This is a message")), and then you create
translation files for all the phrases that are arguments to "_" calls.
This makes it trivial to do translations, even without recompiling,
and it supports all the standard LOCALE stuff.
Right now, we use the older and more primitive method of defining the
strings within the preprocessor and using tokens in the source.
Something like:
#define XACC_HELP_ABOUT_STR "About GnuCash..."
set_menu_item_title(help_menu, about_item, XACC_HELP_ABOUT_STR);
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
