I have been developing multilingual applications (winforms and web) for many years and whether you're working on a large scale application or a small application it's always recommended to have your localized variables away from the fixed ones meaning:
Entity:
ID
IsEnabled
CreationDate
LastModificationDate
Entity_Localized:
ID
Name
CultureCode
RegionCode (if required)
Now in your C# Code, You could have the properties translated according to the current culture so that you have on property called Name and you would have to add the Culture param to the entity related methods such as GetEntity(int id, Culture culture)
This would really give you a good scale of performance and maintainability as you could easily add support for more cultures in the future.
Please Mark as Answered if this post helps you.Your 'Mark' will help other people having similar problem.
gsaadeh
Member
736 Points
141 Posts
Re: Multilingual database design approaches
Oct 25, 2011 04:32 PM|LINK
Hi Dave,
I have been developing multilingual applications (winforms and web) for many years and whether you're working on a large scale application or a small application it's always recommended to have your localized variables away from the fixed ones meaning:
Entity:
ID
IsEnabled
CreationDate
LastModificationDate
Entity_Localized:
ID
Name
CultureCode
RegionCode (if required)
Now in your C# Code, You could have the properties translated according to the current culture so that you have on property called Name and you would have to add the Culture param to the entity related methods such as GetEntity(int id, Culture culture)
This would really give you a good scale of performance and maintainability as you could easily add support for more cultures in the future.