CODEWITHSUNDEEP
asp.netlocalizationinternationalizationglobalization
met.lord
met.lord

Reputation: 618

Globalization and Localization: When? How?

I'm researching a little about different ways to do Localization and Globalization in .NET as I was asked in my job to do it. However, I've been reading lot of posts about those topics, and I don't think that doing Globalization nor Localization is the best option for us:

Apparently bosses' plans are to duplicate the app in many servers as they need with different domains (.com, .es, .co, etc.) in order to use it in many different countries. As I see it, and please correct me if I'm wrong, doing that would imply that there's no need of Globalization nor Localization, because instead of having one application running and accepting different localized resources you will have many different apps running in different servers with different and exclusive resources...

Does it make any sense to implement globalization and localization if they're proceeding this way? Please help me clarify my thoughts.

Thanks in advance,

Upvotes: 1

Views: 578

Answers (1)

Jeroen
Jeroen

Reputation: 4023

I would definitely implement localization and stick to 1 code base as much as possible.

You can deploy the same project to different servers and set a fixed culturecode if you have to or let it depend on the user's browser.

Just splitting your code because you want different languages without a localization mechanism is a bad idea. It will be horrible to maintain.

I have 1 project running for different clients on different domains with slightly different functionality and different languages and i am still sticking to 1 code base for all of them.

Upvotes: 3

Related Questions