I experimented with changing the interface language and target translations to Albanian, Bosnian, Bulgarian, Czech, Greek, Hungarian, Polish, Russian, Serbian, Slovakian, Slovenian, Romanian, and Turkish.
The results are as follows:
The UI works in all tested languages.
Automated content translation works in: Bosnian, Russian, Turkish, Polish, Czech, and Romanian.
Automated content translation to Albanian, Bulgarian, Greek, Hungarian, Serbian, Slovakian and Slovenian produces an error message (see the picture).
Just to understand the testing better. You changed your Interface Language to Albanian etc and then you tested to translate from i.e. English. Correct?
Is anyone else getting this type of error?
PS: Another possibility is that you hit the limit of the setting “max translations per minute - The number of translations per minute a regular user can perform.” (set to 10). If this is the case, the error message should be clearer.
The problem appears when you try to translate content into the previously selected UI language.
Here are the error messages you get when you set the UI lang. to (for example) Hungarian and Serbian and then click the translation button to translate the content.
Note how the “ok” button language is displayed correctly.
One issue here is that apparently the Google API is called with an invalid target language - not sure if this is a bug in the plugin, or you are just using an unsupported language (although in that case ideally it wouldn’t even offer auto-translation).
The other one is that this error message is really useless for a nontechnical person. It should be prefixed with something human-readable (and translatable) about how the translation failed and please report a bug.
The Discourse team contacted me saying that they are looking into this problem. For some reason they have unpublished the post and they are following up in a private thread (I think it is just because of our current contract with them, not for security reasons).
Google Cloud Translation doesn’t seem to support Twi. Translation requests for non-supported languages should be handled more gracefully than a popup with raw API response; that’s a bug in the Discourse plugin, I think.