title: How to best organize translation strings in angular-translate?
body: <p>I am using angular-translate on a rather large Angular project. I am breaking the project into multiple modules to make it more manageable, but I am unable to break up my translation strings per module. </p>
  
  <p>For example, I have modules A and B, where B is a submodule of A. There are strings that pertain to the HTML covered by module A, which are placed in '/json/localization/A/en.json'. Likewise, there are strings pertaining to B that I place in '/json/localization/B/en.json'. First I load B's en.json in module B using angular-translate's $translationProvider. Then I load module A's en.json, also using $translationProvider. The problem is that loading A's strings overrides B's strings and they are lost.</p>
  
  <p>Using angular-translate, is there a way to load strings per module, without overriding, or does the parent module have to load all of the strings from a single en.json?</p>
  
  <p>Here is an example (in coffeescript) of how I am loading the translation strings:</p>
  
  <pre><code>my_module.config(['$translateProvider', ($translateProvider) -&gt;
    $translateProvider.useStaticFilesLoader
      prefix: '/json/localization/A/'
      suffix: '.json'
  
    $translateProvider.preferredLanguage 'en'
  ])
  </code></pre>