Feb 04, 2011, 5:57 PM
[CLOSED] Urgent: Ext.Net's support for localization and internationalization
We recently introduced localization support for one of our large applications that uses Ext.Net in a major way. Introducing localization support for our application went well, and we added French as an option to application users.
During testing, a strange exception with DateTimes was reported. After some analysis, I found that a particular operation in the application was executing well with the english language, but gave the exception in French.
I was able to narrow down the problem with Ext.Net's DateField somewhere.
When Freanch is set as the browser language, the DateField's DateMenu shows month names in French. But there are 2 important problems with the implementation:
1) I selected 14 Nov, 2010 as the date, but it always automatically changes to 14 Feb 2010.
2) Even then after submitting the date, it goes to the server as you can see in the screenshot below:
I was astonished that the value is transferred as the display text of the DateField, and not as sortable serialized representation (like it happens when sending dates from server to client for Stores).
And still then, Ext.Net is not able to convert the value submitted on the server back to a valid date, and instead gives DateTime.MinValue as the value for the DateField.
I have not checked elsewhere, but I suspect other widgets might also have such subtle problems.
If it matters, our application always uses "en-US" as the current culture, only the UICultre is set to "fr" (or the user chosen language).
To ensure that this is not causing any problem, I set both Thread.CurrentCulture and Thread.CurrentUICulture to "fr" but still the same exception.
This is a blocking issue and has the capability to stall the entire localization feature we had introduced for our application :(
During testing, a strange exception with DateTimes was reported. After some analysis, I found that a particular operation in the application was executing well with the english language, but gave the exception in French.
I was able to narrow down the problem with Ext.Net's DateField somewhere.
When Freanch is set as the browser language, the DateField's DateMenu shows month names in French. But there are 2 important problems with the implementation:
1) I selected 14 Nov, 2010 as the date, but it always automatically changes to 14 Feb 2010.
2) Even then after submitting the date, it goes to the server as you can see in the screenshot below:
I was astonished that the value is transferred as the display text of the DateField, and not as sortable serialized representation (like it happens when sending dates from server to client for Stores).
And still then, Ext.Net is not able to convert the value submitted on the server back to a valid date, and instead gives DateTime.MinValue as the value for the DateField.
I have not checked elsewhere, but I suspect other widgets might also have such subtle problems.
If it matters, our application always uses "en-US" as the current culture, only the UICultre is set to "fr" (or the user chosen language).
To ensure that this is not causing any problem, I set both Thread.CurrentCulture and Thread.CurrentUICulture to "fr" but still the same exception.
This is a blocking issue and has the capability to stall the entire localization feature we had introduced for our application :(
Last edited by geoffrey.mcgill; Mar 01, 2011 at 3:38 PM.
Reason: [CLOSED]