External locale files

[aaronchantrill]

Detailed Description

Right now, the only way to provide a new locale for an intent is to edit the plugin directly. I would like it to be possible for someone to provide a new locale for an existing plugin without having to edit the plugin, then make it available on NPE for other users to download. This should be straightforward enough that someone who is bilingual would be able to create a new translation for both the intent templates (input) and the gettext (output) portions of a plugin without touching or knowing anything about the python code.

Context

As a plugin author, I would like to develop plugins in my native language and not worry about other locale's. I would like other people to be able to contribute translations for my plugins in their own native languages, and then make those available via NPE. Ideally, NPE would list the available languages before you install a plugin and download the proper locale automatically based on the language setting in my profile.yml.

Possible Implementation

For a possible implementation, view skills built for Mycroft . These have a locale directory, containing separate directories for specific locales, containing keywords, input templates and output phrases. I'd like to see NPE automatically associate locale files with plugins. I'd like to see some kind of version or release matching. I'm not sure how to keep up with changes the author might make to the plugin templates. A combination of allowing an old version of a locale to be used with newer versions of the plugin until the locale is updated, along with automatic notifications to anyone who has contributed a locale for a particular plugin would probably be okay. There may also be ways in which we could flag a change to a plugin that requires a locale author to update their work.