Import translations into seperate files

[fabiulous]

Is there a possibility to import translations into seperate files like fr.json, es.json, it.json and so on, instead of importing everything into translations.js?

This would allow using Async translations easily

[francescarpi]

Hi,
is not possible now, but I'll consider it in the next develop.

Or you can send me a pull request ;).

Thx

[fabiulous]

Sure, I was playing around with it to try and accomplish it, but I got into some questions.
If I import this into separate .js files, how would I fetch these files on demand? Point is, I don't want to bundle 1mb of translations.
If instead I turn it into a .json file, then I can just have them in a public folder and just fetch it when needed, but it will be a bit weird that one options imports into .js and the other to .json

What do you think of this?

[stayman]

@shizpi, we generally get around this problem by sending back only a portion of the js file at our server layer by reading the accept-language header of the request.