Description:
One thing I think could possibly be useful is having a DB table with this structure:
modulename, key, english, trans1, trans2, ...
all columns are string.
And it would be accessible from core.
Current behaviour: Tell us what happens
Adding translations to C++ is not really good (code and chinese doesnt mix well).
Existing tables use integer keys and cause collisions and maintenance issues.
Expected behaviour: Tell us what should happen instead
Support translations for modules with no collision problems.
Also since the module name is a separate column it is easy to find/modify/delete translations belonging to specific module.
Steps to reproduce the problem:
Branch(es): 0.x / 1.x / master (Specify the branch(es) affected by this issue)
AC hash/commit:
90ed2548c071c1b6a0733042806aa356364ab674
Operating system:
Modules: Are you using modules? if yes, list them
Other Customizations: Are you using any core/db patches or other customizations? If yes please specify them here.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Sounds good
This sounds like a good idea @Rochet2 maybe another thing we could look at is transferring the module conf to database aswell if you think this could work, that way the module can be enabled/disabled through the database instead of having to alter different conf files.
module_name,id,option_name,option_enable... this way it will all be database driven

Working on this as we speak will do a PR if people want it to be merged :) Still a WIP
funny thing is, this is also going to be a module so it gives the players the option :) making hooks and that to make the module work correctly.
Nice ideas