Hi,

I have an application which is going to need to be localized. It's
been trivial to use the ResourceManager to enable me to store all my
in-code strings within a text file and simply compile it to a resource
DLL, having one for each language.

What I'd like ot know is if there is an easy way to manage the
localization process with Windows Forms - i.e. they obviously have
strings that need to be localized, and are stored in the corresponding
..resx file for each Windows Form, however, so are all the other
resources for the Form.

What I'd like is a way to get all the strings for the whole app -
across code files and each Form - into one big text file/database and
then be able to send that away for translation.

Is there an easy way to do this that I'm missing? Or is it the domain
of custom solutions and 3rd Party Apps?

Thanks

Simon Kittle

Hi Simon Kittle,

[quoted text, click to view]

I think there is a big domain for 3rd Party apps! But I do not know of any
good system (expect of our own implementation).

--
Greetings
Jochen

My blog about Win32 and .NET

[quoted text, click to view]

Try to Google something like "windows .net localization tool" or ".net
software localization tool".

--
Check out also Developer Zone at <www.multilizer.com/dev>!
Code snippets, technology backgrounders, how to's, etc.

Heikki Korpisalo
Multilizer Oy

Hello Heikki,

One good option is to gather all localizable resources (UI strings and
exception strings) into one single text files, that you would then compile
into a .resources file using resgen.exe, which is available in the .NET
Frameword SDK. For details on how to use resgen.exe and create .resources
files, you can refer to
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptutorials/html/string_resources.asp.

Also, here is a good articlet that explains another solution on datase based
localization. http://www.code-magazine.com/Article.aspx?quickid=0501081.

Hope it helps,

Kanako Koizumi
kanakok@online.microsoft.com

-Please do not send email directly to this alias. This alias is for
newsgroup purposes only

[quoted text, click to view]

Looks just like one explained at
http://www.multilizer.com/dev/database/row_localization.asp. Personally I
like this technique; It has the most elegant data structure, adding new
languages is very easy, plus you can use prepared queries to switch
language - no need to change the query string but only one where clause
parameter - fast and easy.

--
Heikki

The way I'm doing it is using resources.

I suppose I didn't want to use the database method because then I
presumably have to have code in the _Load() method of every single form
to set all the strings according to language where as with resources
that just happens automatically.