Rockbox mail archive
Subject: language and spearch for plugins
From: Daniel Stenberg (daniel_at_haxx.se)
On Thu, 10 Jun 2004, BlueChip wrote:
> 1. Make lang.h readily available to the plugins, probably via plugin.h
> You may need to add a similar version control system as the plugins
> Personally I wouldn't bother, as if you DO change the lang file(s) you
> risk killing all .voice files that exist.
For language strings? So the single language file should contain strings for
all current and thinkable and future plugins? Won't that make it an unusable
system very soon? I think it would. It sounds like a bad idea. I would rather
have a system that better make the language strings for a particular plugin
more separate and independent. I want Rockbox to be able to work with an
unlimited number of plugins, each with their own set of language strings.
For the talking? If so, we would make a certain plugin-API version require a
certain voice-file version. I don't like this idea either. I would rather have
the plugin API offer some kind of talk function that translates the ID used by
a plugin to the ID that might be used internally, as then that function could
be voice-file version aware etc.
I haven't figured out the details of any of these points, and that's why I ask
for help on ideas on how this is done the best way!
Daniel Stenberg -- http://rockbox.haxx.se/ -- http://daniel.haxx.se/
Page was last modified "Jan 10 2012" The Rockbox Crew