[ using C# with WindowsForms ]
Hi,
I think I've read everything there is to read about localization in dotNET
and I still don't get it.
I understand the concepts and I understand the code, but there's no way that
the scenarios described can be translated(!) to a real world application.
Here's what I got. I have forms with controls on them and I have constant
strings that I show in message boxes and the like.
The forms and controls I can neatly handle in the designer, just by changing
the langage name in the property pane (which behind my back is then stuffed
into some resource files). For the constant strings I need to create my own
resource file (e.g. a key/value type) and then load the strings with the
ResourceManager.
Here's my problem: I'm about to release a v1 of my application. So I send
all the resource-files to the translators, who in turn translates the files
and send them back. A while later I'm about to release v1.1. and... now
what?
It seems that I have to send the the same resource files again to the
translaters, who have to start all over translating what they have already
translated for v1 and continue with v1.1 - a complete waste of time...
There must be something that I have missed during this "cycle". There must
be some (simple) way to split the old and new resources, so I only need to
send changed and new text to the translator. How do you do it??
What I'm really after here, are some of your technical experiences working
with dotNET applications and (third party) translators.
Regards,
Sebastian