Provide facility for machine translation of resources.json in a separate project

[MrCsabaToth]

Here is a simple node.js app, it uses Google Translate:
https://github.com/gdgfresno/translateResources/

I generated Spanish, Hmong and Armenian translations for ValleyDevFest 2016 to support our largest local ethnic groups.

[MrCsabaToth]

BTW, it'd be good to have the language selection popup on the top drawer too

[ozasadnyy]

@MrCsabaToth, looks interesting! How can we integrate this into Hoverboard?

[MrCsabaToth]

The best would be to make it part of the build process. Since if you add a term only into the en resource (but not the other ones) the page/site stops functioning. I didn't look at yet how I could make this part of polymer's pre-build process. Right now it's a node app, and the calls are simple translate calls (no API key needed). In my app I had Spanish, Hmong and Armenian translations.

[MrCsabaToth]

Thinking more: this machine translation probably should not overwrite non machine translations, so probably we need to protect those entries in the resource file somehow. So we need to think more about that.

[ozasadnyy]

Seems like time to use custom build for Polymer CLI

[MrCsabaToth]

Since resources.json is not a flat key-value pair list any more, I need to enhance the translation script first.

[ozasadnyy]

@MrCsabaToth can you make script translate only string values?

[abraham]

This sounds neat but it's implementation will be very dependent on #454. Seeing as this is so old I'm going to close it. Once #454 is completed if there is still interest a new issue can be created.