Is production mode translation intended to work with more than one locale?
I’ve been looking at the way the translation plugin is implemented in JMVC 1.5 and how a file (en_US.js) with a ‘Translation’ JSON is included by app init.js, which can then be compressed in production.js, but am wondering how this can be switched for other countries. Like if I hit the webapp from Canada (fr_CA.js) or Mexico (es_MX.js), these alternate locale files would not be present so can’t be changed to. My workaround is to NOT include it by app init, but to add a script tag to the bottom of my HTML wrapper page which ‘includes’ a particular locale file by writing the path to it using a variable from the request… But I’m looking for a best practice for this sort of thing.
