MULTI MIUI Multi Lang 2.10.19 [ICS & JB]


Status
Not open for further replies.

ingbrzy

Xiaomi.eu Project Leader
Staff member
Feb 11, 2012
11,594
322
Hello all,

Download and flash our current English Only ROM here http://miuiandroid.com/community/threads/2-10-19.18540/ then flash the chosen language pack on top of it. (DO NOT WIPE)

Translators: http://miui.connortumbleson.com/translators/ Please use this website. I will use it to post daily XML changes and remind translators of any problems. Please bookmark this.

DO NOT WIPE YOUR SYSTEM. FLASH ON TOP OF 2.10.19. WIPE DALVIK

Give kudos to your translators. This is a huge group effort and continues to grow bigger.

Languages included:
Languages to be Included:
  • Romanian (epruv)
  • Swedish (Bestonius)
  • Norwegian (datagutt)
MD5 Sums:
Code:
d694df9ace784e7334825aefcaabf882  miuiandroid_lang_aries-2.10.19.zip
2420ba99cf3d31a70a92d8cef3348aec  miuiandroid_lang_crespo-2.10.19.zip
3780fa97143b64e5263b266a84bc3d3a  miuiandroid_lang_edison-2.10.19.zip
bfc0dbcb1d119e5eaddd3fc0cef4e9de  miuiandroid_lang_endeavoru-2.10.19.zip
a60c92494f34ae0304092c46ea16e5dd  miuiandroid_lang_grouper-2.10.19.zip
ff589cd5900a6d0204711f58b72878bb  miuiandroid_lang_GT-I9100-2.10.19.zip
be68e080fb1872a5c8db53ff91705756  miuiandroid_lang_hwu8860-2.10.19.zip
7bbb9d82a1a786dbca82350e31048754  miuiandroid_lang_i_u-2.10.19.zip
3bf7eda6c5b8ef22910681723848df82  miuiandroid_lang_LT18i-2.10.19.zip
1762c84c861e8ade09fce1c6964c168a  miuiandroid_lang_m0-2.10.19.zip
4641b8fe6a73ffd8cca6c58a62bd3587  miuiandroid_lang_maguro-2.10.19.zip
3702911c9b733b3463f63b8b4f93a595  miuiandroid_lang_mione_plus-2.10.19.zip
0408ac0124991c1421079c60eb749bbc  miuiandroid_lang_pyramid-2.10.19.zip
ef7313d51240e6d4f8b58564bc98d54d  miuiandroid_lang_saga-2.10.19.zip
6369deb4608e30edb14c9e01fdc2cfa6  miuiandroid_lang_shooteru-2.10.19.zip
aeeff150b2e78c3cfc2aff4589e4b5b9  miuiandroid_lang_umts_spyder-2.10.19.zip
286f855aea397cee7819abce87afef81  miuiandroid_lang_ventana-2.10.19.zip
e3c949548ffcd6b808e21e9693cd1047  miuiandroid_lang_ville-2.10.19.zip
52c79a32c6a9cee43add74ec30173d81  miuiandroid_lang_vivo-2.10.19.zip

Downloads:
Code:
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_aries-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_crespo-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_edison-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_endeavoru-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_grouper-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_GT-I9100-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_hwu8860-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_i_u-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_LT18i-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_LT26i-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_m0-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_maguro-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_pyramid-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_saga-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_shooteru-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_umts_spyder-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_ventana-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_ville-2.10.19.zip
http://goo.im/devs/ibotpeaches/miuiandroid/releases/2.10.19/multi_lang/miuiandroid_lang_vivo-2.10.19.zip
Thanks,
Connor
 
Flashing this on the Motorola RAZR XT910 over MIUI v2.10.19 made me lose automatic screen brightness. It gets stucked in the lowest brightness level, no matter where I am. However, manually setting the brightness works fine. I tried a clean installation of the whole system, but it ends up with the same issue, after a reboot or two. The problem happens only after flashing the language pack, not within the original ROM. I'm trying Brazilian Portuguese language. Did this happen to anyone else?
 
Flashing this on the Motorola RAZR XT910 over MIUI v2.10.19 made me lose automatic screen brightness. It gets stucked in the lowest brightness level, no matter where I am. However, manually setting the brightness works fine. I tried a clean installation of the whole system, but it ends up with the same issue, after a reboot or two. The problem happens only after flashing the language pack, not within the original ROM. I'm trying Brazilian Portuguese language. Did this happen to anyone else?


This happens only with Brazilian Portuguese language? You try another language?
 
This happens only with Brazilian Portuguese language? You try another language?

I'm stupid and I forgot to check another language before reverting back to my previous generic v2.10.19 backup, but I'm reflashing the language pack right now to see if it happens. I'll edit this post when I get the answer.

Edit: I reflashed the language pack over my working generic v2.10.19. Lost automatic brightness control after booting into system with Brazilian Portuguese language. Switched the language to English, automatic brightness still wasn't working, but got back working after a reboot. Then switched back to Brazilian Portuguese again, automatic brightness was still working, but after rebooting the system, it stopped working once again. I'm afraid this means it's supposed to be a problem with the translation, right? I hope this can help. Manually setting the display brightness worked fine on all tests, although.
 
I'm not sure how the build process for language packs is done, but shouldn't the default translations be based on the English-only ones? There are some inconsistencies in fallback/default translations. Easy example is values/strings.xml in NetworkLocation - On the English-only ROM they are English, but in the language pack they are Chinese (and also has more strings that I guess aren't used anymore)?

Things like this may cause bugs for users on Non-English, not when there is a bug in translation but when there is *no* translation and it falls-back to the obviously-outdated default in values/.

I've said this before but I'll say again - I think it's pretty important that the new MIUIAndroid English XML are used in values/ and not values-en/ - and kept the same across English-only and Multi-language builds. This would ensure that the default (fall-back) values/ XML are always the current English and will allow the user to correctly test if it's a translation issue or not.
 
I'm not sure how the build process for language packs is done, but shouldn't the default translations be based on the English-only ones? There are some inconsistencies in fallback/default translations. Easy example is values/strings.xml in NetworkLocation - On the English-only ROM they are English, but in the language pack they are Chinese (and also has more strings that I guess aren't used anymore)?

Things like this may cause bugs for users on Non-English, not when there is a bug in translation but when there is *no* translation and it falls-back to the obviously-outdated default in values/.

I've said this before but I'll say again - I think it's pretty important that the new MIUIAndroid English XML are used in values/ and not values-en/ - and kept the same across English-only and Multi-language builds. This would ensure that the default (fall-back) values/ XML are always the current English and will allow the user to correctly test if it's a translation issue or not.

Easy to say. Hard to do. We used to replace values & values-en to provide fallbacks to English instead of Chinese, however the /values folders are now different among every device. Mainly the arrays.xml and strings here and there. Using one values setup for all devices causes more bugs then it solves.

It just forces lang developers to pick it up and translate more.
 
I'm stupid and I forgot to check another language before reverting back to my previous generic v2.10.19 backup, but I'm reflashing the language pack right now to see if it happens. I'll edit this post when I get the answer.

Edit: I reflashed the language pack over my working generic v2.10.19. Lost automatic brightness control after booting into system with Brazilian Portuguese language. Switched the language to English, automatic brightness still wasn't working, but got back working after a reboot. Then switched back to Brazilian Portuguese again, automatic brightness was still working, but after rebooting the system, it stopped working once again. I'm afraid this means it's supposed to be a problem with the translation, right? I hope this can help. Manually setting the display brightness worked fine on all tests, although.


Yes, probably is a problem in the translation files, I'll take a look.
 
Easy to say. Hard to do. We used to replace values & values-en to provide fallbacks to English instead of Chinese, however the /values folders are now different among every device. Mainly the arrays.xml and strings here and there. Using one values setup for all devices causes more bugs then it solves.

It just forces lang developers to pick it up and translate more.

Ah right, I see. What a shame. Maybe in time a command-line method of parsing XML to merge/inject values-en updates to values is something I can do for my builds. Thanks for info.
 
Ah right, I see. What a shame. Maybe in time a command-line method of parsing XML to merge/inject values-en updates to values is something I can do for my builds. Thanks for info.

We did use a merge method for a couple of weeks and it worked pretty well. We just had the extras in .part files in the /device directory which was merged on build in the final xml. However, there were XMLs that were different among devices and some removed. A never got the script perfected to properly remove/update/delete. So we dropped it in favour of just values-en.
 
We did use a merge method for a couple of weeks and it worked pretty well. We just had the extras in .part files in the /device directory which was merged on build in the final xml. However, there were XMLs that were different among devices and some removed. A never got the script perfected to properly remove/update/delete. So we dropped it in favour of just values-en.

Wouldn't it still help (and not be device-specific) to compare the XML elements of the same name between values and values-en, and if an element exists in both - move it to values and then remove it from values-en? That way nothing would be removed from the values default, but only updated with values-en's newer entries where appropriate - and anything new (if any) will remain in values-en. Not sure if using a complex sed routine with embedded variables could handle that or not, but gawk could pretty well.

Regardless, the only issues I've found in decompiling the latest language pack is the Ukranian in Phone.apk, so it all seems to be the best it's been in a while. Still, I'm concerned
 
I'm stupid and I forgot to check another language before reverting back to my previous generic v2.10.19 backup, but I'm reflashing the language pack right now to see if it happens. I'll edit this post when I get the answer.

Edit: I reflashed the language pack over my working generic v2.10.19. Lost automatic brightness control after booting into system with Brazilian Portuguese language. Switched the language to English, automatic brightness still wasn't working, but got back working after a reboot. Then switched back to Brazilian Portuguese again, automatic brightness was still working, but after rebooting the system, it stopped working once again. I'm afraid this means it's supposed to be a problem with the translation, right? I hope this can help. Manually setting the display brightness worked fine on all tests, although.


Ricardo,

I believe I have found the problem, but it is specific to your device, so I can not test.

For you to test, in the link bellow is the file to be replaced, you have to put it in the folder "/system/framework/":

http://www.mediafire.com/?2kobly6wwyk8alx

Please report if the problem was solved.

Thank you.
 
  • Like
Reactions: Ricardo Gonçalves
Wouldn't it still help (and not be device-specific) to compare the XML elements of the same name between values and values-en, and if an element exists in both - move it to values and then remove it from values-en? That way nothing would be removed from the values default, but only updated with values-en's newer entries where appropriate - and anything new (if any) will remain in values-en. Not sure if using a complex sed routine with embedded variables could handle that or not, but gawk could pretty well.

Regardless, the only issues I've found in decompiling the latest language pack is the Ukranian in Phone.apk, so it all seems to be the best it's been in a while. Still, I'm concerned

I only know sed and couldn't get it mastered without errors. Using sed expressions with XML is difficult already due to some with newlines and what not. The proper thing was looking for a library that could handle XML files easily, XML::Starlet was one that we tried, but all of this requires hours of testing and time and if you want to keep daily MIUI build testing and make sure everything is set for Friday its not really a thing I want to spend time looking into again.

The main problem is translators are missing strings and we shouldn't have to adapt our scripts majorly to account for it. That being said if you find any progress and it works let me know. The problem with Ukranian is actually an apktool bug on re-decompile. So its fixed in Apktool v1.5.1
 
I only know sed and couldn't get it mastered without errors. Using sed expressions with XML is difficult already due to some with newlines and what not. The proper thing was looking for a library that could handle XML files easily, XML::Starlet was one that we tried, but all of this requires hours of testing and time and if you want to keep daily MIUI build testing and make sure everything is set for Friday its not really a thing I want to spend time looking into again.

The main problem is translators are missing strings and we shouldn't have to adapt our scripts majorly to account for it. That being said if you find any progress and it works let me know. The problem with Ukranian is actually an apktool bug on re-decompile. So its fixed in Apktool v1.5.1

OK nice work regarding APKTool, as always. Alas I build on Windows (gasp) and have been unable to build latest APKTool from source, so I'm happy to work around it until the release of 1.5.1.

Yeah I figured as much, hence why I mentions a gawk script. AWK is basically a programming language for text manipulation, not very elegant but extremely powerful and flexible. But that too would take a lot of coding and salinity tests on obscure patterns.

A quick example on how an AWK script can be used to merge two text files based on mentioned conditions can be seen here. Personally I can't think of a better way to handle XML's and I may look into doing one, but as you said - it's really up to the translators to keep on top.
 
There is u bug in CZ pack... search in default web browser in search panel dont work...

( nefunguje vyhledavani v default web browseru... kdyz napisu hledane slovo do panelu pro vyhledavani vyjede jen cista page googlu ) kdyz to skuim v ciste miuiandroid bez CZ packu tak to funguje...
 
Status
Not open for further replies.