[ltli] Use of HTTP Accept-Language header for a locale model. (#26)

r12a has just created a new issue for https://github.com/w3c/ltli:

== Use of HTTP Accept-Language header for a locale model. ==
https://w3c.github.io/ltli/#dfn-locale-aware

> Historically, locales were identified by the programming language or operating environment of the user. This application-specific identifier was often inferred from language tags. For example, an implementation could map a language tag from an existing protocol, such as HTTP's Accept-Language header, to its locale model.

What if the header value was a list of language tags – that wouldn't work. Perhaps the current wording makes this seem like a too-plausible option.  It is also problematic if not working over http.  Do we have a better example?

Please view or discuss this issue at https://github.com/w3c/ltli/issues/26 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 30 September 2020 13:45:56 UTC