The second question is easy. Inspect the "Accept-Language" HTTP header, serve the page in the most preferred available language
-
Show this thread
-
But in this case, we would have a situation where, like, five out of the 655 pages on my site randomly appear in Hebrew, the rest in English
1 reply 1 retweet 2 likesShow this thread -
This would be very surprising behaviour, and not terribly helpful to someone expecting to read the whole story in a single language
1 reply 0 retweets 1 likeShow this thread -
Or even to someone expecting to browse the whole site in a single language
1 reply 0 retweets 0 likesShow this thread -
I know for a fact that it's not acceptable to, due to incomplete translation work, serve one web page in a mixture of languages
2 replies 0 retweets 0 likesShow this thread -
Replying to @qntm
Accept-Language is only good for discovering the default, you ought to redirect to /en/ afterward
2 replies 0 retweets 0 likes -
Replying to @codahighland
If I'm going to redirect to /en/ afterwards, why inspect Accept-Language at all?
1 reply 0 retweets 0 likes -
Replying to @qntm
To determine the user's preferred default on a first visit.
1 reply 0 retweets 0 likes -
-
Replying to @qntm
Determine which URL to redirect to, of course. :P That's what happens if you put e.g. "http://wikipedia.org " in the address bar.
2 replies 0 retweets 0 likes
But then redirect to /en/ every time?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.