Allow configuration settings and entities to be translated.

I kind of felt this was a phase 2 feature because I am not sure what the best approach is.

For example, should the I just pass all strings through the translate function or do I allow the YAML form and YAML form options config entities to be translated.

I do almost no work using translations, so I think someone might have to step in and help build out this feature.

BTW, if passing all strings though the t() function could be a partial/temp solution, I could probably do it.

You bring up a valid point about email, it starts to seem like the entire YAML form has to be translated. A better work around might to be to create a duplicate form for the translation and direct the user to the correct form based on the user's current language.

I did a quick test and my configuration entities (ie YAML form and YAML form options) are not translatable when I assumed they would be. I will look into this issue and try to figure out the best approach for translating the input labels, descriptions, and options.

Okay so my config schema was not translatable, basically everything was strings instead of labels and text when application. https://www.drupal.org/node/1905070

I am going to update the main ticket and start fixing things. There is a lot of config files that need to be reviewed so this going to take some time.