Xlates and internationalization

JohnL

While we're on the subject of Xlates, I have another question I'm hoping someone can help me with. I'm wondering how exactly internationalization is supposed to occur with custom modules, and if it is possible to translate to a new language w/out having builder. As I understand it, here is how I think the internationalization process works:1.Create module and XDB. Export XDB to .txt file. 2.Translate .txt file. Reimport .txt file to XDB (using builder).The confusing thing to me in this situation is that your original XDB has a name implying the original language, but now has Xlates of a different language - so the name might be MyModuleUSA, but the text in it is no longer in English. (Maybe I'm missing some other crucial step?)The other concern I have with this method is that it's all well and good if you are responsible for the translation. But what if you just want to provide a mechanism for your users to translate the XDB if they want. You can provide them with a .txt file, but they would have to open builder in order to import the translations. This is obviously not desirable. I'm thinking maybe there is a way at start up to look for new .txt files of the MyModuleXXX.txt syntax in the module's ospace dir., and if so, import that .txt file into the XDB. Or maybe (even better) create a new XDB representing the new language, and point the module to use that XDB?I would be very interested to hear how other users have tackled the internationalization issues. Thanks for all your help & insight. Dawn Lambeth