Setting translation to one language only

Hi,

I wanted to test the automatic translations for one language only. My default is English, and I want to enable users to change interface and content lg to German.

The interface works fine, the switcher shows only German as the other possibility. But when it comes to translating the content (topics/posts) all the laguages are visible in the drop-down list for the users. I have all my settings made for German only, but still, I cannot limit the languages for the content.

I think this might be confusing for the users, that even though we show only German in the interface, then they have the possibility to choose any other language for the content. When choosing the other languages (eg. when I select French), the behaviour is that it either gets translated to French, or switches back to English.
Please let me know how can I limit the content translation languages to one only.

Thanks!

Marzena

Can you share a screenshot of what you mean by this?

Content languages (and automatic translations for user-generated content) are a setting that only the admin can set.

User interface language (i.e. buttons and labels) are open to all users to set for their own usage, from their account’s interface preferences.

Please see the gif and my settings, I have the admin account. Can I limit the lgs that are visible in the Content Lg Preferences?

The other thing is that after the change, the interface lg switcher suddenly shows ES as well.

My Video-4

When you select French in your language preferences you see the Discourse interface in French. Since you don’t offer content translation to French the posts are not shown in French but either in their original language or translated to the forums default language.

I don’t think there is an easy way to limit the interface languages users can choose. There is a feature request for that Allow only specific languages

Hmm the header language switcher showing ES is not an expected behaviour, due to the ability to let any user set any language for their user interface. That said, this behaviour in the header is only shown to your user, other users should not see ES in the header.

@moin’s linked topic does feel like there’s some synergy with the content language features we have. Our team will have a think about it… :left_speech_bubble: