Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BCP-47 language subsumption #11

Open
ericprud opened this issue Sep 22, 2021 · 2 comments
Open

BCP-47 language subsumption #11

ericprud opened this issue Sep 22, 2021 · 2 comments
Assignees

Comments

@ericprud
Copy link
Member

In the §3.3 Hybrid Approaches example includes manifest files for language tags with regions (e.g. fr-CA). Is there any expectation that that if e.g. author is missing from MyApplicationManifest-fr-CA.json, an app should prefer the value in MyApplicationManifest-fr.json over the one in MyApplicationManifest.json?
Likewise for variants, scripts, etc.

@aphillips
Copy link
Contributor

Yes: this is called locale fallback.

Note this text in section 5:

Some manifests allow for "sparse population" of values in the localized file. For example, the en-US (English, United States) file might only contain one or two US-specific values, relying on the en (English) file for most of its content. Specifications need to be explicit about whether sparse population is allowed and how it works to avoid misconfiguration errors or missing translations.

@aphillips aphillips self-assigned this Sep 22, 2021
@ericprud
Copy link
Member Author

Tx. Maybe the §3.3 Hybrid Approaches example could have a fr and a fr-CA, with the author conspicuously absent from the fr-CA.
(BTW, in an effort to demo regions in SPARQL, I exploited the Belgian "septante" in a cultural reference that didn't age well.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants