Internationalization of ASP.NET apps

Question

How do you guys handle translation/internationalization of your ASP.NET applications? How do you work with your translators?

We have ASP.NET apps that need to be ava

Answer 1

• Make your resource keys more meaningful. This will give them some context
• Can the translators get access to a running app? If so, you could set the tooltips of all your labels to be the resource key. That would allow them to mouse over a label to see where its string is coming from.
• As your translators become more familiar with the product, they'll be able to better cope with the lack of context. The first time around is a little rough, and you'll need to go through a few rounds of testing and translation revisions. There's not much you can do about it.

Answer 2

How about going around ASP.NET's insternationalization scheme and using a diferent approach, using .po files like the "rest of the world" . The actual text is the key, and translators see that text qhen they are translating. Works pretty well.

http://www.expatsoftware.com/articles/2010/03/fixing-internationalization-in-aspnet.html

describes this.

Answer 3

Here is the article written by Scott Hanselman. Hope it helps Globalization, Internationalization and Localization in ASP.NET

Answer 4

take a look at the Lingobit http://www.lingobit.com/