Bug report

The toLocaleDateString for the ko-KR culture returns a date in format "yyyy. MM. dd", while the kendo.culture.ko-KR.js contains short date pattern 'd' as yyyy-mm-dd

Reproduction of the problem

1. Open the Dojo example - https://dojo.telerik.com/@NeliK/igaGIxoQ

Expected/desired behavior

The format for the ko-KR culture should meet the local format. The kendo.culture.ko-KR.js should be updated accordingly.

Environment

• Kendo UI version: 2024.1.130
• Browser: [all ]

We are using you "number formatting API" (http://docs.telerik.com/kendo-ui/framework/globalization/numberformatting) to display the numbers on our webpage.   

For that, your API works fine as long as we round the numbers. E.g.: 

kendo.toString(10.12, "n0"); //  will result in 10
kendo.toString(10.99, "n0"); //  will result in 11
But we have some use-cases where we have to cut/truncate the number so that:

kendo.toString(10.999, "n0"); // SHOULD result in 10
Here we just want to cut all decimals without any rounding, but I can´t find this option in your API documentation !!
I think this is a very basic use-case which should be handled by your low level API !

I am developing a Vietnamese Web Application, using Kendo UI for ASP.NET MVC. But I cannot find out resource language (*.DLL) for Vietnam. Please send me it, thanks alot! 

Add "daysOrdered" property to the kendo.cultures.current.calendar.days object, which would contains days of week sorted by the first day of week (Sunday or Monday)

Using a single minified culture file that would have all cultures supported by Kendo UI included can be very useful. Although it is possible do this manually by combining all files currently provided on official releases, this would have to be done every time Kendo UI is updated to a newer version. An official file would make things much more straightforward.

Kendo support only "N" format for number format.  If not supported format is provided (for example "F2" for fixed point with 2 decimal), the number could have F in the front, or be truncated etc.  Would like to be able to use a standard .Net formats to avoid such a problems

We'd like to be able to pass "Q" into the toString function for a date and have it return the quarter.

ex. 
kendo.toString(new Date(2000, 10, 6), "Q") -> Q4

While dates and numbers can be formatted according to the current culture, kendo.getFileSizeMessage() has constant English strings '0 Byte' and 'Bytes'.

I suggest doing as Windows Explorer does: 0 as "0 KB", and any size between that and 1 KB as "1 KB".

As suggested here : http://www.telerik.com/forums/supporting-both-comma-and-dot-for-decimal-input
With this example : http://trykendoui.telerik.com/ikId/2

Having to force either the dot or comma for numerical input is cumbersome in applications where customers input data all day long and it has to be effective. 

I would suggest a flag named along the lines of "IgnoreCultureOnInput" which would allow you to punch in either the dot or the comma, but have it converted it back into your local for display. 

Note that the example above is not complete as it is : 
1 - locale specific (won't adjust if you locale calls for a comma instead)
2 - does not support text selection

As per the .NET format support shown here:
http://stackoverflow.com/questions/11731996/string-format-numbers-thousands-123k-millions-123m-billions-123b

And here:
http://msdn.microsoft.com/en-us/library/0c899ak8%28v=vs.100%29.aspx#SpecifierTh

123456789.ToString("#,##0,") will return "123,457".
123456789.ToString("#,##0,K") will return "123,457K".

kendo.format("{0:#,##0,", 123456789) will return "123,456,789".
kendo.format("{0:#,##0,K", 123456789) will return "123,456,789K".

As per the .NET standard, each trailing comma will round off 3 digits, so 123456789.ToString("#,##0,,M") will return "123M".

Base on the doc, the new Scheduler component doesn't support culture.

Please include the scheduler to support culture

http://docs.telerik.com/kendo-ui/framework/globalization/overview#widgets-that-depend-on-culture-info

Hi
the fa-IR culture seems using wrong culture. the culture for fa-IR and arabic culture must not be the same.
for example in Arabic instead of using Saturday they use "السبت" but in fa-IR Culture they use "شنبه".
Also when using fa-IR culture the calendar must be changed to Persian Calendar (or Jalali Calendar) but after changing culture it is using Gregorian Calendar.
Thanks