Japanese Calendar Support

2 posts, 0 answers
  1. Gurpreet
    Gurpreet avatar
    1 posts
    Member since:
    Oct 2014

    Posted 20 Oct 2014 Link to this post

    In my application I am using Telerik RadDateTime Picker control to let the user select a Date.

    The calendar used by the application is Japanese Emperor Calendar.
    Please find the documentation here: http://msdn.microsoft.com/query/dev12.query?appId=Dev12IDEF1&l=EN-US&k=k(System.Globalization.JapaneseCalendar);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);k(DevLang-csharp)&rd=true

    The Japanese Emperor Calendar has years which are different than the Gregorian year, all other things are same as the Gregorian year. The year is counted from the current emperor's year of rule. For example the current year is '平成 26'

    There are currently 2 issues with the control:
    1) The control shows the correct emperor year after the postback. But before the postback, the year shown is the Gregorian year.
    2) When the control is selected, i.e. it is "inFocus", the year shown is Gregorian year. The year is changed to Emperor year when the control is not in Focus.

    Will you please suggest how can I solve the above two issues.
    If they are the issues in current implementation of RadDateTime Control, will you support the Japanese Calendar in next release or in some hotfix?
  2. Vasil
    Admin
    Vasil avatar
    1547 posts

    Posted 22 Oct 2014 Link to this post

    Hello Gurpreet,

    The RadCalendar supports only cultures based on the Gregorian Calendar.

    We do not plan to support other calendars until the browsers start to support more calendars in the Date type. The Date objects are heavy used in the RadCalendar and RadDateInput for all calculations and validations of the dates.

    Regards,
    Vasil
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top