- From: Addison Phillips <notifications@github.com>
- Date: Sun, 01 Feb 2026 09:14:22 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 1 February 2026 17:14:27 UTC
aphillips left a comment (w3c/manifest#975) @carlosjeurissen noted: > The color_scheme_dark.icons_localized would result in authors having to copy all icon declarations across all buckets. Which can be a nightmare to maintain. One callout: localization processes often take the default/root locale resources and copy the entire tree into the target locale. You can think of this being "developers", but in practice the developers touch one locale and the translation team make all the rest. So it may not be as onerous as it sounds. That said, monolithic resource files (with all languages in a single file) are less-forgiving to maintain because they depend on all languages being fully available at build time and the resulting file is unwieldy and hard to work with. Adding a language means respinning the file. Multiple languages means that "proofreading" the file can become complicated. These sorts of considerations are why resource file based or hybrid approaches tend to be more widely recommended by I18N. See [here](https://www.w3.org/TR/localizable-manifests/#common-approaches) in our localizable manifests note. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/975#issuecomment-3831464135 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/975/3831464135@github.com>
Received on Sunday, 1 February 2026 17:14:27 UTC