davidben/client-language-selection

client-language-selection's Issues

Scalability

Web sites can be translated into dozens or hundreds of languages, and may also include regional variants and script variants. In your proposal, it looks like the server has to send a full list of supported languages to the client. How does this scale?

Origins containing multiple languages

The explainer should discuss what the browser does for an origin for which all resources are available in languages A and B, but some are also translated to language C, if the user's preferences are something like C, B.

One option would be to use the UI indicator, remember which languages the user has chosen to send to the site, and then send that subset of the user's full preference ordering since they've already been revealed for fingerprinting purposes.

Unicode extensions (user preferences)

Modern Unicode locale identifiers are not limited to languages; they also carry additional subtags and extensions. In tc39/ecma402#416 I proposed a way to add unicode extensions to the Accept-Language header. How would you envision supporting Unicode extensions with your new model of language negotiation?