1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
/*!
An interface to all manner of locale-related information.
This crate provides a locale-related codes/identifiers and any standards-based
information concerning them. For example, ISO-396 language identifiers, or
ISO-3166 country identifiers. These are under the module
[`locale_codes::codes`](codes/index.html). These modules are effectively
registries of standard code/identifiers and any metadate published as a part
of the associated standard(s). For example, _Codes for the representation of
currencies_, or ISO 4217 is based on a spreadsheet published directly by ISO
itself with some additional fields added from other publicly accessible sources.
While there is no formal type system or traits for modules exporting codes, there
are definitely some patterns all of the current implementations follow.
1. modules typically implement a `lookup()` function that returns an `Option`,
1. although where some standards have both alphabetic and numeric identifiers
there are `lookup_by_alpha()` and `lookup_by_numeric()` instead, .
1. Most will also include a function `all_codes()` to retrieve a vector of all
the known identifiers,
1. or, `all_alpha_codes()` and `all_numeric_codes()` as appropriate.
Some standards, specifically language and country, support 2-character and
3-character alphabetic identifiers, a single `lookup()` function is used to
lookup either.
## Example - Codes
The following example demonstrates some of the components of the crate, at
least some reasonable use cases.
1. Construct a _strict_ locale string where identifiers are checked against
known standard codes where possible.
1. Lookup the ISO-3166 data for the country (in the
[`CountryInfo`](codes/country/struct.CountryInfo.html) struct) identified
by the ISO-3166, part 2, 3-character identifier.
1. The data fromn the last call contains one or more regions (in the
[`RegionInfo`](/codes/region/struct.RegionInfo.html) struct), determine
the countries name from the `country_code`.
1. Now we have the country name we can lookup the details of the currencies
(in, the [`CurrencyInfo`](CurrencyInfo) struct).
```
use locale_codes::{country, currency, region};
let mexico = country::lookup("MEX").unwrap();
println!("{:?}", mexico);
let mexico_region = region::lookup(mexico.country_code).unwrap();
println!("{:?}", mexico_region);
let currencies = currency::currencies_for_country_name(mexico_region.name.as_str());
println!("{:?}", currencies);
```
## JSON Data Files
The script [`create-data-modules`](https://github.com/johnstonskj/locale-codes/blob/master/create-data-modules.sh)
on the other hand is used to process files downloaded, or scraped, from
standards web sites to create data used by the library. This data is generated
as JSON files in the `src/codes/data` folder and read as a part of the
build for `codes` modules using the Rust `include!` macro.
Currently data is generated for the following standards:
* ISO 639 _Codes for the representation of names of languages_; Parts 1-4,
2-character and 3-character codes supported.
* ISO 3166 _Codes for the representation of names of countries and their
subdivisions_; Part 1, 2-character codes, only.
* ISO 4217 _Codes for the representation of currencies_; alphabetic and
numeric codes supported.
* ISO 15924 _Codes for the representation of names of scripts_; alphabetic
and numeric codes supported.
Each folder under `src-data` represents a single standard, which may
generate one or more data sets. Each directory will contain a Python
script, `generate.py` which is called by the top-level script to create
the JSON in the correct location. Each should also contain a README
that includes attribution for any data retrieved to make this possible.
*/
extern crate lazy_static;
extern crate log;
extern crate serde;
extern crate serde_json;
// ------------------------------------------------------------------------------------------------
// Public Modules
// ------------------------------------------------------------------------------------------------