Matt Johnson-Pint

I tend to agree with Gilmore's points. Thanks for your efforts, but I recommend against this.

See also this post: http://stackoverflow.com/questions/16086962/how-to-get-a-time-zone-from-a-location-using-latitude-and-longitude-coordinates APTimeZones is essentially doing the approach that is recommended _not_ to do. (See the diagram with the two squares.)

I'd be interested in reviewing when you do. There are a few other libraries that already have the IANA data implemented, and it can be a bit challenging. I'm not...

@longlho - [moment-timezone](http://momentjs.com/timezone/) has gotten a lot better lately. :)

Yes, parsing is tricky, and data maintenance is a pain. Perhaps consider a plugin model. Expose some API in Intl.js that can be passed a function for time zone conversions....

Also, note that ECMA-402/2.0 makes a lot of the time zone stuff required instead of optional.

Actually, most browsers don't have this yet. See http://kangax.github.io/compat-table/esintl/ under "DateTimeFormat" - "resolvedOptions().timeZone defaults to the host environment"

This isn't urgent, just wanted to report it somewhere so that it can be eventually addressed.

Actually, it looks like the example doc referenced is showing *custom* context information. The build in one is available with just `context.TryGetHttpPath()`. The docs could still be a little clearer...

@lucas-zimerman - want to improve this doc if you have some time?