Add a localizable but not translatable concept to config schema

Created on 30 March 2015, about 10 years ago
Updated 7 May 2025, 3 days ago

Problem/Motivation

As discussed in #2457703: Default translatable site name is "Drupal" (incorrectly) β†’ , there are strings that can be different per language, but not translatable. One example is the default site name "Drupal".

The referenced issue solves this for now by removing the default value from the config file, which prevents the localization system from providing a default translation.

However, there are more strings like that, for example, views configuration has things like the multi-field separator, that by default is ', '. It could be different per language, if you actually use a word, but by default, it is not.

Proposed resolution

Introduce a type of flag for config schema to mark strings like that and have them ignored by potx. Nothing else should change.

Remaining tasks

User interface changes

API changes

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

configuration system

Created by

πŸ‡¨πŸ‡­Switzerland berdir Switzerland

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 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!

  • πŸ‡¨πŸ‡­Switzerland berdir Switzerland

    Still an issue IMHO

Production build 0.71.5 2024