Change language in screen's text

[neometalero]

I'm using this code for changing the language on my screen, but it doesn't work when I change the language. Always show the none option. What I'm doing wrong?

Code: Select all

vbox:
            if Language(None):
                text _("{color=#F313E4}Points:{/color} ") + str(g.points) size 24
                text _("{color=#F313E4}Time:{/color} ") + str(g.duration) size 24
            else:
                text _("{color=#F313E4}Puntos:{/color} ") + str(g.points) size 24
                text _("{color=#F313E4}Tiempo:{/color} ") + str(g.duration) size 24

[_ticlock_]

Hi, neometalero,

Your example is not how the RenPy translation system works.
The construction _("") you are using is necessary for the RenPy translation system to recognize that this string should be translated. For your screen you need only:

Code: Select all

vbox:
    text _("{color=#F313E4}Points:{/color} ") + str(g.points) size 24
    text _("{color=#F313E4}Time:{/color} ") + str(g.duration) size 24

Then you can generate translation files in the RenPy launcher. (Check doc and this cookbook for more info and example).

In your generated translation file that is located in tl/<language>/<name_of_file.rpy> you should have something like:

Code: Select all

# game/script.rpy:<line number>
    old "{color=#F313E4}Points:{/color} "
    new "{color=#F313E4}Points:{/color} "
    
# game/script.rpy:<line number>
    old "{color=#F313E4}Time:{/color}  "
    new "{color=#F313E4}Time:{/color} "

old show default language string, and new string you replace with translated string

[Jackkel Dragon]

Another note with translating displayables (as opposed to dialogue): some displayables only update on the next interaction. This means changing languages while that text is displayed requires rolling back to update the language. Using translation strings should prevent this in most cases, while the original code you have may require rolling back to work.

[neometalero]

Hi, neometalero,

Your example is not how the RenPy translation system works.
The construction _("") you are using is necessary for the RenPy translation system to recognize that this string should be translated. For your screen you need only:

Code: Select all

vbox:
    text _("{color=#F313E4}Points:{/color} ") + str(g.points) size 24
    text _("{color=#F313E4}Time:{/color} ") + str(g.duration) size 24

Then you can generate translation files in the RenPy launcher. (Check doc and this cookbook for more info and example).

In your generated translation file that is located in tl/<language>/<name_of_file.rpy> you should have something like:

Code: Select all

# game/script.rpy:<line number>
    old "{color=#F313E4}Points:{/color} "
    new "{color=#F313E4}Points:{/color} "
    
# game/script.rpy:<line number>
    old "{color=#F313E4}Time:{/color}  "
    new "{color=#F313E4}Time:{/color} "

old show default language string, and new string you replace with translated string

Renpy didnt generated translations for those items on the screen, that why I tryied to to it by hand

[neometalero]

Another note with translating displayables (as opposed to dialogue): some displayables only update on the next interaction. This means changing languages while that text is displayed requires rolling back to update the language. Using translation strings should prevent this in most cases, while the original code you have may require rolling back to work.

Tks, I didnt knew that about displayables. Will check if rolling back works.