EmulationStation localization (translation)

hiulit

@heloisa Yes, please! Thanks

kactius

@heloisa
Is easy only:

msgid "OTHER SETTINGS"
msgstr "⚙️OTRAS CONFIGURACIONES"

msgid "CONFIGURE INPUT"
msgstr "⌨️CONFIGURAR CONTROLES(MAPEADO)"

heloisa

@kactius Tks :) Really cool. I'm going to test here, with other icons too.

darknior

Excellent idea, How do you do for icons ? They are in the font ??

hiulit

@darknior I think they are emojis https://emojipedia.org/ Am I right @kactius ?

kactius

@hiulit @heloisa @darknior

Yes they are emojis, those two were copied from Telegram client.
I tried paste many more without success.
I also think it's related to the font file, but I do not know what is the font file.

hiulit

@Flyinghead any news on updating EmulationStation from the master branch?

Leonard Lin

@Flyinghead I add traditional chinese translation (zh_TW) file.
https://github.com/Leonard-Lin/EmulationStation/blob/master/locale/lang/zh_TW/LC_MESSAGES/emulationstation2.po

darknior

@hiulit said in EmulationStation localization (translation):

@Flyinghead any news on updating EmulationStation from the master branch?

Yep if possible please when you have some free time :)
They've finally fixed the video image resize bug i reported last year ...
Thanks

hiulit

We could also try to "pressure" the RetroPie team to bring localization to main EmulationStation repository https://retropie.org.uk/forum/topic/21328/bring-localization-to-emulationstation

Leonard Lin

Hello.
I translated the translation into Traditional Chinese,
https://github.com/Leonard-Lin/EmulationStation/blob/master/locale/lang/zh_TW/LC_MESSAGES/emulationstation2.po
compiled & run ES, LANG=zh-TW.UTF-8 ./emulationstation,
but EmulationStation V2.8.0RP-DEV it won't launch :-( ,
I don't understand why returns to English,
Can someone help me? Thank you in advance!

hiulit

@Leonard-Lin Did you follow these steps? https://github.com/flyinghead/EmulationStation#how-to-use-the-localized-emulationstation

When you have compiled EmulationStation, you have to:

cd /home/pi/EmulationStation # Or the path to your compiled EmulationStation
LANG=[your_locale].UTF8 ./emulationstation

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

Leonard Lin

@Hiulit after compiled EmulationStation, found 9 fatal errors (string & duplicate),

I corrected the file (Traditional Chinese)
https://github.com/Leonard-Lin/EmulationStation/blob/master/locale/lang/zh_TW/LC_MESSAGES/emulationstation2.po

and Run EmulationStation,

cd /home/pi/EmulationStation
LANG=zh_TW.UTF-8 ./emulationstation

now EmulationStation V2.8.0RP-DEV can translate into Traditional Chinese correctly.
@Flyinghead can you upgrade localized ? thanks a lot !

Another question, does anyone know how to modify the text and color description of EmulationStation in the red box? I want to add localization information.

hiulit

@Leonard-Lin That's amazing! One more translation for EmulationStation :D

Leonard Lin

One generation plants the trees in whose shade another generation rests, Thanks everyone sharing here :-)

@Hiulit said in EmulationStation localization (translation):

@Leonard-Lin That's amazing! One more translation for EmulationStation :D

hiulit

@Leonard-Lin Btw, it would be better if you create a Pull Request in @Flyinghead Github with your Traditional Chinese translations ;)

hiulit

@BuZz Would you be willing to merge https://github.com/flyinghead/EmulationStation with the master branch of RetroPie's EmulationStation? We have already 8 different languages and we are waiting for another one to come in pretty soon :)

jdrassa

@hiulit In its current state, @Flyinghead's isn't going to be merged into RetroPie. There are a couple of issues that would prevent this.

First, there are other changes unrelated to localization. Those changes, if wanted in RetroPie should be handled separate from the localization. However, I briefly reviewed the commits and there is at least one feature added that we would likely not accept. There is a UI option added for adjusting screen backlight brightness. This is hardware/os specific functionality that we prefer to keep out of ES.

As to the actual localization implementation, it is dependent on the boost library. RetroPie has moved away from using boost. I can't say definitively that boost would not be accepted, but it would be an uphill battle. It would have a better chance of being accepted if boost was not used.

That being said, I have been thinking about this and there are some changes that could be made in RetroPie ES to ease the process maintaining a localized fork for @Flyinghead or anyone else who might choose to do so. We could abstract out the localization and for now support a noop localization implementation, in theory would minimize the changes needed to support localization via boost or some other method. Instead of having to change every file where text is rendered, they would only have to change the localization abstraction.

Of course, doing that requires time, effort and motivation.

hiulit

@jdrassa Thanks for the explanation. I can't speak for @Flyinghead as he/she is the one who created this fork and did all the coding to allow the localization. He/she would be the one to better answer you about those changes unrelated to localization.

In any case, could the localization be implemented in RetroPie's EmulationStation in another way? I know this would require time, effort and motivation, but I can see people want, or are very interested in localization. We already have a good amount of translations and if localization would ever be a part of the main EmulationStation (and with good documentation, that I'd be more than happy to help create) I think more people would contribute with more translations.

Lolonois

Since it is not very probably that the current implementation can/will be merged, why not change the implementation?

From my understanding you change the language not very often (mostly once during setup of an Arcade).

Let's assume the localization (e.g. es_l10n) would be a retropie package that can be applied via retropie_setup.sh or retropie_package.sh.

Just as idea (since this is the ideas and development forum ;-) ), the use case would be as follows:

Install ES as ever
Select l10n package, select your language from retropie-setup
- The es_l10n package fetches ES sources and
- does a search and replace with all the strings to localized with the user specified *.po file (the language)
- recompiles ES and installs it in the usual manner

On update of ES the process could be:

During installation of the ES the es_l10n is called with the language set by the user as above,
the language specific strings get replaced by the es_l10n package,
then the usual install continues.

Benefits:

No royal PITA (and/or "uphill battle") to merge the current implementation into upstream
Seamless integration into current retropie-setup logic
Current translation efforts are not lost

Drawback:

Code changes from fork can not be used