Re: localized oaf ...

[Maciej Stachowiak <mjs noisehavoc org>]

On 17Jul2001 03:40PM (-0400), Michael Meeks wrote:
> 
> Hi guys,
> 
> 	I was wondering ... as I looked at fixing the bonobo component
> selector, where is / is there any nice code to do the localization of the
> various translated strings that oaf has ?
> 
> 	Are these localized at oaf's end ? - it would seem not sensible to
> me, or are they localized at the client's end ? this seems reasonable, but
> again one would need to possibly fetch several different attributes using
> LC_ALL etc. to actualy get the right translation for a component
> description.
> 
> 	It seems to me we pay a huge penalty shipping all the data across
> the wire - but don't actualy use it to translate component descriptions
> etc.
> 
> 	But I might be wrong ?
> 

If you use this function to look up properties you'll get the
localized version (if any):

const char *
oaf_server_info_prop_lookup (OAF_ServerInfo * server, 
			     const char *prop_name,
                             GSList * i18n_languages);

Nautilus uses this extensively and shows up with translated component
names and descriptions, so you could look there for example code.

Regards,

Maciej