CODEWITHSUNDEEP
language-agnosticlocalizationstandardslocalerfc
Daniel Trebbien
Daniel Trebbien

Reputation: 39208

Is there a standard algorithm for locale resolution?

In support of software internationalization, many programming languages and platforms support a means of obtaining localized resources to be used in the UI that is shown to the user (e.g. Java's java.util.ResourceBundle class). Often, if resources for the user's preferred locale are not available, then there is a fallback mechanism, or locale resolution process, that will attempt to locate the nearest-matching resources from the sets of available resources. For example, if resources for en-US are not available, then commonly the system attempts to find resources for en.

The locale resolution process seems nearly the same for many languages' and platforms' resource bundle solutions. Are they following some standard locale resolution algorithm, or, if not, does such a standard exist?

Upvotes: 7

Views: 1397

Answers (3)

Doug Domeny
Doug Domeny

Reputation: 4470

The CLDR - Unicode Common Locale Data Repository has a proposed (as of 2015) algorithm based on language distance. Without the distance data this is not a solution, but is worth watching for a solution in the future.

Upvotes: 1

Daniel Trebbien
Daniel Trebbien

Reputation: 39208

There is apparently RFC 4647, Matching of Language Tags, which describes the syntax of "language-ranges" for specifying the list of a user's preferred languages, as well as the "filtering" and "lookup" mechanisms for comparing and matching language-ranges to RFC 4646 language tags. RFC 4647 describes these mechanisms as:

Filtering produces a (potentially empty) set of language tags, whereas lookup produces a single language tag.

Upvotes: 2

Tom Anderson
Tom Anderson

Reputation: 47193

I'm not aware of a standard per se.

However, the algorithm being used is a trivial consequence of the fact that locales are hierarchical. There is a (notional) root locale with no name. Beneath this are language-only locales (en, fr, etc). Beneath those are national locales (en_GB, en_US, etc). Beneath those are, optionally, variant locales (en_GB_Yorkshire, en_GB_cockney, etc - for realistic examples, look at Norway).

The natural way to find an appropriate resource is to start with the lowest, most specific, locale you can, and walk up the tree until you find something. So, starting with en_US_TX, you step up to en_US, then en, then the root.

Upvotes: 1

Related Questions