A possible workaround, for the time being, involves setting the InputLanguageManager.Current.CurrentInputLanguage property along with the Culture in a Dispatcher.BeginInvoke call:
Dispatcher.BeginInvoke(new Action(() =>
{
var culture = System.Globalization.CultureInfo.GetCultureInfo("ar-AE");
InputLanguageManager.Current.CurrentInputLanguage = culture;
virtualKeyboard.Culture = culture;
}), System.Windows.Threading.DispatcherPriority.Loaded);
Regards,
Dilyan Traykov
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.