Open bigeasy opened 12 years ago
What an excellent find. It has EVERYTHING
Funny how whenever one spends enough time with even the most mundane programming problems, they starts to get interesting, and even kind of exciting. I looked through the slide shows. I'm tempted to create a collation function generator for JavaScript.
Also, I found this: https://github.com/jquery/globalize
Here is one of the locale files.
https://github.com/jquery/globalize/blob/master/lib/cultures/globalize.culture.ar-AE.js
Interesting how this library focuses almost entirely on dates and times. That seems to be where people get started with localization. Which is why a lot of date libraries are huge, because localization has a lot of details.
In any case, you can probably pluck what you need from those files and convert them to the strftime
formats.
If you know .NET, and you have the time to take a peek, it would be nice to see how all these files are "generated". I'm guessing that, because it needs .NET to run, it might just be printing out the localization information in .NET.
I'm more interested in CLDR for use here with Timezone.
Yeah, CLDR is perfect for Timezone. No point in looking at anything else in my mind, it appears to have pretty much everything you would need. It looks like it even specifies Titlecase for the month and day names (at least at the French file I looked at)
When are you pushing 0.0.16?
On Thu, Jul 19, 2012 at 9:57 AM, Alan Gutierrez < reply@reply.github.com
wrote:
Funny how whenever one spends enough time with even the most mundane programming problems, they starts to get interesting, and even kind of exciting. I looked through the slide shows. I'm tempted to create a collation function generator for JavaScript.
Also, I found this: https://github.com/jquery/globalize
Here is one of the locale files.
https://github.com/jquery/globalize/blob/master/lib/cultures/globalize.culture.ar-AE.js
Interesting how this library focuses almost entirely on dates and times. That seems to be where people get started with localization. Which is why a lot of date libraries are huge, because localization has a lot of details.
In any case, you can probably pluck what you need from those files and convert them to the
strftime
formats.If you know .NET, and you have the time to take a peek, it would be nice to see how all these files are "generated". I'm guessing that, because it needs .NET to run, it might just be printing out the localization information in .NET.
I'm more interested in CLDR for use here with Timezone.
Reply to this email directly or view it on GitHub: https://github.com/bigeasy/timezone/issues/126#issuecomment-7104136
Oh, I don't have anything in 0.0.16 yet. I always make an issue to bump the version string in the timezone.js
source immediately after I push a version so I don't forget.
Are you asking for a timeframe on the CLDR formats?
Oh, uh. Right 0.0.15 on the other hand, was released yesterday. That has all the UNIX strftime
locales in it. The data is online also at...
http://bigeasy.github.com/timezone/v0.0.15/jsonp/America/Detroit.js
And so on.
No, more on the languages you imported yesterday. I'm not expecting CLDR anytime soon.
On Thu, Jul 19, 2012 at 10:30 AM, Alan Gutierrez < reply@reply.github.com
wrote:
Oh, I don't have anything in 0.0.16 yet. I always make an issue to bump the version string in the
timezone.js
source immediately after I push a version so I don't forget.Are you asking for a timeframe on the CLDR formats?
Reply to this email directly or view it on GitHub: https://github.com/bigeasy/timezone/issues/126#issuecomment-7105081
Signals crossed.
Just tested, looks great!
Parse CLDR to extract date and time formats.