Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)

carlosjeurissen left a comment (w3c/manifest#975)

@aphillips noted:
> 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 is a great point! And thanks for stating some of the motivations for the localisable manifest design decisions! The example I gave in https://github.com/w3c/manifest/issues/975#issuecomment-3830708925 was indeed very developer focused.

With this mindset, one could actually argue why nesting icons_localized inside `color_scheme_dark` can be problematic. It splits the resource declarations into two separate buckets:
`icons_localized.fr` and `color_scheme_dark.icons_localized.fr`. And potentially more in the future.
What if a specific locale is missing in one but not the other?

Should the default dark mode be used, or the localised light mode? A potential middle ground could be to have the global `icons` and `icons_localized` with the waterfall syntax inside. One can argue restricting to just `icons` and `icons_localized` seem to still result in a big improvement over the `color_scheme_dark.icons_localized` dimensions as it automatically resolves ambiguity like the above and resolve splitting localized members across color_scheme.

However transferring the localised icons declarations all to the translation teams seems like it could be potentially error prone and risky considering it also requires handling of the actual resource files and handle changes in icons declarations. If you add a non localised monochrome icon (which does not have any localised text on it), you would ideally not want to wait for all translation teams to update their own icons declaration before this monochrome icon is available in said locale.

Yet as `icons_localized` has been discussed for a long time and was finally merged @christianliebel. This ship may have sailed. However allowing the waterfall declarations within them could address many of the maintenance and fallback problems listed above and in my previous comment.

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

Message ID: <w3c/manifest/issues/975/3832239412@github.com>