#2 Translation key enhancement
As far as I have understood, there is a simple string key
to identify translations.
If I want to use Esperantus in a multi-project, multi-
module, multi-developer environment it will be difficult to
make sure that everybody uses unique keys.
I propose to add a new field "Module" and create unique
keys based on Module+TranslationKey.
I know it's possible to build key by concatenating the
module id and the key and use the current system but I
don't think it's a good idea because: 1) it's not possible
to load or delete all translations for a given module in a
secure and performant manner.
The side effect is that it will be more convenient to
translate because you work with translation sets and
this allows more coherent and efficient translations.