Problem/Motivation
Per Gabor in https://drupal.org/node/2272363#comment-8822223 I implemented translatable configuration in a way how it was not intended by the design. What a lot of people need is the ability to have configuration per language. As maintainer of a Google Analytics I thought this is the way how I can allow my users to use independent UA codes per language. We had this already implemented in D7 with variables module.
Proposed resolution
Allow definition of translatable settings, but also block POTX from extracting them as translatable string to l.d.o. We could add a new key like translation_export: false to help POTX.
account:
type: string
label: 'Web Property ID'
translatable: true
translation_export: falseRemaining tasks
Write patch.
User interface changes
None
API changes
Maybe