On Sun, Jan 26, 2014 at 7:34 PM, Dave Rolsky <auta...@urth.org> wrote:
> > I never got around to doing the time zone localization work. At this > point, DateTime::Locale is _years_ out of date with regards to CLDR. The > approach I was using to parse CLDR and generate locales was not very > robust, so when the CLDR files changed it was a huge amount of work to > release a new DateTime::Locale. > > All this is to say that we could really use an updated DateTime::Locale ;) > > There are a few ways to do this: > > 1. Essentially what I'm doing now - which can be good enough, but is hard > to get 100% correct because of things like fallback locales, locale > "inheritance", etc. > > 2. Implement an ICU library in Perl that handles the full lookup reslution > logic required by CLDR. Said logic was not actually documented anywhere > last I looked, of course. So that means poking around in the Java and/or C > libraries to figure out what it should do. > > 3. Implement Perl bindings to libicu. I like this idea except I wonder if > this makes Windows support much harder. On the plus side, it'd almost > certainly be faster than #2 and much more correct than #1. > Yes, that does sound like the way to go. I'll ask at work if anyone has experience with libicu, but it wouldn't be anyone also with XS experience. Any suggestions on what to do in the near term working with current DateTime? Punt with "26 يناير، 2014 EST 10:37:42 ص"? Thanks, -- Bill Moseley mose...@hank.org
