EmulationStation localization (translation)

hiulit

@heloisa Wow! Thanks!! I'll try it as soon as I can!

heloisa

@hiulit You're Welcome. Good luck :)

Shaddonai

Yes, I AM interested and willing to help. Retropie en español no estaría mal, especialmente para los teclados de LATAM. Poner comandos sin saber dónde hay teclas como - es molesto.

wakaya

@Flyinghead
I fixed a few expressions and sent a pull request.
Please merge when you have time.

@heloisa
I'm glad to help you.

kactius

@heloisa
Hello.
Please can you tell me what is the correct way to notify , about of some improvements to a Spanish translation?
Example:
NOMBE , correct Word is = NOMBRÉ.
I have more suggestions.

heloisa

@kactius Hello. Thanks for warning me, typing error. Open pull request on my github, or send me email with the improvements. :)

hiulit

Thanks @heloisa ! It works! :D

hiulit

I would like to thank @Flyinghead for this fork of EmulationStation and the rest of the people that made localization possible. It's a pity that the RetroPie team doesn't want (that's my understanding) to add this feature to the master branch of RetroPie's EmulationStation fork. It would be really cool.

In the meantime, @Flyinghead , could you update your fork to be at the same level as RetroPie's EmulationStation fork? There has been many new features that the people who also want localization are missing.

Thanks a lot! :)

hiulit

Btw, @heloisa , why do you need to do the step 3 on your documentation?

Copy the Locale Directory

cp -r locale/lang/fr locale/lang/(Your locale)

I didn't use it and I got it working anyway.

heloisa

@hiulit :) Good thing it worked, you're welcome.

heloisa

@hiulit I couldn't translate without. I'll try again without step 3. Tks

hiulit

Does anybody know who did the Italian and French translations?

hiulit

Questions for @Flyinghead :

Is the .gitignore that I see in some LC_MESSAGES folders necessary?
Shouldn't we agree on the first part of the *.po file?

msgid ""
msgstr ""
"Project-Id-Version: retropie-emulationstation\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-02-06 10:58+0100\n"
"Last-Translator: hiulit \n"
"Language: ca_ES\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

Is this the correct version? What should/n't be on it?

Thanks!

hiulit

Updated the README on @Flyinghead 's EmulationStation fork.

Localized EmulationStation

This is a localized fork of Retropie's EmulationStation fork.

Inspired by similar work on the Recalbox fork.

Languages currently supported

Catalan
French
Italian
Japanese
Portuguese (Brazilian)
Spanish

How to use the localized EmulationStation

Resolve dependencies of libraries

sudo apt-get install -y libboost-system-dev libboost-filesystem-dev libboost-date-time-dev libboost-locale-dev libfreeimage-dev libfreetype6-dev libeigen3-dev libcurl4-openssl-dev libasound2-dev cmake libsdl2-dev

Create a clone from GitHub

cd /home/pi/
git clone --recursive https://github.com/flyinghead/EmulationStation.git

Compile EmulationStation

cd /home/pi/EmulationStation
mkdir build
cd build
cmake ..
make

Run EmulationStation

Be aware that your system must be set to the same locale that you want EmulationStation to run on.

cd /home/pi/EmulationStation
LANG=[your_locale].UTF8 ./emulationstation

Install EmulationStation

cd /home/pi/EmulationStation
sudo cp ./emulationstation /opt/retropie/supplementary/emulationstation/
sudo cp -r locale /opt/retropie/supplementary/emulationstation/

How to add a translation

You should have, at least, created a clone from GitHub before continuing with the following steps.

Create files for the new locale

cd /home/pi/EmulationStation/locale
mkdir lang/[your_locale]
cp emulationstation2.pot lang/[your_locale]/emulationstation2.po

Translate the strings

Open the newly created emulationstation2.po inside [your_locale] folder and start translating all the msgstr strings.

Once you are done, you can compile EmulationStation and then run it to test your translations.

Author

flyinghead.

Credits

Thanks to:

flyinghead - For the French translations.
heloisa - For the Portuguese (Brazilian) and Spanish (Spain) translations.
wakaya - For the Japanese translations and for the instructions on how to use the localized EmulationStation.
hiulit - For the Catalan and Spanish (Spain) translations.
Unknown - For the Italian translations.

hiulit

@heloisa Yay! :D

ande.rocha

@heloisa ou Carmen Sandiego, como preferir... rs
Poderia me ajudar a configurar o ES para o português pt-br também?

heloisa

@ande-rocha kkkkk meu jogo favorito. Então, eu fiz o passo a passo. AQUI. Mas se não conseguir, me envie email, está ali no meu GitHub.

Clyde

Hello everyone,

is anyone working on a German locale already? If not, I would like to give it a try.

Do I just take the emulationstation2.pot and write the translated terms into the corresponding msgstr fields? Where should I put the final file and how should I name it? I already have a Github account if it helps.

Thanks for any advice.

wakaya

@hiulit

You should ask me questions, because I'm the author of this explanation, may be.

This explanation is just for "adding a new locale".
It does not explain how to compile from an existing source tree.
Therefore, I think that step 3 is an essential method to simply add a locale.

In addition, I found out that your document contains old information.
"sudo apt-get install libboost1.62-*"
It is unnecessary.

The latest commentary is always updated with https://pastebin.com/edit/L3MyFkeD.
Because the information has not been confirmed at this time.

I am writing a document on pastebin because there is a possibility of future modification.
I think that writing a "well formatted document" on a place like a forum may cause misunderstanding.

wakaya

@Clyde

Hello:-)
I wrote a brief comment on "https://pastebin.com/edit/L3MyFkeD"
You should replace (your locale) with "de_DE" or similar locale.

The way of editing just fills msgstr with German as you assumed.
Since you already have a github account, you should send a pull request to flyinghead after your editing.