Comment from the i18n review of: http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/
Comment 8 At http://www.w3.org/International/reviews/0711-xhr/ Editorial/substantive: S Owner: AP Location in reviewed document: send() Comment:At the end of the section on the send method, this para appears: -- If the user agent implements server-driven content-negotiation it should set Accept-Language, Accept-Encoding and Accept-Charset headers as appropriate; it must not automatically set the Accept header. Responses to such requests must have the content-encodings automatically decoded. [RFC2616] -- The Accept-Language header is currently the only mechanism available in XHR for locale management. It may be important for locale-sensitive interactions to convey a language or locale to the server. Thus, it would be useful to separately mention the Accept-Language header and its use in informing the server of language/locale preference. In addition, we suggest you recommend the use of the BCP 47\'s Lookup algorithm(found in the RFC 4647 portion of BCP 47) for matching the A-L header. Note: the normative words \"should\", \"must not\", and \"must\" all appear in non-normative form.
