I have a enhancement request.
It would be nice to have the possiblity to create translation of one extension with a special context.
For example:
When we create the ts files of our cjw_newsletter extension we get all ts context information of all i18n operators of cjw_newsletter.
But i am overriting standard admin tpls. This tpl has standard translations. But i do not want this ts context infos in my cjw_newsletter ts files.

May be it is possible to have a parameter to only add defined i18n context infos

./bin/linux/ezlupdate -e extension/$EXTENSION_NAME ger-DE --utf8 --context="cjw_newsletter:context2;..."

{"Send Test Newsletter"|i18n("cjw_newsletter/send")}

So i can use standard translations and do not spam this to my cjw_newsletter ts files.

This would be a very nice feature.
Thank's