Cannot use localized resx files in exported game

[xill47]

Godot version: 3.2.3.stable.mono

OS/device including version: Windows 10 2004 (also tested in Ubuntu VM)

Issue description:

When I use .resx file and its localized counterpart, I am getting the right string (ResourceManager respects CultureInfo.CurrentCulture) when running the game from Godot Editor, but string fallbacks to the default (unlocalized one) when running exported project.

Probably relevant: mono/mono#19928
Mentioned workaround doesn't work in exported project since all assemblies seem to be packed into .pck file.

Steps to reproduce:

1. Create Mono project
2. Add resx file
3. Add localized resx file
4. Export project with default Windows or Linux template

Minimal reproduction project:

ResxLocalizationProblemMinimum.zip

[Calinou]

Out of curiosity, why not use Godot's built-in localization system instead of .resx files? It supports both the CSV and gettext formats.

[xill47]

That's what I am probably going to do, but it was just out of old habit. Still need to find comfortable tooling to use with gettext (csv will just become too cluttered if there will be additional translations).

[akien-mga]

Do you add *.resx files in your export filter to ensure they get included in the PCK? Godot by default only exports known resources, and doesn't know about *.resx.

That's what I am probably going to do, but it was just out of old habit. Still need to find comfortable tooling to use with gettext (csv will just become too cluttered if there will be additional translations).

You can use PO files with Godot's Translation resource.

[xill47]

@akien-mga
Both .NET and Mono compile .resx files down to .dll files (I can find them inside .mono\temp\bin\Debug\{lang id} in Godot project) so it doesn't seem necessary. I tried anyway, it didn't make any difference.

I understand that I can use Godot's Translation resource, I am just looking for a convenient way to generate PO templates and edit translations. (For future reference or anyone who will find it with similar problem: I will probably create .txt file with strings, use txt2po from translate-toolkit package and then Poedit as recommended in Godot Documentation, or similar alternative)

[akien-mga]

You might be interested in @SkyLucilfer's GSoC work: #39415
It's for Godot 4.0 though.

I'm not familiar with the .NET translation workflow but we probably need to support it independently of Godot's own features. @neikeq might know more about this.

[object71]

It could work pretty easily - in the minimum project you provided after build you can find the compiled resources in:
ResxLocalizationProblemMinimum/.mono/temp/bin/Debug

There will be a "ru" folder in your case. Copy that ru folder to the exported project location as in:

[object71]

I will take a look if the folder can be included in the export process

[Calinou]

I will take a look if the folder can be included in the export process

@object71 Bump 🙂 Did you manage to do this?

[object71]

Considering I wrote it an year ago we can safely assume I forgot about it.

[markdibarry]

Any news on this front? Would be super cool to have type-safe resource strings supported with Godot.

[RedworkDE]

This was fixed on 4.0, tho the issue likely remains on 3.x.