Hat tip to @jhodgdon for finding this.
The ContentLanguageSettings config entity cannot be translated because it does not have a dedicated edit form. Instead all of the content language settings are edited on a single page.
Because content language settings do not have any translatable settings in core this is marked minor and also not tagged with sprint. However, because content language settings support third_party_settings contrib modules could add translatable values there and expect to be able to translate them with the Config Translation module.
Create a ContentLanguageSettingsMapper which adds all the content language settings config entities.
Add a Translate tab to the Content language settings page. This will only ever be shown if there is a module which adds translatable third-party settings to content language settings.
None.
None.
Active
10.1 ✨
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I tested this on Drupal 10.1.x and yes, there is no translate tab at /admin/config/regional/content-language. I installed Italian and went to
it/admin/config/regional/content-language and the strings were translated. And they can be translated at admin/config/regional/translate. So, I have updated the title. Since the strings can be translated I am changing this to a task.