Okay guys, there's a lot of demand for this rom and for language packs but not yet a lot of people who know how to make the packs. Whilst I set up the crowdin translation project I can not create or maintain language packs.
So, here's a summary of the instructions required to create a language pack for MIUI (indeed for any app/rom). You need a collection of tools and a little patience but the process isn't too difficult so do give it a go.
Also note that this summary includes generalisations for brevity. These instructions assume you have a deodexed rom.
For the purposes of this post language information is stored in XML strings in files on the Android system. In the case of MIUI and these instructions we will be dealing with .apk files (applications).
Within the apk files is a resources directory (/res) and within this are various values directories, there is a default values directory (/res/values) and alternative language values directories (e.g. /res/values-DE and /res/values-IT).
If the rom is set to use it's default language it will read values from /res/values although these may NOT be in English. In MIUI, all of the common Android ASOP values in /res/values are English but the (additional) custom MIUI strings are in Simplified Chinese.
If you select a different language in the ROM than the default then the appropriate values directory will be searched. If a suitable string that matches your language selection is found in the alternative /res/values-xx directory then that string will be used instead. If an alternative does not exist then the default will be used.
In this example, if the language is set to the default the word "Stop" will be used, if it is set to German the word "Halt" will be substituted in, likewise "Basta" for Italian.
So, to add languages to a rom (or app) or to make an app multi-lingual you need to either change the default strings in /res/values/strings.xml to the ones you want to use or, and this is the preferable approach, add a /res/values-xx/strings.xml with the translations you want. The first approach will work (changing the default strings) but is not recommended because the Android Open Source Project and Android development in general, defaults to English. It's best to use the built in language substitution capabilities of Android rather than to work around them. Indeed, if the MIUI devs actually added their strings in English to /res/values/strings.xml and the Chinese equivalents in the appropriate directory this rom would already be in English!
To add a translation file (strings.xml) to an apk you need to:
decode the apk
create a language directory
add the translation files
recompile the strings
add the new strings to the apk
Which all sounds a little daunting but it's really quite straight-forward, rewarding when you see the result and a good way to understand how parts of Android work. Here's how you can do it.
1. decode the apk
You will need the excellent apktool from brut.all which you can get from the link below. apktool is relatively easy to use but includes some little tricks so you will need to read the wiki and thread about it.
Do NOT just post problems about apktool if you can't get it to work. The tool DOES work so if it's not decoding (or encoding) your apps correctly then you're probably doing something wrong. If you start with this understand BEFORE you ask for support you'll get a lot more help...
Please make sure you run the following command to include the MIUI framework in apktool. You only need to do this once for each framework. If apktool works with one rom and not the next then (re)install the framework for that rom.
apktool if framework-res.apk
Where framework-res.apk is the one from the rom you are working with. Make sure apktool can find (the correct) framework-res.apk before you run this command.
This thread is not for apktool support.
Now, before you proceed, decode a simple app from MIUI (such as updater.apk) using apktool, do not make ANY changes, then re-encode it using apktool. For example:
apktool d Updater.apk ./decoded/
apktool b ./decoded/ new_updater.apk
Use the -v (verbose) flag in apktool if you have problems and need to diagnose further.
Remember, Android uses a case-sensitive file system, make sure your capitalisation is correct.
Typically you will not be able to install this apk because it is not signed so if you want to test the process further you can now just try step 5 below using the two apks you have.
2. create a language directory
Assuming you can decode/encode now, this is the easy bit. For your decoded app, navigate to the directory it was decoded in, then to the /res/ directory and simply create an empty directory for your language (e.g. /values-FR/) - use international naming conventions.
3. add the translation files
Again, not too difficult this. Download the appropriate language file for your apk from the crowdin project linked below and, using the same structure as exists in /res/values/strings.xml create a new file called strings.xml in your alternative language directory (e.g. /res/values-ES/strings.xml).
The news strings.xml may contain as many or as few translations as you like. Remember, if a translation does not exist the default value from /res/values/strings.xml will be used.
The xml formatting and tag names need to match exactly with the default strings.xml in /res/values although the translated file does NOT need to be complete.
It is worth remembering here that unless your source apk is already translated to English then some of the default values in /res/values/strings.xml will still be in Chinese, it would pay to check these.
4. recompile the strings
Now, if you've done everything carefully and correctly this step is really easy, all you need to do is recompile the apk with apktool using the b (for Build) switch.
apktool b ./<decoded_apk_dir>/ <output_apk_name>.apk
If this throws errors or does not work then use the -v switch to turn on verbose mode and diagnose your problem. If you did the test in step #1 and it worked then any problem at this step is likely related to your news strings.xml. Back out the changes one by one until you have found the problem and try again.
If you simply can't get it to compile with your changes then try just making a single change to the default strings.xml file in /res/values and see if that works for you.
Do NOT sign the apk!
5. add the new strings to the apk
Easy. Open your new apk with a zip program (like 7Zip for Windows) and copy out the resources.arsc file in the root directory of the apk. Now take that file and copy it into the source apk from the rom overwriting the existing one. This process replaces the strings but keeps the integrity of the signatures on the files.
You can now push the modified file to your phone, replacing the stock one, reboot and you're translated. Push the file using "adb push" or copy it into place using a root file manager, do not "install" the new apk. Make sure you put it in the correct place (replace the original) and reboot.
This process will help you add languages to any app including those in the MIUI rom. Because it's a rom the strings are contained in many different apps as well as framework-res.apk. To completely translate the rom you will need to edit every apk that has strings in it.
You will need to do this every time an apk in the rom changes. If a new version is released and say launcher2.apk is changed but updater.apk is not, then you can retain your updater.apk but you'll need to re-edit your launcher2.apk.
When an app changes the default strings.xml may also change. In this case you will need to make corresponding changes to your translations.
Good luck and if you get really stuck there's lots of people in this that have achieved success and may be willing to help!
Originally Posted by kaobiore
HOW TO SPEED-UP THE TRANSLATION-PROCESS:
I've created a simple application (java-based) which tries to merge orginal-froyo-translation (taken from the official repository) into the miui-value-files. (only strings.xml are currently supported).
1) Extract the Translator.tar.gz file (windows-users use winrar or whatever) - a directory named "Tanslator" will be created.
2) Extract the strings.xml file from the miui-package you want to translate.
This can be done with the apk-tool: apktool -d Contact.apk Contact_decoded
Copy the "res/values/strings.xml" to the created "Translator"-direcory. Open that folder and rename (the previous copied) strings.xml to "untranslated.xml".
3) Copy the strings.xml from the official froyo-sources for the package and the language you want to "merge" to the "Translator"-directory and rename the string.xml-file to "translation-file-from-froyo-repo.xml".
4) Run the program. Open a command-prompt/console. Change directory into the "Translator"-Directory and run: java Translator untranslated.xml translation-file-from-froyo-repo.xml
This will generatre a file named "translated.xml"
For some safety reasons not all string which match "by key" are merged. (Stuff wich contains characters like '<' or '%'). You probably see some warnings printed in console (with the key) that needs to be translated manually.
If you want to override this "safety-featiure". Run the app with: java Translator untranslated.xml translation-file-from-froyo-repo.xml psycho
(psycho at the end)
I ran the language file you posted above through Google Translate so we can get a better idea how the text should read... (For the people like me that don't understand Chinese )
<string name="breathing_light_color_title"> trackball color </ string>
<string name="breathing_light_color_summary"> received a new notification, tracking the ball indicator color </ string>
<string name="breathing_light_freq_title"> trackball flicker frequency </ string>
<string name="breathing_light_freq_summary"> trackball pause time between two flashes </ string>
<string name="trackball_wake_title"> trackball light up the screen </ string>
<string name="battery_settings"> power settings </ string>
<string name="battery_settings_title"> power </ string>
<string name="battery_indicator_style"> power status bar style </ string>
<string name="battery_low_level"> low battery warning value </ string>
<string name="battery_saving_rules_title"> Automatic power rules </ string>
<string name="battery_saving_rules_summary"> alert when the power is lower than the value of the operation will be applied when the </ string>
<string name="battery_auto_saving_category_general"> the page the next time all the changes will take effect when entering a low-power </ string>
<string name="battery_auto_saving"> value into the low battery warning when the automatic power saving </ string>
<string name="battery_setting_quick_entry"> power to set Quick Entry </ string>
<string name="battery_setting_quick_entry_summary"> when the low battery, the drop-down box in the status bar display the prompt, and click to enter the current settings page </ string>
<string name="battery_auto_saving_category_rule"> power rule </ string>
<string name="battery_auto_saving_rule_brightness"> reduce the screen brightness </ string>
<string name="battery_auto_saving_rule_brightness_summary"> brightness to a minimum, you can significantly reduce battery consumption </ string>
<string name="battery_auto_saving_rule_background_data"> disable the background </ string>
<string name="battery_auto_saving_rule_background_data_summary"> save power at the same time and save network traffic costs </ string>
<string name="battery_auto_saving_rule_auto_sync"> disable automatic sync </ string>
<string name="battery_auto_saving_rule_auto_sync_summary"> close contacts, messages and other account synchronization </ string>
<string name="battery_auto_saving_rule_apn"> disable the mobile network </ string>
<string name="battery_auto_saving_rule_apn_summary"> off GPRS, 3G and other data connections </ string>
<string name="battery_auto_saving_rule_wifi"> disable WiFi wireless network </ string>
<string name="battery_auto_saving_rule_wifi_summary"> can significantly reduce battery consumption </ string>
<string name="battery_auto_saving_rule_bluetooth"> disable Bluetooth </ string>
<string name="battery_auto_saving_rule_bluetooth_summary"> can significantly reduce battery consumption </ string>
<string name="battery_auto_saving_rule_gps"> disable the GPS satellite positioning </ string>
<string name="battery_auto_saving_rule_gps_summary"> prevent background programs using the GPS, power consumption </ string>
<string name="battery_auto_saving_rule_vibrate"> disable the vibration </ string>
<string name="battery_auto_saving_rule_vibrate_summary"> shock in general consumes little power, but in a time of low power consumption is to save a little bit </ string>
<string name="battery_auto_saving_rule_haptic"> disable tactile feedback </ string>
<string name="battery_auto_saving_rule_haptic_summary"> principle above </ string>
<string name="battery_auto_saving_rule_wallpaper"> disable dynamic wallpaper </ string>
<string name="battery_auto_saving_rule_wallpaper_summary"> wallpapers will consume a lot of power but also slow down the system speed </ string>
<string name="battery_auto_saving_rule_screen_time_out"> reduce screen timeout </ string>
<string name="battery_auto_saving_rule_screen_time_out_summary"> timeout to a minimum, you can reduce the battery consumption to some extent </ string>
<string name="battery_auto_saving_rule_cpu"> reduce the CPU frequency </ string>
<string name="battery_auto_saving_rule_cpu_summary"> can reduce the "cottage" lock screen when the program is produced by CPU power consumption </ string>
<string name="battery_auto_saving_category_practise"> want more power? </ string>
<string name="battery_auto_saving_practise"> saving tips </ string>
<string name="battery_auto_saving_practise_summary"> 1 usually minimize the program running in the background \ n2 unless the bright light, usually no need to use the highest brightness \ n3 sleep can be considered to set flight mode </ string>
<string name="battery_auto_saving_practise_more"> More energy saving tips to the forums> </ string>
<string name="sd_ext_memory"> A2SD </ string>
<string name="usage_type_power"> power consumption </ string>
<string name="current_ime"> the current input method </ string>
<string name="experimental_settings"> developer-specific settings, the average user to use at your own risk </ string>
<string name="experimental_category_control_title"> system control </ string>
<string name="overscroll_mode_title"> elastic default list style </ string>
<string name="menu_style_title"> menu style </ string>
<string name="experimental_category_launcher_title"> Desktop </ string>
<string name="app_icon_background_title"> enable the icon background </ string>
I'm going to work a bit on refining the language tonight.
Going to work backwards.
1) Uploading this language file in place of the Chinese language file.
2) Load up the ROM.
3) Start browsing the menus and figure out how they should read and make the text more accurate to English.
4) Make the changes needed to the language file.
Device: EVO 4G
Recovery Image: Stock
Firmware version: 2.2
Memory: 8GB Class 2 SDHC
if you've not heard about this rom yet then check out this excellent thread started by dai323 who deserves credit for bring it to our attention.
This is an excellent rom if for no other reason than it introduces the first non-cyanogenmod/carrier/manufacturer framework overhaul of android 2.2, and boy what an overhaul. It's hard to ignore the conspiracy theory that this includes leaked elements of gingerbread... The next android. Don't ask me, i have no idea...
de-odexed | themeable | ready for translation
i will pull this at the request of the devs, pm me if you wish.
this is for advanced users only.
this is a no questions rom, you are not allowed to ask questions that you could work the answers out for yourself. Don't dare.
this is a no complaints rom, you are not allowed to complain if it does not work, breaks your phone or has sex with your sister.
please contribute to the enhancement of this rom in a constructive fashion, see the next post.
if you agree to all of the above then you may download the rom by clicking on the appropriate answer below.
Despite introducing many useful features and overall great performance and enhancements,Android 4.4 KitKat … more
01 Sep 2014
By Tomek Kondrat
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?