[Wasm] Satellite assemblies are not properly published

[paulovila]

Current behavior

In WASM, the ResourceManager.GetString uses the CultureInfo as parameter, but fails to recognise the culture passed

Expected behavior

It should return the culture passed regardless of the supported languages of the browser.

How to reproduce it (as minimally and precisely as possible)

see example in https://github.com/paulovila/UnoLocalization/blob/master/App9/App9.Shared/MainPage.xaml.cs
UnoLocalization-master.zip

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[jeromelaban]

Localization at this time is best supported using resw, not embedded assembly resources. Are you able to use resw instead?

[paulovila]

The netstandard2 project is also referenced from WPF, therefore Windows.ApplicationModel.Resources.ResourceLoader .GetForViewIndependentUse().GetString(resource); can't be used.
Is it possible to re-implement System.Resources.ResourceManager.GetString , or where's the source code of this?

[jeromelaban]

Thanks. This issue is related to satellite assemblies publishing in the uno bootstrapper. Reimplementing it on your side is one option, but not necessarily the best one either.

[darenm]

@jeromelaban Sounds like this is a non-trivial issue to address on either side. Are there any plans to address this in Uno?