PySol FC's Language Cannot be changed away from English

[shlomif]

I got this in an email:

«

Hello! For some reason, my bug is not displayed on GitHub, probably that I recently registered and my account was flagged. Duplicate you a bug about PySolFC 3.0:

In the previous version of PySolFC, everything was fine. As soon as I updated to the latest version (3.0), then the language of the game became only English. Not a change in the AppData configuration of the language = did not give anything, nor reinstalling the program several times and cleaning the configuration files, the language is still English. What's happened? How to change the language of the game in the PySolFC version 3.0? Thank you.

»

It's from a user calling themselves Ivich. Ivich, can you provide details about your operating-system, hardware, etc.?

[shlomif]

Ivich wrote:

«

OS: Windows 10 Pro x64
Version: 22H2; 19045.4529; Windows Feature Experience Pack 1000.19058.1000.0
AMD Ryzen Processor; Russian language (system language)

Thanks!

»

[joeraz]

So I looked into this on my Windows 10 environment. When I tried to change the language while running from the source code, I was able to do so no problem. But when I tried the version installed with the installer, I saw the same thing happening. I tried both version 3.0 and the latest dev version, and got the same issue.

I think there might be an issue with the localization files being included in the installer (the installer config scripts have been giving me a lot of trouble lately). The most recent issue I ran across is where AppVeyor is no longer recognizing the xgettext command, which is part of the logic generating the localization files, but this is more recent, and causes AppVeyor to fail outright unless I tell it to use the previous version of the environments. Though given this, it seems there are more issues with this than I realized, which doesn't surprise me given how the scripts have been lately.

Unfortunately, I'm not sure how to fix this.

[joeraz]

So it seems even if I use the files I generated myself and included in the package, I still see the issue. It seems to be something specific to the compiled builds generated with PyInstaller.