Issues with Globalization/Culture in .Net 2.0

  • Thread starter Thread starter Sajit
  • Start date Start date
S

Sajit

Hi,
Could anyone provide any suggestions on how to implement localization features for a multilingual website. Before you jump the guns, let me define the site structure a little more. We have a global site and around 40 country sites. Each of these country sites have localised information both in the native language (fr,de,de-at,it,ar,ar-ae etc). Also, each of these local country sites would have an english counterpart (fr-en,de-en etc). Currently, we do not see how we could define the resource files for the english version of the regional country sites. The issue being that there are no 'cultures' defined as 'fr-en' or 'en-fr'. Is there any way we can map an existing resource file somewhere within the server and use it within my application without copying the files to my App_LocalResource folder?

Also, is there any way we can specify the culture to be used for a page from within a user control or vice-versa. The way we see it, you have have individual resource files for both the page and the user control (and no, using the App_GlobalResources folder is not an option at the moment)

Hope you get the idea. Any help would be greatly appreciated.

Regards,
Sajit
 
Patrice,
You may want to explain why you need "localized english" cultures in case
someone would have a better solution for the problem you are trying to
solve...
Click to expand...

By instance because that you want the use a date.
These are different between the USA and the rest of the English speaking
world. As sample "September 11" and "11 September". As well would I prefer
not to show an Englishman/woman words as color etc.

Localization is nice, but at least I cannot get the globalisation
information from the normal webpage client (without and active X or
something). You can very easily get the used language, but that says nothing
about how you have by instance to write a date.

Therefore I am as well curious about the answers.

Cor
 
This is more or less the kind of things for which I think there are other
solutions than creating additional cultures (for example it could be
possible to just "map" each country to a en-us or en-gb preference). Also
AFAIK the .NET framework differentiates the culture used for localized
strings and the one use for numbers, dates, hours etc... formatting (i.e :
it could be even possible to mix english and keep some local rules though it
could lead IMO to possible ambiguity (is 1,500 in "French English" 1 500 or
1.5 ?)

Hopefully the OP will give some explanation if he's not totally convinced
that he really have to create all those additional cultures...

--
Patrice

Cor Ligthert said:
Patrice,
You may want to explain why you need "localized english" cultures in case
someone would have a better solution for the problem you are trying to
solve...
Click to expand...

By instance because that you want the use a date.
These are different between the USA and the rest of the English speaking
world. As sample "September 11" and "11 September". As well would I prefer
not to show an Englishman/woman words as color etc.

Localization is nice, but at least I cannot get the globalisation
information from the normal webpage client (without and active X or
something). You can very easily get the used language, but that says
nothing about how you have by instance to write a date.

Therefore I am as well curious about the answers.

Cor
Click to expand...
 
Localization is nice, but at least I cannot get the globalisation
information from the normal webpage client (without and active X or
something).
Click to expand...
CurrentUICulture is for localized content and CurrentCulture is for
formatting date/number/time, sorting, etc.
 
We need localized english content because the local country sites would have content different from the Master English site. Each of the 80 odd sites (in the corresponding local languages as well as their english counterparts) will have localised content. This is because of the fact that the business users/designated agencies world wide would be updating the content using our content management system. We have about 90% content pages and about 10% application pages. We are trying to implement the resx files for the application pages. The content pages would be published directly out of our CMS.

The resx files would hold the text to be used in labels, alerts and instructional text. The instructional text could vary from site to site. For example, the instructional text used in the English version of India/Australia sites would vary from the ones for UK/US.

Hope you get the idea.

Regards,
Sajit
 
Back
Top