Localization Project
-
When the default assembly(xxxx.resx) is created in a localized project, how does one extract the file to send out for translation and how do you import it back into the project after the translation?
Hi, I'm not absolut sure, but if you use .NET2.0 there should be an editor where you can edit the ressource file's and the GUI. But I havent worked with it yet (just having a quick look). I wrote my own ressource file parser that creates an excel file wich I can send to our customers. Actually i cant send this parser to you because its company restricted (sorry) and offcourse a bit buggy (lol). But its not that hard to do on your own. You simply need to watch out for Attributes that ends with ".Text". I saved the control text along with the control name to the excel file so that I am able to write the modified excel table back to the ressource. Thats all... a simple recompile and the software is localized (of course you need to check the GUI *hehe*). Good luck, Snow
-
When the default assembly(xxxx.resx) is created in a localized project, how does one extract the file to send out for translation and how do you import it back into the project after the translation?
If you are using professionel translation just send the compiled EXE file, and you should get satallite DLL's back. Can't say it for sure though as we wrote our own translation tools (the commercial available solutions sucked so big time when you ran them at enterprise level), but I would be surprised if they can't handle it. Talk to a few translation vendors to find out what they support. The editing feature built into Visusal Studio is just for small hobby projects where you manually maintain a language or two - it can't be used for anything serious. But if you only need a language or two translated by someone you know then send them the VS project and let them use VS to translate.