My customer has 140 German resx files in different folders that he wants us to translate.
He wants us to provide culture specific resource files (en-gb) and has provided us with “Windows Resource Localization Editor” to translate the files with.
He wants the culture specific resource files to only contain strings we translate and anything we don’t translate will fallback to the Neutral/Default culture being the German resx file.
This seems to work well in the “Windows Resource Localization Editor” as only edited/translated strings are added to the translated resx file en-gb.resx
The problem is that we don’t want to use “Windows Resource Localization Editor” as we want to use a tool that allows for side by side translation and utilizes Translation Memory so we can stay consistent when translating the Help and Doc.
Most of the localization tools that we want to work with would just import the Neutral resx and output a copy of the Neutral file but with the strings translated. But as I said the client doesn't want to have too much unnecessary information in the culture specific resx.
My client doesn’t know much about the localization capabilities of Visual Studio and I don’t know anything about Visual Studio. When we have translated for other clients in the past they have just provided us with en-gb.resx files that only contained translatable strings that they wanted us to translate.
So here are my questions.
1. Is there not a function in Visual Studio that will allow my client to automatically generate en-gb.resx files that only contain strings for translation? If there is can you advise step by step so I can forward the instructions.
2. I suppose this question depends on the answer to the previous question. If the client can provide us with the above is there anyway t for them to remove duplicate strings that we didn’t have to translate. e.g. strings that contain product names and or web addresses, e-mails etc? I think they are just trying to keep their code as clean as possible
3. Finally, if the client later wants to create an en-us version, would it have to be a complete copy of the en-gb version with a few strings changed or could they have a en-us version that only contains strings that differ from the en-gb version?
Hopefully someone will know what I am talking about.