Marcus Spiegel

loading from multiple sources is not (yet) supported

reading (globbing) and merging files is only one thing. Using the glob package would ease any kind of implementation, totally agree. Do you have any more thoughts of the implementation...

ya, reading, merging is no prob. My concern is about writing those files while maintaining backward compatibility with any combination of those options: ``` js i18n.configure({ // watch for changes...

another (better?) option could be to split phrase and namespace with an extra parameter... or delimter, imaginable like so: ``` js __('admin|mysection.greetinig') __('frontend|mysection.greetinig') // or even __('frontend/mobile|mysection.greetinig') ```

Ok, got it :) Still we need a little change in writing - by now a write serializes the whole catalog to get written in one file. To change I...

If you prefer a static/manual way to manage those, why not setup any kind of external build that combines your multiple sources into one single json file to provide translations...

a gulp step should be quite easy to setup and integrate in any existing pipeline

as i18n config & init will only run once on startup I wonder how you planned to add modules at runtime... anyway, with i18n's option: ``` autoReload: true ``` set...

@chamerling: calling i18n.configure() and/or i18n.init() would trigger a kind of "manual reload" anyways. Still not reading recursivly... but this is what we discussed earlier

this is how test cover autoreload. Check out https://github.com/mashpie/i18n-node/blob/master/test/i18n.configureAutoreload.js to get an idea. It's basically accomplished by configure autoreload and write json files after startup. I'll take a dive into...