The simplest solution is to change the translator property from a string to an array, and make it accept multiple translations, this doesn't break backwards compatibility and adds the feature of being able to scan multiple languages (PHP, JS, templates, etc).
Pull request is here: #1229
@Arne-S you can link issues on github like this to auto create a backlink on the other side: #1229
Enh #1228: Added ability to MessageCommand to generate translation fi…
…les for multiple functions
Unit test case for issue #1228 has been added.