Unplanned
Last Updated: 29 Jan 2020 08:28 by ADMIN

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".

Unplanned
Last Updated: 24 Jan 2020 09:57 by ADMIN
Created by: Imported User
Comments: 3
Category: Globalization
Type: Feature Request
19
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
Unplanned
Last Updated: 20 Jan 2020 13:51 by ADMIN
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".