Put the doc language in the doc url

[brson]

As suggested in http://ericholscher.com/blog/2014/feb/27/how-i-judge-documentation-quality/, our doc URLs should be future-proofed for translation by putting 'en' somewhere in them. Nominating.

[steveklabnik]

This has pros and cons. If you use Accept-Language, then you end up showing the correct language to whomever you link.

It's not as simple as 'put it in the URL' if you want to do it right. After a bunch of thought, https://github.com/jcasimir/locale_setter#how-it-works is what I came up with on this topic.

[kud1ing]

This has pros and cons. If you use Accept-Language, then you end up showing the correct language to whomever you link.

This depends on the implementation. The user should be able to adjust that "correct language".

[steveklabnik]

Exactly. All I mean to say is that 'put the language in the URL' isn't a universal solution; there isn't one.

[brson]

@steveklabnik Which of the techniques you suggest can work with a static site?

[darnuria]

There is some work who have made for Support Mozilla and MDN.
Just a little JavaScript code.
I can ask some peoples who work on it.

[steveklabnik]

@brson depends on what you mean by 'static site.' The tiny bit of logic here should be able to be done in an nginx or apache config. Think mod_rewrite.

[pnkfelix]

cc our localization story in #12553

[pnkfelix]

Assigning 1.0, P-low. (Felix would like to be able to hack on his urls to jump between french/english and between versions.)

[brson]

@darnuria I'm interested in seeing the MDN JavaScript code for locales.

[brson]

OK, after reading @steveklabnik's link here's my suggested plan of action:

• Change our artifact directory structure to contain a directory for locales, so where right now we have doc/1.0/std/ we will then have doc/1.0/en-US/std/. For now, while our i18n is poor, we can do this in the makefiles, but someday rustdoc may need to be locale-aware.
• Modify the doc.rust-lang.org nginx rewrite rules to pick the correct content based on:
  1. A URL &locale=es parameter
  2. A domain prefix, e.g. es.doc.rust-lang.org.
  3. The Accept-Language HTTP header

In the future, once we know how to properly build and distribute internationalized docs, we can teach rustdoc to be multilocale and add links to the &local=es, etc. URL's.

Since we don't need to have internationalized docs up for 1.0, not all of this needs to be done now.

[brson]

Though maybe we should pick either the URL args or the domain prefix, not both.

[brson]

Nominating for removal from 1.0. URL's can change later.

[pnkfelix]

Leaving as P-low, removing from 1.0 milestone list. No one wants to block the release on this issue.

[steveklabnik]

We have no i18n anymore, and so this isn't directly relevant. If and when we bring translations back, this is something that would need considered.