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.
Comments
Comment #1
Gábor HojtsyQuoting your issue summary text with emphasis from me:
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?