Load i18n files using promises, not callbacks about ghost

[matthojo]

Personally I think the i18n should be JSON, keep the database cleaner.

It may also improve the development learning curve for themes / plugins as there will already be an example working JSON file.

[cgiffard]

My vote is to keep it JSON. Then if you want to internationalise your module, you just create an i18n.fr.json and leave it in your module directory (alternately, mymodule.i18n.de.json, perhaps).

Then you uninstall your module and the localisation is gone. No cruft left in the DB.

But I also think that the i18n module should do a recursive search of localisations with a given key, enabling module developers to more easily localise their modules using terms that already exist in the system and have translations available.

[hugomano]

+1 for JSON as a module/plugin. For edit our translations it's more simple.

[twinsant]

+1 for JSON

[ErisDS]

Closing in favour of #3801. The original plan we had for how to do this is defunct now and needs a new approach.