cldr

SlikelySubtags.json not loaded

时间秒杀一切 提交于 2021-02-10 07:39:07
问题 I use cldr and globalize libaries. And I read in docs that I need to load likelySubtags.json . Maybe, it is due to my poor English but I can't get where I need to get these files? Or how to generate? Just for example: <script> Globalize.load({ main: { en: { ... } }, supplemental: { likelySubtags: { ... }, timeDate: { ... }, weekData: { ... } } }); </script> As I understood it generates these JSONs. But that do I need to write instead of points? Can anyone explain more clear? Below the code

install package on windows ERROR: compilation failed for package 'cldr'

孤街醉人 提交于 2020-01-23 12:33:48
问题 url <- "http://cran.us.r-project.org/src/contrib/Archive/cldr/cldr_1.1.0.tar.gz" pkgFile<-"cldr_1.1.0.tar.gz" download.file(url = url, destfile = pkgFile) Console >trying URL 'http://cran.us.r-project.org/src/contrib/Archive/cldr/cldr_1.1.0.tar.gz' Content type 'application/x-gzip' length 2296083 bytes (2.2 MB) ============================== downloaded 2.2 MB install.packages(pkgs = pkgFile, type = "source", repos = NULL) > Installing package into ‘C: / Users / v - xuawan / Documents / R /

mapping joda timezone to windows timezone (for example in C#)

本小妞迷上赌 提交于 2020-01-05 02:51:07
问题 I'm having trouble mapping joda time zones to windows time zones. I use the xml of CLDR mappings, and it works for most of the translations. nevertheless, it doesn't have values for several joda time zones: America/Indiana/Indianapolis, BST, Australia/Victoria, Universal, Australia/NSW, America/Fort_Wayne, Africa/Asmara, America/Kentucky/Louisville, Asia/Kashgar, US/Pacific, Australia/West, Australia/Queensland, Australia/South, US/Eastern, US/Central, US/Arizona, Australia/Tasmania, NZ, US

ICU/CLDR | ISO 639 Changes - Monitoring & Maintenance

跟風遠走 提交于 2020-01-03 04:47:13
问题 The International Components for Unicode (ICU) is the underlying library that provides localisation features in various programming languages and environments; I approach this from PHP where the intl extension uses ICU for this purpose. As I understand it, ICU uses Unicode Common Locale Data Repository (CLDR) for identifying ISO 639 language codes. Language codes are subject to change The ISO 639 language codes are actively maintained and have been subject to quite substantial changes over

JS Globalize - load json cldr

旧城冷巷雨未停 提交于 2019-12-07 06:52:04
问题 I have a problem with the latest version of globalize.js . To work with it I had to load the cldr modules and language definitions. Now I had this example from the globalize docs: // loading needed modules $.get('/Scripts/cldr/supplemental/likelySubtags.json', Globalize.load); $.get('/Scripts/cldr/main/en/numbers.json', Globalize.load); $.get('/Scripts/cldr/main/de/numbers.json', Globalize.load); // set current language lobalize.locale('de-de'); My problem now is that the local json files are

JS Globalize - load json cldr

烂漫一生 提交于 2019-12-05 10:34:36
I have a problem with the latest version of globalize.js . To work with it I had to load the cldr modules and language definitions. Now I had this example from the globalize docs: // loading needed modules $.get('/Scripts/cldr/supplemental/likelySubtags.json', Globalize.load); $.get('/Scripts/cldr/main/en/numbers.json', Globalize.load); $.get('/Scripts/cldr/main/de/numbers.json', Globalize.load); // set current language lobalize.locale('de-de'); My problem now is that the local json files are loaded async. That means at the moment where my script is try to set the current language, the modules