Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434)

> +          Using content-negotiation, or geo-ip, etc. on the server:
> +        </dt>
> +        <dd>
> +          The server that hosts the web application could attempt to
> +          predetermine the user's language by using a geo-ip look-up or by
> +          using content negotiation (e.g., using [[RFC7540]]'s
> +          "<code>Accept-Language</code>" header, or even a custom HTTP header).
> +        </dd>
> +      </dl>
> +      <p>
> +        Given the options above, developers need to be mindful of the
> +        end-user's privacy with respect to their preferred language. Sending
> +        the user's preferred language in the clear is generally not ok, as it
> +        reveals personal information about an end-user. As such, developers are
> +        encouraged to use [[TLS]] to reduce the chances of pervasive monitoring
> +        of their Web applications [[RFC7258]].

I'm going to try to clarify that it's for when the user explicitly provides the language (i.e., not applicable so much for Accept-Languages, as those are usually just pre-configured in the UA). 

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/434/files/a8e3a8c6daf13bed5b3fc73bbcbde305880e6a53#r57104273