Context-less Localized Strings

[infofromca]

Is your feature request related to a problem?

currectly , we need msgctxt for each module view path:
msgctxt "GuangCore.SaaS.Views.Setup.Index"
msgid "Email"
msgstr "电子邮箱"

Describe the solution you'd like

we do not need msgctxt :
msgid "Email"
msgstr "电子邮箱"
in this way, the translation can be used across the whole site to avoid repeating in .po files.

Describe alternatives you've considered

or:
msgctxt "OrchardCore.General"
msgid "Email"
msgstr "电子邮箱"

[hishamco]

The message context is useful if the localization string appears in multiple modules. I understand what you mean. You could use a shared class to have common localization strings, but we need to check https://github.com/OrchardCoreContrib/OrchardCoreContrib.PoExtractor for supporting this

Related: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/localization/make-content-localizable?view=aspnetcore-10.0#shared-resources

[infofromca]

oh, maybe i did not express it clearly.
we need current way:
msgctxt "GuangCore.SaaS.Views.Setup.Index"
msgid "Email"
msgstr "电子邮箱"
but also need

msgid "Email"
msgstr "电子邮箱"

if there is no msgctxt or msgctxt "OrchardCore.General", perform the above first way.

[sebastienros]

To rephrase, you want a way to have context-less localized strings, such that you don't have to translate the same things all over the place when it will never vary (for simple strings).

I think that's a good idea if we can make it work. Assuming it's opt-in, so we don't duplicate these in crowdin.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[hishamco]

This needs two things:

• Let the PO Extractor tool be aware of shared localization resources, and where the shared resources are stored
• Modify the underlying logic in the localization APIs to support context-less

Last, how will Crowdin be aware of this?

/cc @agriffard