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

Comments

Gábor Hojtsy’s picture

Issue tags: +D8MI, +language-config

Quoting your issue summary text with emphasis from me:

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.

So if a given view may have human language text in there then how can the schema say it is not translatable? Looks like it would depend on the contents of the config file, not the schema of the file, right?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.