I Can Add Japanese Lanuage Miui Global Rom For Mi5

[rina2016]

Hi all.
I ordered xiaomi Mi5 3GB/64GB white today.
It is installed MIUI global ROM.
But japanese language not support now.

I want to add japanese language to MIUI global ROM for Mi5.
I can translate english to japanese.

I want to participate in the translation work, how do I do this?
Please advice me.

Thank you!

 

[discom]

Hello ,
That's the weakness of this project.

There is no help or documentation for newcomers who wants to start translation.

I tried to get help like you and I finally stop my efforts.

 

[MannyRibo]

What's this?

https://docs.google.com/document/d/1H8DoN6nnbsOGB_fauBiCcpyB4OAIEHjqEiJX322v45Y/mobilebasic#

Ask me what you want to know and I will help.

 

[discom]

What's this?

https://docs.google.com/document/d/1H8DoN6nnbsOGB_fauBiCcpyB4OAIEHjqEiJX322v45Y/mobilebasic#

An very outdated documentation who is lacking of many steps.

How did you get the origial tree of XML to translate ?

How did you get; weekly; the news string to translate ?

 

[MannyRibo]

I think that link tells you that perfectly but anyway. 1. Because you clone the English repository and copy all the XML files including file structure, rename all the folders accordingly to your language and then you start translating it.

2. New strings show on the English repository. You have to keep up with the changes made there. So whenever there are strings added/removed there you do the same.

 

[discom]

Hello

Sorry. I don't understand which repository I must fork first (URL).

2. How did we get the "diff" between releases? What is the automated process to keep our XML up2date with the new strings to translate, and auto remove the obsolete strings?

Thanks for your help

 

[MannyRibo]

The original English repository. Only so you have those files on your hard drive.

There is no automated process, and no auto delete. That's why every language needs someone to maintain it and check for changes. The strings that get removed from the English repo, you remove from your XML files too. The strings that get added, you add them to your files too, and translate them.

 

[discom]

I looked into the English repo and they post a lot of commit for a release.

near 15 enormous commits for 6.5.5.

If i look at the 1rst, all the file path are beggining with "wt88047" which is a device.
Ex : wt88047/Browser.apk/res/values/strings.xml

But if i look into your Dutch repo; there is no "wt88047" folder.

and your commits are a lot lot shorter; and you touch many less files.

So what's the point ? Why you didn't have the same folders as the English repo ?

And for a release (ex 6.5.5) What do you do with for example with a commit of

cancro/Browser.apk/res/values/strings.xml

And the one of

gemini/Browser.apk/res/values/strings.xml

(you don't have any of theses in your repo)

Thanks

 

[ingbrzy]

Translation has "main" folder which is used for all devices...

~Tapatalk Mi5~

 

[dogiex]

Where to get the current "main" folder english files or can I just download these https://github.com/Acid-miuipolskapl/v6-XML-Compare and using the devices (like cancro) .xml files and translate those to the "main" folder?

Or is it fine if I download the apktool and decode one of the recent dev roms .apk files and then I get the english .xml files from there and start translating them?

 

[discom]

OK for the "main" folder. So all goes in this one.

But which root directory (aka device ) to follow for translation?

 

[ingbrzy]

Choose one.. Gemini for example.. But wait for MIUI 8..

~Tapatalk Mi5~

 

[MannyRibo]

I looked into the English repo and they post a lot of commit for a release.

near 15 enormous commits for 6.5.5.

That's because every week all the changes get pushed for all the devices. So changes are, a lot of those commits include the same changes. You pick one device which you track the changes of and edit your xml files accordingly. You don't have to skim through all these 15 commits.

and your commits are a lot lot shorter; and you touch many less files.

So what's the point ? Why you didn't have the same folders as the English repo ?

Because we only have a main folder and not all the different device folders. When a particular device needs a string it takes it from the main folder. Our commits can be a lot shorter because some things are values, or some things don't need translation because they are usable as they are. Then the system just takes those strings from the original xml file and it will be fine.

And for a release (ex 6.5.5) What do you do with for example with a commit of

cancro/Browser.apk/res/values/strings.xml

And the one of

gemini/Browser.apk/res/values/strings.xml

(you don't have any of theses in your repo)

As said before you only have to worry about one of those and ignore the rest.

When you don't get something I'm always willing to help, just let me know.

 

[discom]

@rina2016
Did you get all the information you need to start the translation in Japanese?

I asked a lot but it was for the global knowledge as I am not Japanese ^.^

Envoyé de mon MI 5 en utilisant Tapatalk