globalization

[Arie]

We have followed the globalization guidelines to implement ASP.NET
application on .NET Framework 1.1. When we published this application on US
XP machine with Spanish MUI, all the Date/Time columns on data bound grid
were displayed correctly with Spanish locale (dd/MM/yyyy HH:mm:ss). However,
when we published this same application on US Window 2003 machine with
Spanish MUI, the Date/Time columns on the data bound grid were still in US
format (MM/dd/yyyy hh:mm:ss tt). Please help. Thanks.

 

[Cowboy \(Gregory A. Beamer\)]

You can set the default in the web.config. I would personally head this way
for default.

For localization, I will generally pull the user's preferred language first.
It is sent as part of the request header. I will also allow the user to
override the language set in their browser and use a custom Profile object
to store this. If the user has set a locale in Profile, it gets precedence
over the browser, which gets precedence over the default language. You might
want to do this slightly different.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Blog:
http://feeds.feedburner.com/GregoryBeamer

*************************************************
| Think outside the box! |
*************************************************

 

[Arie]

Yes, we are currently setting the user’s locale language during the form
load. On 2003 machine, the labels/texts are translated as expected except the
date/time and numbers which still displayed with US locale.



We have also followed your suggestion to modify the web.comfig to include
<system.web> <globalization culture="es-ES"/> but unsuccessful. Please help.