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

Thanks @aarongustafson for linking MiniApps WG to this issue.  ​

The MiniApp WG already had conversations with the i18n WG to address this same problem. No solution found so far. One of the major concerns was the potential compatibility with the Web Manifest.  

The language negotiation or dynamic serving [suggested by the Web Manifest](https://www.w3.org/TR/appmanifest/#internationalization) cannot be implemented by MiniApps since they are packaged, and they can be retrieved using other non-HTTP protocols (or the file system). 

That second approach (translations within the manifest) would enable MiniApps to implement multilingual support, keeping the compatibility with the Web Manifest. So, it's great you raised this issue.

To feed the discussion, apart from the `lang`, we would also **need to specify each language's direction** (`dir`) to cover all cases.  

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