Skip to content

Locales: Indicate what database a locale is coming from #510

@conradarcturus

Description

@conradarcturus

Locales may be in LangNav for various reasons and it would be know why we included that specific combination of language + territory. We have an enum that helps a little bit:

export enum LocaleSource {
  StableDatabase = 'StableDatabase', // the standard source, kept in locales.tsv
  IANA = 'IANA', // created when importing IANA variant tags
  Census = 'census', // created when importing census data
  CreateRegionalLocales = 'createRegionalLocales', // created when generating aggregated regional locales
  CreateFamilyLocales = 'createFamilyLocales', // created when generating locales for language families
}

StableDatabase is everything that comes from locales.tsv -- but we should break up that better and add a column in locales.tsv list for why we added it. Possible values:

  • CLDR (Common Locale Data Repository)
  • ECMLR (European Charter of Minority Language Rights)
  • Ethnologue: Ethnologue lists the combination. Note we need to be careful if we are allowed to cite Ethnologue.
  • Census -- right now "Census" means it was not in the Stable Database (locales.tsv) and its not visible the main LocaleTable but we loaded it with CensusData and its in the Potential Locale Table. We should keep this distinction but recognize the source by splitting it into Census and CensusMarginal -- with marginal meaning that its from a census but not in the main table because its a marginal entry.

As you imagine while there may be 1 primary source, there may be multiple sources as well, eg. CLDR + Census so we may need to change how the field is stored & displayed. Potentially we may want to split it into "OriginalSource" and "Sources"

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions