Big suggestion
There are many excellent features in your product (i've just tried it), but also some negative ones that prevent me to propose it in my company. So, please take this as (positive!) suggestions.
Indeed, working for along time with localization/globalization, what we really miss in your software are the lack of support for resource-based classes, ie the classes that you can generate automatically in VS.NET through the ResXFileCodeGenerator. In corollary, the name of the resource you generate (_XXX where XXX are figures) are not at all intuitive - why not rather use the same naming mechanism as in ResXFileCodeGenerator?
These 2 suggestions may look little, but they really allow a team to reuse on the fly the existing translations while adding new code, rather than adding new resources (new strings) that the code or another person will have to translate later on...
Hope you will implement these shortly as, apart them, your add-in looks very useful!
Best regards and Happy New Year (in advance)