You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
Tx. Maybe the §3.3 Hybrid Approaches example could have a frand 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.)
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 fromMyApplicationManifest-fr-CA.json
, an app should prefer the value inMyApplicationManifest-fr.json
over the one inMyApplicationManifest.json
?Likewise for variants, scripts, etc.
The text was updated successfully, but these errors were encountered: