Language Picker Multi-Lingual

Marc George 21

Using the Xamarin Forms Picker control, I had been able to create a Languages picker in which I had every language supported by Azure listed with its name translated to its language for selection. That functionality has disappeared; now every language name displayed is displayed in English. Is it not supported anymore or is there a new parameter(s) that needs to be set?

Marc George 21 Reputation points

2020-12-25T12:20:19.12+00:00

@JessieZhang-MSFT Thanks for the pointers, but they don't seem to provide an answer to my issue. My app's UI is already dynamically multi-lingual using Azure Cognitive Services. On initial startup, it determines if it has been previously initialized. If not, it immediately downloads all supported languages which are placed in a list. The list is then iterated, the language name translated to that language and added to the picker:

In the past, the picker would display the list of language names in their actual language. It doesn't anymore; the list is in English despite. That is what I am trying to fix.
JessieZhang-MSFT 7,706 Reputation points Microsoft Vendor

2020-12-29T07:23:06.733+00:00

Could you please post a basic demo to github or one driver so that we can test on our side?
Marc George 21 Reputation points

2020-12-29T15:57:41.01+00:00

The requested issue was created: 1811
JessieZhang-MSFT 7,706 Reputation points Microsoft Vendor

2020-12-31T08:16:16.617+00:00

Hi @Marc George ,did you make any changes to your app before this problem came up?
Marc George 21 Reputation points

2020-12-31T13:28:53.697+00:00

Looking back at app versions, to the picker provisioning code no. To the rest of the App code, for sure.

However, in investigating over the last day or so, it appears that one function of the CognitiveServices class has been modified and another added at some point since I originally wrote the code segment. TranslateToText(string text) was modified to be async and SelectLanguage(string language) was added. I see the both having major impacts. TranslateToText immediately returns the text to be translated untranslated if not awaited and App.activeLanguage no longer being the the specifier for the translation to a language, being replaced by SelectLanguage.

I have been trying to implement them, but running into a new issue of exceeding the GREF limits in doing so.
Marc George 21 Reputation points

2021-01-02T01:33:55.683+00:00

@JessieZhang-MSFT

After digging very deep and performing a thread syncing analysis, discover that the Cognitive Services Authentication component that establishes the necessary streams was no longer completing its task before the initialization process of the picker. Therefore the translation was not being performed. The default for no connection is the use of the English based languages collection. Controlling the tread executions enable the goal of a multilingual picker.

This case can be closed.

1 answer

JessieZhang-MSFT 7,706 Reputation points Microsoft Vendor

2020-12-24T07:41:14.417+00:00

Hello,

Welcome to our Microsoft Q&A platform!

Have you check Cameron's article Add Languages to Your Xamarin Apps with Multilingual App Toolkit here?

And I tested the sample LocalizationSample included in above article on my android device, it works properly.

Make sure to add different language resources(e.g. AppResources.resx) to folder Resources.

When we changed the language, the text shown above will change accordingly.

Besides, above sample use nuget Plugin.Multilingual, and we find that the nuget has been deprecated.

As a new approach, you can check article Handle Multilingual in Xamarin Forms (Without any plugin). In this article, it will show us the simplest way to add multi-lingual support to our app.

And we can check the full source code here.

Best Regards,

Jessie Zhang

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment