Add note about i18n

[marcoscaceres]

The note should include:

• The spec should details how we expect developers to localize content. Like by: <link rel=manifest href='manifest?lang=en'>
• An example showing the use of a language other than English.
• Add discussion of obtaining a correctly localized reference, particularly for use in cases where the source page itself has used language negotiation.

[mounirlamouri]

With the current Manifest 18n support, it seems that HTTP headers could do?

[marcoscaceres]

There is a ton of things that could be used, from geo-ip lookup, to HTTP headers (accept-language or whatever), a URL string, and just simply allowing the user to choose their own language (and update the link element's URL, as above)... basically, whatever sites do today. It all works, and it's all good 💃

[kenchris]

can this be closed?

[marcoscaceres]

Not yet, no. I'll send a PR soon.

On Tuesday, March 17, 2015, Kenneth Rohde Christiansen <
notifications@github.com> wrote:

can this be closed?

—
Reply to this email directly or view it on GitHub
#323 (comment).

[marcoscaceres]

An example showing the use of a language other than English.

I used French, because I like to include @mounirlamouri.

[himorin]

Note: W3C i18n WG closed our tracker with actions taken satisfactory. (please not remove i18n-needs-resolution label which is used by our bot and tracking system)