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

I like the hybrid approach, since it lets everyone do what their infrastructure supports best.

One thing to point out in informal language for **Approach 2** might be that no assumption may be made as to the "primary" language (that is, the language of the top-level fields *not* under `"translations"`). For some apps, English may be a secondary target.

```json
{
  "name": "Meine Applikation",
  "description": "Eine deutsche Applikation",
  "lang": "de",
  "translations": {
    "en": {
      …
    }
  }
  …
}
```

This comment is basically saying if `"lang"` is missing, don't assume it to be necessarily `"en"`.

-- 
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-810869837