So it ultimatly boils down to the individual application maintaning its own ditionary. In a way this is better, this gives developers more control over the application, and the behaviour is not unpredictable, which would be the case if the app relies on external 3rd party language converters. That being said, here is how its done.
On Android,
Assuming you use the default Android application development environment and code structure (is there anything other than default? :D ) -
- Copy the res/values/strings.xml bundle to res/values-es/strings.xml (Espanol/ Spannish)
- Replace all the
Spannish text here with the Spannish text as shown. Use Google translate (link below) - Copy the contents of res/drawable bundle to res/drawable-es-rES (Espanol/ Spannish)
- Replace the drawable resource files (your png files) to its any Spannish equivalents.
- Note: If the equivalent of a string or drawable is not found in the language directories, the default values are taken from the res/values and res/drawable folders.
- All references using android:text="@string\englishtext", etc. will display the equivalent Spannish text if the user chooses Spannish as the device language.
- Similarly, all drawable items wil show the Spannish equivalents, if it exists, or display the default drawables.
- Localization almost always gets precedence for a user.
- Use
String locale = context.getResources().getConfiguration().locale.getDisplayName();
to get the localization being used.
- Google translate
- Wiki Language Codes
- Android localization