[gmpi] Re: 3.19 Localization

On Thu, Sep 30, 2004 at 09:53:52AM +0100, Steve Harris wrote:
> On Wed, Sep 29, 2004 at 09:23:35PM -0700, Tim Hockin wrote:
> > * GMPI plugins must be localizeable.  The host must expose the current
> >   language settings to plugins.
> 
> Shaouldn't that happen automatically though the POSIX i18n stuff?
> Hypothetical platforms that dont support POSIX could fake it up easily,
> its just an environment variable.

That's exactly why I said gettext()

> Some work could be taken off the plugin by letting the host pick a
> metadata file (where one is provided) based on an extension or name
> component. For example metadata-en_GB.txt, assuming the metadata
> syntax chosen doesnt have builtin i18n support. 

That's what I meant by the third req - providing a translation API.  it
could be gettext() or it could be host->translate() or it could be
gmpi_xlate() or whatever.  If you know the plugins 'name' and path, you
can find the strings automatically, so all the plugin needs to do is call
the gmpi specced translator.  Works for images too.

char *skin = gmpi_xlate(this_plugin, "background.jpg");
/* now you have a potentially localized version of the jpeg, if one
 * existed. */

----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: