Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968)

> nor would it allow for arbitrary language shifts to be handled within the root manifest (e.g., description in English, name in Swahili)

Actually, I take that back. You might be able to do something like

```json
{
  "dir": "ltr",
  "lang": "sw"
  "name": "Tembo",
  "translations": {
    "en": {
      "description": "Never forget where you put your keys with our revolutionary technology."
    }
  }
}
```

We need to define what happens when a key exists in `translations` that is not in the root Manifest, so… if we allowed you to define values that are undefined in the root Manifest, that might solve for your issue.

-- 
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/968#issuecomment-965879370