Allow filtering/configuration of which languages apply to what (UI, nodes, files, etc)

Created on 19 October 2011, over 13 years ago
Updated 25 March 2025, 15 days ago

In Drupal, we aim to provide a generic language list, but in effect, people use languages for all kinds of things, and which languages from the general list are applicable to which operation are not possible to define.

Some examples:

1. Site wants to track English (US) and English (British) content separately. They don't want to have user interface translation for them (even if they have other languages, they want to have UI translations for). This means their list of languages for UI and content are largely overlapping but not equal.

2. Web application wants to offer its interface in various languages (think google search), but help pages and documentation on the web app will be available in a limited set of languages, and no intention to offer more. Language switchers in the documentation area (for content) would show less languages compared to the language switcher on the web app. Content language assignment should not show irrelevant languages.

3. A web site wants to expand into more languages, and while the new language pages are built out, they obviously don't want their language switcher links to show the soon to be added languages, so users are not confused that the content is not there yet, since its unpublished or permissions to be only seen by QA stuff at least.

To support these use cases, we'd basically need to refactor the "enabled" bit on languages to be a set of feature specific bits. Whether this language is enabled for UI translation (also very useful for #1266318: Make English a first class language where we are attempting a stop-gap solution for now), whether this language is exposed in language switchers, content language assignment, etc.

Related Issues

Feature request
Status

Postponed: needs info

Version

11.0 🔥

Component

language system

Created by

🇭🇺Hungary Gábor Hojtsy Hungary

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • D8MI

    (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.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024