Skip to content

Commit 2cebd35

Browse files
committed
Version and docs link bump
1 parent da27df4 commit 2cebd35

File tree

3 files changed

+12
-11
lines changed

3 files changed

+12
-11
lines changed

Cargo.toml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
[package]
22
name = "zoneinfo_parse"
3-
version = "0.1.0"
3+
version = "0.1.2"
44
authors = ["Ben S <[email protected]>"]
5+
documentation = "https://docs.rs/zoneinfo_parse"
56

67
[dependencies]
7-
lazy_static = "*"
8-
regex = "*"
8+
lazy_static = "0.2.1"
9+
regex = "0.1.77"
910

1011
[dependencies.datetime]
1112
git = "https://github.com/rust-datetime/datetime.git"

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ The database itself is maintained by IANA. For more information, see [IANA’s p
1111
[w]: https://en.wikipedia.org/wiki/Tz_database
1212
[zc]: https://github.com/rust-datetime/zoneinfo-compiled
1313

14-
### [View the Rustdoc](https://datetime.rustdocs.org/zoneinfo_parse/index.html)
14+
### [View the Rustdoc](https://docs.rs/zoneinfo_parse)
1515

1616

1717
## Format
1818

19-
The zoneinfo files contains `Zone`, `Rule`, and `Link` information. Each type of line forms a variant in the [`line::Line`](https://datetime.rustdocs.org/zoneinfo_parse/line/enum.Line.html) enum.
19+
The zoneinfo files contains `Zone`, `Rule`, and `Link` information. Each type of line forms a variant in the `line::Line` enum.
2020

2121
To get started, here are a few lines representing what time is like in the `Europe/Madrid` time zone:
2222

@@ -31,7 +31,7 @@ The first line is a comment. The second starts with `Zone`, so we know
3131
So parsing these five lines would return the five following results:
3232

3333
- A `line::Line::Space` for the comment, because the line doesn’t contain any information (but isn’t strictly *invalid* either).
34-
- A `line::Line::Zone` for the first `Zone` entry. This contains a [`Zone` struct](https://datetime.rustdocs.org/zoneinfo_parse/line/struct.Zone.html) that holds the name of the zone. All the other fields are stored in the [`ZoneInfo` struct](https://datetime.rustdocs.org/zoneinfo_parse/line/struct.ZoneInfo.html).
34+
- A `line::Line::Zone` for the first `Zone` entry. This contains a `Zone` struct that holds the name of the zone. All the other fields are stored in the `ZoneInfo` struct.
3535
- A `line::Line::Continuation` for the next entry. This is different from the line above as it doesn’t contain a name field; it only has the information in a `ZoneInfo` struct.
3636
- The fourth line contains the same types of data as the third.
3737
- As does the fifth.
@@ -44,23 +44,23 @@ Lines with rule definitions look like this:
4444
Rule Spain 1918 only - Apr 15 23:00s 1:00 S
4545
Rule Spain 1919 only - Apr 5 23:00s 1:00 S
4646

47-
All these lines follow the same pattern: A `line::Line::Rule` that contains a [`Rule` struct](https://datetime.rustdocs.org/zoneinfo_parse/line/struct.Rule.html), which has a field for each column of data.
47+
All these lines follow the same pattern: A `line::Line::Rule` that contains a `Rule` struct, which has a field for each column of data.
4848

4949
Finally, there are lines that link one zone to another’s name:
5050

5151
Link Europe/Prague Europe/Bratislava
5252

53-
The [`Link` struct](https://datetime.rustdocs.org/zoneinfo_parse/line/struct.Link.html) simply contains the names of both the existing and new time zones.
53+
The `Link` struct simply contains the names of both the existing and new time zones.
5454

5555

5656
## Interpretation
5757

5858
Once the input lines have been parsed, they must be *interpreted* to form a table of time zone data.
5959

60-
The easiest way to do this is with a [`TableBuilder`](https://datetime.rustdocs.org/zoneinfo_parse/table/struct.TableBuilder.html). You can add various lines to the builder, and it will throw an error as soon as it detects that something’s wrong, such as a duplicate or a missing entry. When all the lines have been fed to the builder, you can use the `build` method to produce a [`Table`](https://datetime.rustdocs.org/zoneinfo_parse/table/struct.Table.html) containing fields for the rule, zone, and link lines.
60+
The easiest way to do this is with a `TableBuilder`. You can add various lines to the builder, and it will throw an error as soon as it detects that something’s wrong, such as a duplicate or a missing entry. When all the lines have been fed to the builder, you can use the `build` method to produce a `Table` containing fields for the rule, zone, and link lines.
6161

6262

6363

6464
## Example program
6565

66-
This crate is used to produce the data for the [`zoneinfo-data` crate](https://github.com/rust-datetime/zoneinfo-data). For an example of its use, see the bundled [data crate builder](https://github.com/rust-datetime/zoneinfo-data).
66+
This crate is used to produce the data for the [`zoneinfo-data` crate](https://github.com/rust-datetime/zoneinfo-data). For an example of its use, see the bundled [data crate builder](https://github.com/rust-datetime/zoneinfo-parse/tree/master/data-crate-builder).

src/lib.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
//! [iana]: https://www.iana.org/time-zones
1515
//! [tz]: https://github.com/eggert/tz
1616
//! [w]: https://en.wikipedia.org/wiki/Tz_database
17-
//! [zc]: https://datetime.rustdocs.org/zoneinfo_compiled/index.html
17+
//! [zc]: https://github.com/rust-datetime/zoneinfo-compiled
1818
//!
1919
//! ## Outline
2020
//!

0 commit comments

Comments
 (0)