- From: Aaron Gustafson <notifications@github.com>
- Date: Mon, 06 Nov 2023 09:24:21 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 November 2023 17:24:28 UTC
> I think I'd prefer just letting the website use the `Accept-Language` HTTP feature for this. Probably the most elegant, but it’s not within the realm of possibility for a lot of orgs and site types (thinking static sites, for example). > Would the use case for this be that you can have URLs with different ?lang= query parameters to match the user's language? See also MDN style links where the language code is embedded in the URL path. > Icons, graphics, or remote content (help pages, for example) are sometimes varied by locale or by region (with locale serving as a poor proxy for region). This might be done, for example, because the icon contains some text or because a graphic shows a culturally-linked image (personal images, national costume, post box shapes, etc. etc.) that the user wishes to localize. Or it might be because functionality or defaults differ (sorting based on pronunciation instead of name for Chinese, for example) > > We don't know why the user might want to localize the icon or shortcut (or whatever). Agree on all of these. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/pull/1101#issuecomment-1795574792 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/pull/1101/c1795574792@github.com>
Received on Monday, 6 November 2023 17:24:28 UTC