Re: [w3c/manifest] Add optional `translations` member (#676)

> Is there a way of making all languages equal, rather than having one apparently main language and then all these others over there?

The idea of a "main language" is needed for two reasons:

- Backwards compatibility. A browser that doesn't know about the new translations feature needs to read the old data which is at the top level.
- Having a default. If the user's preferred language(s) are not supported, we can fall back to the "main language" of the manifest.

The concept of a "primary language" already exists in the Manifest, in the ["lang" member](https://www.w3.org/TR/appmanifest/#lang-member). So "primary language" is something we need to continue supporting, but it doesn't necessarily mean English, and it doesn't necessarily mean the browser is unaware of what language it is.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/676#issuecomment-952440826