Components should be able to automatically be translated when loaded in a specific language

[sebastienlevert]

[ghost]

Hello sebastienlevert, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[gavinbarron]

Is this a request to support multiple languages and dynamically determine which of those localizations to use?

Seems like a great idea that some of the search work will unlock.

[sebastienlevert]

Exactly. Basically having proper localization files in the product and display the right content based on the locale of the connected user (if this is the desired behavior). This would improve scenarios like SPFx integration with the Modern Search Web Part where the ownership of localization is on the team importing MGT. I feel we need to do better.

[JoelBVezina]

I've been using mtg-person (mainly through PnP Search module) for French only institutions and this always comes up as an issue. Looking forward for evolution in that regard

[sebastienlevert]

Salut Joel!

We are currently review the strategy here. We want to be able to provide a better experience. We have 2 options at this point. Make this part of MGT, or document how to achieve from a 3rd party library using MGT. For PnP Modern Search, we'd even be able to go and send a PR.

We're still in the process of understanding the constraints but we think this should land as soon as we have a good path forward. Thanks!

[JoelBVezina]

@sebastienlevert I'd like to know if there is any hope this being addressed in the future. We would like to be using mtg-person more but I have a hard time pushing this solution to any organization not working exclusively in english.

Thanks!