On Wednesday 11 December 2002 19.32, Tim Hockin wrote: > > This is *exactly* why I'm proposing the use of a structured text > > file that matches the structure of the plugin's "exported" names. > > The *structure* is what you go by; not the actual words. A host > > would not even have to ask the plugin for the english names, but > > just look up the corresponding position in the XML and get the > > name from there instead. > > You've basically described gettext(), which happens to be the > standard way of doing localization in modst code.
Yes, then there is no problem, is there? [...] > I had thought about making reccomendations about this, but decided > there was no need. Plugins don't display anything themselves > (modulo UIs which we haven't even breached, and let's not, yet). > Leave loclaization to the host and the translators. Exactly. //David Olofson - Programmer, Composer, Open Source Advocate .- The Return of Audiality! --------------------------------. | Free/Open Source Audio Engine for use in Games or Studio. | | RT and off-line synth. Scripting. Sample accurate timing. | `---------------------------> http://olofson.net/audiality -' .- M A I A -------------------------------------------------. | The Multimedia Application Integration Architecture | `----------------------------> http://www.linuxdj.com/maia -' --- http://olofson.net --- http://www.reologica.se ---
