-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the localeManager wiki!
LocaleManager is a practical tool to manage resources files of different locales for Java and .NET. This executable that includes the translate function can be found at localemanager/downloads.
The Detailed How to Steps can be found in http://nextdoorcoder.blogspot.com/2009/03/how-to-use-localemanager.html.
A problem I have been facing recently during software development with localization support is that the en_US base locale files change from time to time as new strings are added to codes and it is hard to keep the files for other locales in sync. I couldn't find any simple and free tool like this on the web so I decided to develop it by myself.
This app allows a user to select a base locale and any other locale or locales to work on. Then it displays the name and value of resources in a table. Users can keep track of which entries need to be translated or simply work on this table to fill all the blanks. The changes will be saved with UTF8 encoding.
It supports two types for resource files: .properties files for Java or Flex .resx files for .Net The assumptions are that users follow the common practices for locale folders: use a separate folder for each locale. So they normally look like: locale- --- en_US - resource files in English --- de - resource files in German --- fr - resource files in French
It is a C# implementation. Here are the sources for the initial version without the translate function. I didn't open source the part with the Translate API because in theory, everybody that wants to use this tool should request their own Bing Translate API developer app ID from Microsoft and then use that ID instead. It will be quite troublesome to do that unless they already have an ID. The source has my own app ID embedded so I don't want to share it. But you can use it to do some automatic translation as long as the amount is not huge. Otherwise, I may have to disable my app ID.
For .Net Developers, you can refer to my article about ResourceBundle to see how it is possible to organize resource files this way for .Net applications including WPF applications.