it's not 100% true that no integration into VS is needed.
Before compiling, there should be at least a check if all UID's are set.
After compiling, the satelite assemblies needs to be generated as well. ELse there might be unexpected behaviour/appearance of the UI.
Currently this is done by pre and post build steps, which gets automatically added to the project by my tool.
May be I can find an easy way to maintain an plugin and a standalone tool.
About the editor:
The filter issues are known to me. Sometimes you need to clear the filter and set it again to work correctly. This seems to be some WPF issue.
Comfort functions will be added over time by it's needs.
There is also an standalone editor planed, so external people (or at least non developers) can do translations as well without any knowledge about the VS project.
Then there will be an auto translation feature, where everyone can implement it's own providers. So you could write a provider for Babelfish online translation (if that is possible) or anything you like.
But my time to work on this is limited, and the missing feature list is long.
To be honest, I havn't used it by my self so far. But soon I will need it.
Please be aware that I have to change the way how additional properties are stored in the project file. But I will add an automatic conversion feature.