Localization story #666
Comments
|
Issue number suggests it's going to be fun. |
|
Without cross-platform resgen (#395), this isn't going to be fun. |
Specifically this enables us to leverage `dotnet-resgen` to auto-generate the `resx` files into `resources` files for the default culture, which are then compiled into the SMA assembly. This requires a change to the C# bindings. The Windows build system takes `file.resx` and compiles `file.resources`, but CLI prepends the assembly name, thus compiling `SMA.file.resources`. So the resource manager in the generated bindings must be adjusted to look for `SMA.file` instead of `file`. Note that C# bindings cannot yet be auto-generated. Given localized resources of the form `file.en-US.resx`, `dotnet-resgen` will create a satellite assembly and publish it to `en-US/SMA.resources.dll`, so #666 will not be a technical problem.
|
There is now improved satellite assembly support, per dotnet/cli#2511. |
|
Assigning this to me to follow-up with legal to determine to what extent we need this. |
|
Any news? |
|
Copying over a simple Pester test for localized error messages from the now closed duplicate #10679: [cultureinfo]::CurrentUICulture = 'de-DE'; Get-Item nosuch 2>&1 | Should -match 'nicht gefunden' |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Question came out during our onboarding hackathon: "Who will localize our resources when we move to github?"
Assigned to Joey to follow-up.
The text was updated successfully, but these errors were encountered: