Localization problem !
-
Hi, I have read few articles about localization, and I have stumble across one big question how can someone edit my localized (dll) file ??? I want to add option (if there is such possibility) for my users to change localization files by themself, but I dont know how to do it? So as far as I know after compiling from resx file generates dll file that can be later used for localization, so there is no way it can be xml file or such so that it can be edited? Any healp? Big thanks!
-
Hi, I have read few articles about localization, and I have stumble across one big question how can someone edit my localized (dll) file ??? I want to add option (if there is such possibility) for my users to change localization files by themself, but I dont know how to do it? So as far as I know after compiling from resx file generates dll file that can be later used for localization, so there is no way it can be xml file or such so that it can be edited? Any healp? Big thanks!
For "amateur" translations - which is probably what you have if you expect the users to do the translation - look at WinRes.exe (part of the SDK). It works on the .resources files as far as I remember - but you can easily making a tool extracting these from the DLLs. The .NET linker can create a DLL from the translated .resources file. Notice you have to be careful getting the name of the embedded resources right, but it's not too hard if you make a sample with VS and see how it names everything. For professionel translation buy a commercial localization tool so you get support for leverage etc. For enterprise level translation, make your own tool, as the commercial solutions simply sucks if you get a high level of text and updates flowing though your localization process. :)
-
For "amateur" translations - which is probably what you have if you expect the users to do the translation - look at WinRes.exe (part of the SDK). It works on the .resources files as far as I remember - but you can easily making a tool extracting these from the DLLs. The .NET linker can create a DLL from the translated .resources file. Notice you have to be careful getting the name of the embedded resources right, but it's not too hard if you make a sample with VS and see how it names everything. For professionel translation buy a commercial localization tool so you get support for leverage etc. For enterprise level translation, make your own tool, as the commercial solutions simply sucks if you get a high level of text and updates flowing though your localization process. :)
-
- Search for WinRes on Google. I know it exist, I never used it. 2) Contact a translation vendor and let them deal with it - you give them the DLL with the English text embedded, they return translated DLL's (in case they are signed you need to work with them how their tool can support this - possibly though delayed signing). 3) This should only be done by enterprises - if you are not working for a company at least 3 software developers in a deticated localization team (NOT localization engineers - the entire localization team will probably be at least 15 people before you have the 3 developers) this is not the option for you. Such a localization team will also be experienced in using third party localization tools and can hence make the judgement on when your translation volume is so high that they no longer can keep up using the standard 3rd party tools. Unfortunately Microsoft made some serious design errors in the localization file format of .NET, but it is still best to follow the standard .NET localization methods instead of inventing your own XML format.
-
- Search for WinRes on Google. I know it exist, I never used it. 2) Contact a translation vendor and let them deal with it - you give them the DLL with the English text embedded, they return translated DLL's (in case they are signed you need to work with them how their tool can support this - possibly though delayed signing). 3) This should only be done by enterprises - if you are not working for a company at least 3 software developers in a deticated localization team (NOT localization engineers - the entire localization team will probably be at least 15 people before you have the 3 developers) this is not the option for you. Such a localization team will also be experienced in using third party localization tools and can hence make the judgement on when your translation volume is so high that they no longer can keep up using the standard 3rd party tools. Unfortunately Microsoft made some serious design errors in the localization file format of .NET, but it is still best to follow the standard .NET localization methods instead of inventing your own XML format.
Well I wanted to create my application so that anyone can edit file, for instance I give application to my friend in France, he takes it and translates it into French without having to play around with WinRes resgen and other things :). Thank you anyway for you`r response.