Hello Karl,

thanks for this solution. It works.

@Infragistics-Team:

This thread is from 2012. In your actual Version 13.2 this bug is still a part of the DatePicker. It cost several times to get a solution. It is time to eliminate this bug or to update the documantation!

Having just encountered this issue myself, I have realized that there are a couple of things wrong with both the documentation and the implementation of the regional settings.

The first issue is that the documentation glosses over the use of $.datePicker.setDefaults when in fact it is slightly more complicated. Here is the loader function that we now use successfully:

$.ig.loader(
    function () {
        if (m_sCurrentLocale != 'en') {
            var oRegion = $.ig.regional[m_sCurrentLocale];
            if (oRegion) {
                if (!oRegion.dayNamesMin) {
                    oRegion.dayNamesMin = oRegion.dayNamesShort;
                }
                $.datepicker.regional[m_sCurrentLocale] = oRegion;
                $.datepicker.setDefaults($.datepicker.regional[m_sCurrentLocale]);
            }
        }
    }
);

Where m_sCurrentLocale is set to the appropriate locale.

The first thing that has to be done is that the infragistics defaults have to be loaded into the datepicker regional settings and THEN the datepicker's defaults can be set.

In addition, you will notice the testing for dayNamesMin: these are the values that are used at top of the calendar entries and are only present for a few regions. Without these settings, the English versions will be displayed.

Once these changes are implemented, the datePicker in the grid will function as expected with regional settings.