Re: [xine-devel] config regrouping and xine-ui wishes

[Michael R. <mr...@us...>]

Hi Miguel,

> > > Config entries are untranslated. Full stop.
> > > Whenever they are presented to some UI, they are passed through
> > > gettext. This may require an API extension for most cases...
> >
> > I think I misunderstood you. I thought you wanted to call gettext within
> > the entry handling in configfile.c. So you actually want a new API
> > function like xine_tr() which can be called by frontends to translate the
> > enums. (And we should use this for the config entry section headings as
> > well.)
>
> sounds like a good idea, at least for enums.

What about the config section headings? Should we use it for that, too? I 
think this:

xine_tr("audio.device");

will look cleaner than our earlier idea with the virtual config entries.

What about the name for the API function? Anyone against xine_tr()?
(xine_translate() seems too long for something that basic, xine_i18n() might 
be an alternative, Qt uses tr() as well)

> do we need a new a api function or would it work if frontend called
> gettext directly?
> i don't know how gettext works, but it should be able to automatically
> merge MSGID catalogs as shared libraries are loaded, right?

I would not rely on that. When xine-lib or the frontend have gettext 
statically linked, this might not work (but I don't know that for sure). And 
an API function would be much more convenient for frontends that decide not 
to use gettext.

Michael

-- 
/* Thanks to Rob `CmdrTaco' Malda for not influencing this code in any
 * way.
 */
	2.4.3 linux/net/core/netfilter.c