I have a few questions about globalization :
1) Why don't you use the browser language by default ? If the script of the current culture of the browser was added, why not use it by default ? For the moment, it's always 'en-US'
2) I added the script <script src="scripts/js/cultures/kendo.culture.fr.min.js"></script> in my application. If I set the culture to 'fr-FR' (kendo.culture("fr-FR")), it doesn't work, the default 'fr' script is not used (I think it should be).
3) Is it possible (and how) to use your globalization framework to localize our own strings ?
7 Answers, 1 is accepted
Straight upto your questions:
#1: In order to globalize the widgets the developer should include the required resouces. That is why setting the current culture should be developer's task.
#2: I was not able to observe the described erroneous behavior. Check this jsFiddle demo. You can also check the globalization demo for more information.
#3: Currently this is not supported.
the Telerik team
Concerning the second point, you added the script 'kendo.culture.fr-FR.js'. Ok, in this case, it works well but if you add only the script ''kendo.culture.fr.js' and you set the culture to 'fr-FR', it doesn't work. As the fr-FR script is not found, I think you should try to choose the default culture 'fr' script. It's not the case actually. If the script 'fr-FR' is not found, you choose directly the default culture 'en-US'.
Currently the culture method will search directly for a "fr-FR" property in the kendo.cultures object. If you load only "kendo.culture.fr.js" script, then you will need to set the culture like this:
All the best,
the Telerik team
Is it possible to set the culture by using "fr" instead of "fr-FR" in the latest release of kendo ?
Seems like it's still not possible ?
The functionality discussed here talks about setting "fr-FR" culture when only "kendo.culture.fr.min.js" is registered. Check this jsBin demo for clarification. The opposite functionality is not supported.