You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@agjohnson mentioned in #4600 that RTD was looking into redirecting users to a translation that matches their browser's language.
User requested /, redirect to /<default language>/<version> if no accept language header, or /<accept language header code>/<version> if there is a header. This change is relatively easy and we have an issue already tracking this internally.
I was just looking to see what happened with that suggestion.
Thank you,
Austin
The text was updated successfully, but these errors were encountered:
AustinShalit
changed the title
Revive #4600
Revive #4600 (Redirect to Translated Docs)
Sep 9, 2020
I'd still like to see this happen, and we're probably more equipped for this now that we have an application in front of all requests that serve documentation. I'm not sure what priority we have on this though, we'd probably want to get up to date figures on how many projects have active translations.
humitos
changed the title
Revive #4600 (Redirect to Translated Docs)
Automate locale selection for documentation pages
May 10, 2022
Hi folks,
@agjohnson mentioned in #4600 that RTD was looking into redirecting users to a translation that matches their browser's language.
I was just looking to see what happened with that suggestion.
Thank you,
Austin
The text was updated successfully, but these errors were encountered: