Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

Changed language field to adhere to RFC 5646 #100

Closed
wants to merge 3 commits into from
Closed

Changed language field to adhere to RFC 5646 #100

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
71fc91e
Changed language field to adhere to RFC 5646
Jul 31, 2013
d5e2e02
Added additional clarity to language field to comply with RFC 5646
Aug 1, 2013
53f5444
minor typo fix
Aug 1, 2013
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,8 +263,8 @@ Field | title
**Cardinality** | (0,n)
**Required** | No
**Accepted Values** | String
**Usage Notes** | -
**Example** | `{"language":"English"}`
**Usage Notes** | This should adhere to the [RFC 5646](http://tools.ietf.org/html/rfc5646) standard. http://rishida.net/utils/subtags/ provides a good tool for checking and verifying language codes. A language tag is comprised of either one or two parts, the language subtag (such as en for English, sp for Spanish, wo for Wolof) and the regional subtag (such as US for United States, GB for Great Britain, MX for Mexico), separated by a hyphen. Regional subtags should only be provided when needed to distinguish a language tag from another one (such as American vs. British English).
**Example** | `{"language":"en-US"}` `{"language":"en-GB"}` `{"language":"jp"}` `{"language":"es-MX, wo, nv, en-US"}`

{.table .table-striped}
**Field** | **granularity**
Expand Down