Allow sharing localization between multiple projects

[tinganho]

There should be a way of defining base localizations that other projects can use.

[gwildu]

@tinganho we are thinking about implementing something to sync translations of npm dependencies that we have in our projects (that also would use l10ns). It would be interesting, to see, what your strategy is to solve this issue, so we could implement something that will be compatible with what you're going to develop. When done, we could of course share our solution.

We were thinking about translating the resources in the each dependency and then collecting the already translated resources from the dependency in the project and sync it with the project resources by syncing the json files by key and timestamp.

We were not sure, about the new flag and what the projects (plural) in the config means and how and if it will change in the future.

[tinganho]

Right now, I haven't thought so much about this issue.

But I will definitely take this up when designing v3 of l10ns. Though v3 is quite distant in the future right now. Mainly because of no time to develop, but it is also a huge undertaking, since the goal is to support multiple programming languages. And it must be rebuilt from the ground up.