Spun out from bug 1048882. We should investigate using Gaia's L10n.js in Loop Desktop. Reasons: - Harmonise the L10n process for loop between the standalone client and the desktop. -- For consistency of translation -- For consistency of format of strings, e.g. plural forms - Possibility to share strings (at least from the en-US side) Issues: - Gaia L10n.js expects to load locale files via an xhr, this doesn't work for the content space that Loop is in. - There may be other hidden issues with using the Gaia L10n.js

ckarlof mentioned another possibility earlier on, adding him here for details.

Ah, I see you've already asked ckarlof for that info in bug 1000269; never mind.

I'd need more background on how Loop works, but for Node we support node's I/O - https://github.com/l20n/l20n.js/blob/gaia/lib/l20n/platform/io.js - will this help?

Associating with main Localization investigation bug.

Forgot about this bug - we did it in bug 1062835.