[gmpi] Re: 3.19 Localization

On Thu, Sep 30, 2004 at 05:43:02PM +0100, Steve Harris wrote:
> On Thu, Sep 30, 2004 at 09:01:49AM -0700, Tim Hockin wrote:
> > > 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.
> 
> If you have static metadata you dont need to call any translation
> functions.

There are two kinds of metadata - "This plugin has N inputs and M outputs,
with parameters A, B and C" and "This param is named "Frequency".

It seems to me that IF you want static metadata, you want it in one place.
So you have some metadata that says "This plugin has N inputs and M
outputs...".  Adding a parameter is done in one place.  Now you provide
translation files for each language you support.  The plugin and host,
when displaying info about this plugin, can both look up the strings for
the current language in that translation file.

We're saying the same thing, right?

----------------------------------------------------------------------
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: