Le Monday, 6 Jan 2003, à 09:54 US/Central, Rob Cozens a écrit :
The first of the described appoaches is perfectly suitable for your purpose. My Polylexis is intended to be user modifiable: this means that the user will be able to add a new bases of up to 9 languages of his choice. In my case the interface translation is not crucial since the program already comes with half a dozen widely spread languages, but changing/adding interface language is not a different problem. All you have to do is replace all the "blablabla" int the script by <item x of dialogPhrases> were dialogPhrases is a global containin the line corresponding to the chosen language.As for me I've being using in my HyperCard stacks three different ways of dealing with such a problem:Hi Manuel,
My problem with these approaches (or the Profile Manager) is, AFAIK, they can only support languages that are preprogrammed in the application. OenoLog and future applications I produce with RunRev are designed to be end-user translatable into any single-byte character language.
--
Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.com/who.htm
The present version of Polylexis permits user friendly changes, additions and suppressions in the existing contents base, easy suppression and creation of bases; but is not yet very fruser friendly for creating a new big bases, or dealing with the interfacial base.
See my next mail for some information about the differences between the languages your program could support.
Regards
Manuel
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
