Clean-up code managing language type configurability

Created on 3 January 2014, over 11 years ago
Updated 25 June 2025, 17 days ago

Updated: Comment #0

Problem/Motivation

hook_language_types_info() allows to define additional language types to be used in the system. It also allow to specify predefined language negotiation settings for non-configurable language types through the fixed key. The name of they key is completely meaningless to almost everyone looking at the API docs for the first time. Additionally all the code managing language type configurability is extremely convoluted and is hard to follow even for the people that originally designed/wrote it.

Proposed resolution

  • Rename the fixed key to something more self-documenting, such as settings or config.
  • Clean-up the code that handles language type configurability.

Remaining tasks

  1. Agree on a solution
  2. Write a patch
  3. Fix failing tests
  4. Reviews

User interface changes

none

API changes

TBD

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

language system

Created by

🇮🇹Italy plach Venezia

Live updates comments and jobs are added and updated live.
  • 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 creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. 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