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. - Steve ---------------------------------------------------------------------- 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: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe