Update GoogleTranslate module

[Prasanta-Hembram]

Description:

The Linguist extension's Google Translate module likely relies on a static list of supported languages. As Google Translate's language support is expanding and needs to be updated manually regularly. Below are the sources where supported languages are updated regularly (even before google list them in their official website :-)).

• Google Translate now supports 249 languages. Ref: https://en.wikipedia.org/wiki/Google_Translate#Supported_languages
• 70 languages by speech. Ref: https://en.wikipedia.org/wiki/Google_Translate#Supported_languages_by_speech

[vitonsky]

What this issue about?

[Prasanta-Hembram]

What this issue about?

I have updated, sorry forgot to add description and lack of clarity.

[vitonsky]

@Prasanta-Hembram thanks for update. Linguist uses languages defined in ISO-639-1 standard, but not languages supported by google, since Linguist is not just wrapper around Google rather it is replace for google translator.

What a reasons to add Languages into Linguist? Do you have some specific problem with languages list?

[Prasanta-Hembram]

All those languages are not available in Linguist GoogleTranslate module, example Santali is present in defined in ISO-639-1 standard, but not in Linguist extention. If I have to update/add langauge like Santali to GoogelTranslate module how to do it.

[vitonsky]

@Prasanta-Hembram as i see there are no this language in vesrion 1 (2-letter code): https://github.com/vitonsky/ISO-639_langs/blob/a3611a49b8f6bb369734a03b36fa161114cce4ac/ISO-639-1/data.json#L2725-L2731

If this is incorrect and you have links that confirm it, we have to fix it.

Otherwise this language will not supported even if any translator support it.

This design decision is motivated by factors below

• We have to localize languages Linguist support. Currently we set language names in localization files. As alternative way, it is possible to generate localized strings with Intl - browser API and in case we can't translate language - we should hide it, that may lead to inconsistency between browsers depends on languages list they support
• 3-letter codes are confused and may have few codes for single language
• Most sites uses ISO-639-1 for language definitions, so we have to map v1 language codes to v2 while translating, since if we would support 3-letter codes, some translators may use 3-letter codes in list of languages they support