What bugs are you talking about? Currently there are no open bugs, just feature requests. If you think something is not working as expected, please create a new issue at: https://resxresourcemanager.codeplex.com/workitem/list/basic
Discovered this recently, and it has quickly become an essential tool. It has all the features I need for managing my resource file-based localization needs, without being too bloated. It feels like a tool that could be part of the base Visual Studio install.
Love this tool. Makes it very easy to look at all your resource strings and see what languages still need to be translated. I absolutely love the export option, as when translations are required I am required to provide an Excel file. Thank you Tom!
Nice tool on the first look.Have just started and clicked a little bit around.
As i added another language i got an exception inside of Visual Studio (but the file was created and the second change to the file was saved). I will test it on another PC and report an issue if i can reproduce the error.
I found your extension very useful, thank you. In my project we have a separate person who manage strings and translations but he doesn't know visual studio. Currently we use export/import excel feature -> copy/paste google sheet but we faced on with a merging issues. When translation manager update string and developer add new string we should merge it manually. We use comments like "edited" or "new %date%" to help us. I plead you to create next features which will extremely increased popularity of your plugin:
- update project resources based on google sheet
- update google sheet based on project resources
- resolve conflicts window which simply ask you two options use google or use project string
If you think this idea useful I can help you with it's implementation
This plugin is really, really, really great but I have issues. In my project there are multiple resource files with the same name in different sub directories. Actually named Locale.resx -- it's just the way it is. While ResXManager seems to work anyway, and the excel export in a way works as well, the excel import screws everything up. Is there a way to switch from "FileName" to "Namespace+Class"? While file name may not be unique in a single project, a Namespace+Class must be. Or include the sub directories within the project, not just the file name, that makes it unique as well.
Do I need to have ms office installed for the export to succeed ? The export do not complain, the file is created and when I open it with open office I can see as many tabs as selected files, but each tab is desperately empty... Could somebody help me ?
Please do not report bugs here! Use https://resxresourcemanager.codeplex.com/workitem/list/basic
#1: It's just the image that's wrong, will be fixed in next version.
#2: What translation service are you using? Does it work if you use the same service online?