Makes sense! I actually hadn't factored in that sort of action
(although it does happen), more: the order of the main page links on
the root www.wikipedia.org page.
On 7 May 2015 at 03:51, Scott Hale computermacgy...@gmail.com wrote:
The accept-language header is the obvious place to start, but
The accept-language header is the obvious place to start, but there is
amble scope to combine multiple approaches together.
In addition to accept-language and geolocation data, any logged in user
will have view/edit history related to multiple editions. If the user is
requesting a specific
Accept-language is systematically broken for minority languages within
dominant language communities. In New Zealand, a country with three
official languages and a textbook case of language revivalism, I've never
met anyone without a degree in computer science who sets accept-language,
and I've
Thanks for looking into www.wikipedia.org traffic from India; I've been
complaining about it for a while. :) See also:
* https://phabricator.wikimedia.org/T26767
* https://phabricator.wikimedia.org/T5665
Mark J. Nelson, 07/05/2015 04:24:
But for the average Copenhagener, the following order is
Thanks for the bugs, Nemo!
(search team: should we take those over?)
On 7 May 2015 at 03:08, Federico Leva (Nemo) nemow...@gmail.com wrote:
Thanks for looking into www.wikipedia.org traffic from India; I've been
complaining about it for a while. :) See also:
*
Interesting! This I didn't know; I'll factor it in :).
On 7 May 2015 at 04:48, Stuart A. Yeates syea...@gmail.com wrote:
Accept-language is systematically broken for minority languages within
dominant language communities. In New Zealand, a country with three official
languages and a textbook
Scott Hale, 07/05/2015 09:51:
The accept-language header is the obvious place to start, but there is
amble scope to combine multiple approaches together.
Which is what UniversalLanguageSelector / jquery.uls, used on all
Wikimedia projects, exists for. :)
In addition to accept-language and
