I want to change what is shown in the scheduler headers, depending on my current culture, and on the view (different things for a week view and for a day view, for example).
Hello,
The difference comes from default formats. In the web-based suites, the format designated in my previous post is used, you can also see it in the Kendo UI for jQuery suite, for example: https://demos.telerik.com/kendo-ui/scheduler/localization. Whether the month or only the date is included is a matter of different design that has been chosen probably around a decade ago. The solution is a header template so you can choose what to render. Here are two examples:
Regards,
Marin Bratanov
Progress Telerik
Five days of Blazor, Angular, React, and Xamarin experts live-coding on twitch.tv/CodeItLive , special prizes and more, for FREE?! Register now for DevReach 2.0(20).
Well, all your other control suites manage it. I've been using the ones for web, WPF and WinForms, and all of them format correctly when I set the culture to en-GB. That's why I can't understand why this component doesn't. They don't use a single format for all cultures, they use one specific to each culture.
Best regards,Hello,
For such a "fix", the feature must be implemented first, because there is no single format string that can suit all cultures.
Regards,
Marin Bratanov
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.
Marin,
Whilst it would be nice to be able to control the format, the most important point is to fix the bug that makes it show the US format when the culture is UK. It should respect the application culture, which it doesn't right now. All other Telerik products I've used (a fair few) respect the application culture, and show dates in the appropriate format.
The ability to specify a more specific format would be great, but is less important than showing the right format in the first place.
Thanks
Hi,
There are many locales in the world in addition to the US and the UK, and so there are many users who expect the date first, and many users who expect the month first. Thus, there should be a feature that lets the developer control this so they can choose what suits their audience best. The built-in feature needs to also provide a format short enough to not expand the cells with narrow scheduler widths.
I understand that users in the UK find this confusing, this is why I mentioned it in my post explicitly, and you can click the Follow button on this page to get email notifications for status updates - when it is implemented and what release that will be in.
Regards,
Marin Bratanov
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.
Hello, thanks for the reply and sample project.
However, you are missing a fundamental point here. The UK culture does not use the M/dd format, that is the US format. In the UK, we exclusively use dd/M, eg 29/4 for the 29th Apr.
That is my whole point, UK users will not want to see dates in a US format. Furthermore, for dates where both day and month are less than 12, eg for the first week in Jan-Sep, the format is unclear, as UK user will expect 1/2 to mean the 1st Feb, whereas according to the way you have formatted it, the date is actually 2nd Jan.
This seems to be a bug in your software, presumably arising from the developer not knowing that the UK uses a different format from the US.
Thanks again, but is there any way this can be fixed?
I am attaching here a small localization sample that shows:
Regards,
Marin Bratanov
Progress Telerik
Five days of Blazor, Angular, React, and Xamarin experts live-coding on twitch.tv/CodeItLive , special prizes and more, for FREE?! Register now for DevReach 2.0(20).