11 Dec
2002
11 Dec
'02
12:47 p.m.
On Wednesday 11 December 2002 17.02, Sebastien Metrot wrote:
This doesn't work most of the time because many
names can have
multiple meanings and vice versa.
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.
Also you'll have to manage
encodings correctly, and most developpers are just not aware of
what an encoding really is.
Then don't try to write a host that supports non-english languages.
Just use what the plugins give you (english) and be happy.
//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 ---