Re: [w3c/manifest] Add members for localization (PR #1101)

@calidion @christianliebel 

> Please also note that we make these decisions in close coordination with the i18n working group.

Note that I18N has pointed out that the choices here necessarily include tradeoffs.

Examples in the spec and generally in discussion of the spec have a small number of languages. However, many applications are localized into tens or (in the case of large or geographically diverse companies) even over a hundred languages. 

Using multiple files for manifest localization reduces application size for these cases, since only the languages in use have to be retrieved. However, the retrieval mechanism is more complex and runtime changes (particularly to the OS locale) become more complicated or require a network connection to effect.

Using a single manifest file resolves some of these these problems, but the manifest itself can become quite large. The file can be difficult to work with (who has the ability to edit Hindi _and_ Japanese _and_ Arabic at the same time?). It also means that adding a language means redistributing the entire manifest.

None of these choices are specifically right or wrong. See: https://www.w3.org/TR/localizable-manifests/


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

Message ID: <w3c/manifest/pull/1101/c2211781940@github.com>