>This standard is necessary for problems exactly as the one you've >experienced in the win32 frontend. These are internal names that need >to be usable in standard encoding mechanisms such as programming
Then I strongly vote for adding an optional Displayname= or something like that to the configuration files. I think it is not wise to identify internal module identifier and screen display name -- these are two distinct concepts. (All the old modules don't have to be changed (except for those with ~) because we can use the identifier if the Displayname is not present.) Especially when you consider that for some modules, people might like to use UTF-8 names. I'd prefer to call a German dictionary "Wörterbuch", instead of having the APIs force me to use the clumsy "Woerterbuch". Greetings, Christian Renz -- [EMAIL PROTECTED] - http://www.web42.com/crenz/ - http://www.web42.com/ "A man who gives in to temptation after five minutes simply does not know what it would have been like an hour later. That is why bad people, in one sense, know very little about badness. They have lived a sheltered life by always giving in." -- C.S. Lewis
