[gmpi] Re: 3.19 Localization

On Thu, Sep 30, 2004 at 06:00:30PM +0100, Steve Harris wrote:
> > 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.
> 
> You could do that, or you could say "this is the label for port 3 in
> en_GB ..., this is it un ru_RU ..."

We're saying the same thing - at runtime, the host or a shared lib or
something looks at $LANG (or whatever) and decides which string gets
shown.  Right?

That's fine for the UI which really is static, but let's suppose I have a
dialog box, or an About screen - surely you don't intend to mix those
strings with parameter meta data?

The strings should be separate from the GMPI metadata, but beyond that,
we're on the same page, I think.

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