New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include information from zone.tab and iso3166.tab in Tzdb.nzd #194

Closed
GoogleCodeExporter opened this Issue Mar 15, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@GoogleCodeExporter

GoogleCodeExporter commented Mar 15, 2015

> What situation does this request make simpler?

Offering the user time zone information (with location) with English country 
names and comments, until we provide full CLDR support.

> Can you provide a straw-man example of what you'd want the API to look
like?

The current work in the zone.tab branch exposes an IList<GeoLocation> 
GeoLocations property, where GeoLocation has the following properties:

- CountryName
- CountryCode
- Latitude
- Longitude
- ZoneId
- Comment

The current implementation increases the size of Tzdb.nzd (2012j with Windows 
mappings 22.1) from 111,189 bytes to 125,524 bytes.

The implementation is pretty simple - we really need to just work out whether 
or not we want this. If we do, we should probably do it soon, in order to 
maximize the benefit before the release with more CLDR information.

Original issue reported on code.google.com by jonathan.skeet on 23 Feb 2013 at 9:11

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 15, 2015

This is implemented, and will be reviewed as part of issue 173.

Original comment by jonathan.skeet on 21 Mar 2013 at 2:50

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 15, 2015

Original comment by malcolm.rowe on 6 Apr 2013 at 9:08

  • Added labels: Milestone-1.1.0
  • Removed labels: Milestone-1.1-consider

@malcolmr malcolmr modified the milestone: 1.1.0 Mar 15, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment