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

Food for thought:

Platform | Embedded localization | Separate files | Docs
--------- | ---------------- | ------------ | ---------
| Android | ❌ | ✅ | [docs](https://developer.android.com/guide/topics/resources/localization)
| Apple (iOS & macOS) | ❌ | ✅ |  [docs](https://developer.apple.com/documentation/xcode/adding-support-for-languages-and-regions)
| ChromeOS | ❌ | ✅ | [docs](https://developer.chrome.com/docs/extensions/reference/i18n/)
| Windows | ❌ | ✅ | [UWP](https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/prepare-your-app-for-localization) [Win32](https://docs.microsoft.com/en-us/windows/win32/intl/localizing-resources-and-building-the-application)
| Firefox OS / Gaia / KaiOS  | ❌ | ✅ |  [docs](https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Firefox_OS_apps/Localization/Getting_started_with_app_localization#create_translations)

@marcoscaceres Totally agree that a build process would be relatively easy to set up, assuming you are already using a build process, but given how a lot of app architectures are relying on separately-maintained files, I think it would be good to offer out of the box too. I believe I addressed all of [your primary concerns about the external files](#issuecomment-817617728) in [this comment](#issuecomment-817850548).

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