Talk:Universal Language Selector/Design/Interlanguage links

Feel free to provide any feedback

Please make it stick across devices so that it works across handsets, tablets, and desktop
We've long talked about this feature and in a multi device world we shouldn't have to train each of our devices about what languages we speak Tfinc (talk)
 * Thanks for the feedback. That makes a lot of sense. There is no need to repeat the learning process once per device. Pginer (talk) 01:41, 11 February 2014 (UTC)

Reports
Now that the code landed in the ULS repo \o/ can we file bugs and enhancement requests in the ULS component? --Nemo 11:06, 5 March 2014 (UTC)
 * Well, I filed two before I forget, with [Interlanguage links] label. --Nemo 21:57, 6 March 2014 (UTC)

ULS in "personal" position
What's wrong with this feature when the ULS trigger is in the personal tools position? It works just fine for me on after enabling it in preferences, the ellipsis button is very clear and the language selector opens in a sensible way. --Nemo 20:55, 6 March 2014 (UTC)
 * Removed from ULS, filed a bug. --Nemo 07:32, 7 March 2014 (UTC)
 * Thanks for reporting this. There are a couple of related improvements we are working on:
 * Make sure that the beta feature is not listed as a beta feature on those wikis where it cannot be applied to avoid confusion.
 * Use a more accurate way to determine if the feature should be available for a given wiki. Currently the ULS position is used as a conservative way to make sure the feature only applies to wikis where we are sure interlanguage links exist. We can base this logic on $wgInterwikiMagic and $wgHideInterlanguageLinks instead which are the variables directly related to the use of interlanguage links on the sidebar.
 * --Pginer (talk) 11:52, 7 March 2014 (UTC)

Confusing selection of languages
Visiting no:Oslo with the eetension turned on I got
 * (af) Afrikaans
 * (am) አማርኛ
 * (an) aragonés
 * (ang) Ænglisc
 * (ar) العربية
 * (arc) ܐܪܡܝܐ
 * (en) English
 * (nn) norsk (nynorsk)
 * (se) sámegiella

Nynorsk is a variant of Norwegian and is correct, Northern Sami is another language used in Norway. English is a common secondary language. Due to the number of people in Norway from other countries I would expect to find Swedish (sv), Danish (da), Deutsch (de), and perhaps Urdu (bal), Finnish (fi), Russian (ru). In addition I would expect to find Icelandic (is) and Faroese (fo) due to geographical closeness and similarity of language.

In short, the present list of languages seems weird. 109.247.163.112 10:41, 29 March 2014 (UTC)


 * Hi. Can you please put this on the Talk page instead? Thanks! Niharika (talk) 16:18, 29 March 2014 (UTC)


 * Done.
 * See FAQ "How does Universal Language Selector determine which languages I may understand?".
 * http://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html#NO doesn't have any of the languages you mentioned, please file bugs to them as explained in the FAQ. --Nemo 08:32, 30 March 2014 (UTC)
 * From your list of languages it seems that the system detects three languages that are relevant to you (en, nn, se) and the rest are filled with the first 6 languages the article is available in alphabetical order. With the recent version that was deployed of this beta feature, those less-meaningful 6 slots will be filled by other languages based on your previous choices. Additional criteria is considered for the future to make these "free slots" as meaningful as possible, but it it is not implemented yet. Thanks for your detailed feedback, and feel free to provide more as the feature evolved. --Pginer (talk) 07:56, 4 April 2014 (UTC)

Featured articles/lists
FAs and FLs should be displayed correctly, preferably given priority. I'm in a FL page, and I need some information that might be available from other languages with FL status, but I can't find the familiar yellow star on the short list nor in the pop-up. Bennylin (talk) 15:27, 10 April 2014 (UTC)
 * I totally agree with Bennylin. --151.231.110.157 20:04, 11 April 2014 (UTC)

exclude closed and locked projects?
On it.wikisource I get Aenglisc (ang) as the first language of the list. This is rather weird, not only because the language is dead since many centuries, but even more because ang.source has been closed ages ago. Can you guys just directly exclude it (and possibly others, like ht.source)? I cannot think of any reason why somebody should want to visit a project which is closed and has very little content, if any. Thanks Candalua (talk) 22:29, 10 June 2014 (UTC)
 * ULS doesn't add any link, it only filters those which are already there. I don't think this sort of filtering should be done in ULS: if you think closed wikis shouldn't be in interlanguage links, you should either get them removed from sitelinks in wikidata or file a bug for them not to be used (I think I already saw this request, might be in WikimediaMaintenance, Wikimedia>General or Wikimedia>Site requests). --Nemo 17:07, 11 June 2014 (UTC)


 * Already tried to have sitelinks removed :D but some people insisted they should be there (I don't understand for which reason, but I suspect only reason was to "see that all domains have been added and none is missing"). Anyway apart from the fact that ang.source is closed, I don't really get the rationale of the links I'm getting. Intuitevely, I think one should get the languages which are more important world-wide, or which are spoken in his/her region or country, or are related in some way to his/her language. But what I'm getting is: Aenglisc, Arab, Catalan, German, Greek, English, French, Hungarian, Slovenian. Not even Spanish is there, how come that Aenglisc is?! Candalua (talk) 19:41, 11 June 2014 (UTC)


 * IIRC there are configuration settings that a wiki could use to exclude some target sites from the interwikis. Sadly, "ang" is there simply for reasons of alphabetical precedence. You're right that the language selection is very bad, that's something that needs to be worked on case by case: for Italian see 62346, it was a big effort but it should be much better after CLDR 26 is released (September). --Nemo 19:50, 11 June 2014 (UTC)

Some languages are missing
I noticed that: and maybe other inter-wiki links with more than 2 characters to define "language code" are missing from the side bar once "Compact language links" are enabled. Kazkaskazkasako (talk) 08:50, 30 June 2014 (UTC)
 * bat_smg
 * be_x_old


 * It's not about length, it's probably Language codes / 19986 striking again: invalid language codes don't work well with the language selector (or don't work at all). --Nemo 09:05, 30 June 2014 (UTC)


 * @Nemo: thanks for noting down this bug! Kazkaskazkasako (talk) 15:43, 28 July 2014 (UTC)

Edit manually
I just activated the new Beta function, as the first on the german wikipedia (yay!). How ever, the inital languages it shows (Alemannisch, العرب, Boarisch, català, English, français, italiano, lumbaart, rumantsch) are completely irrelevant to me and I'm missing a direct way of editing them (add, remove, sort) cause it should look more like (Deutsch, English, Alemannisch, français).--Sevku (talk) 19:29, 13 March 2014 (UTC)
 * I'm the first who have activated it on the Dutch Wikipedia and I have the same question. - Supercarwaar (talk) 19:54, 13 March 2014 (UTC)
 * For context, the list comes from here: . And if I understand correctly, when it comes to languages considered by CLDR in use in the country, it picks the first by number of speakers to reach the amount of 7-9. Languages that one has previously selected in ULS should come first in theory? I tried to select Latin but I don't manage to get it to the list. --Nemo 21:17, 13 March 2014 (UTC)
 * First, thanks for your interest in the feature and providing detailed feedback. Our design goal is to make a set-up process unnecessary by making it unnecessary to select a language more than once it if was not included in the initial list (since your last choices should be remembered). However, it seems that some of the criteria for selecting the relevant languages are not working yet. In particular previous choices should be the most important criteria to make a language appear in the initial list and are not working now. In a context where selecting a language to access content makes it appear the next time, there is not much need for having a specific set-up process, but once the criteria for anticipating languages is working, we can reevaluate this --Pginer (talk) 12:54, 14 March 2014 (UTC)
 * Automation is NEVER going to work in a satisfying way if it is about choosing languages for a user. This is a problem that is almost as old as the WWW. One of the main reasons is that language and geographical information doesn't correlate too often. There are so many different reasons it can go wrong - a person moving to another part of the world, a person studying or using a "distant" foreign language, a person belonging to a minority, a person living in a non-English part of the world, a person just wanting to find a date or a picture (in any language)... Automation is overkill in a situation where there is only a few hundred languages to choose from.
 * I had the same problem on Portuguese Wikipedia: the list I got when I used pt-BR in my preferences was not really interesting. For now, I prefer to keep using a hack: b:pt:User:Helder.wiki/Tools/FilterInterlanguageLinks.js. Helder.wiki 16:04, 14 March 2014 (UTC)
 * I would also vote a feature to make prominent language I have an interest in. The showed language are not relevant.  --198.48.204.201 03:43, 24 March 2014 (UTC)


 * Showing languages I have showed an interest in does not always work. I often use iw links of languages I do not understand, e.g. to find files to use, or languages I understand only rudimentarily (but associated with the subject of the article), to perhaps get a hint or reference about a missing or dubious statement. Having these languages permanently added to the shorter list makes its contents more or less randomly chosen. Personally, I probably will use the complete list, but such "pollution" of the short list will probably annoy many users and have them refrain from checking exotic languages - which is a very nice aspect of using Wikipedia. --LPfi (talk) 14:49, 24 March 2014 (UTC)


 * Why is this still not implemented? This is the best form for user, and easier for devs, user choose what he wants not some script that is irrelevant. -- (Oxmaster (talk) 17:59, 9 June 2014 (UTC))
 * Have you tried recently? There was a patch some time ago which should have helped this. --Nemo 17:14, 11 June 2014 (UTC)
 * Can't see anything new, list still appears like this when browsing eng: العربية Български Bosanski Català Čeština Deutsch Lietuvių Polski Українська, I only understand 1 language from these, and I don't need whole list of 7 langs when I'm using only 2. -- Oxmaster 15:04, 16 June 2014 (UTC)
 * So you want to reduce the number of languages shown? Nothing was done about that, there isn't a bugzilla report either. Worth testing: if I manually select a language from the language search, does the same language automatically show up next time? --Nemo 15:07, 17 June 2014 (UTC)

Feedback form German WP
Hi, some feedback at german WP: The selection of interwikilinks is apparently automatic and very intransparent, not like a whitelist. See de:Wikipedia:Fragen zur Wikipedia/Archiv/2014/Woche 18 (28. April 2014). --Atlasowa (talk) 11:37, 28 April 2014 (UTC)
 * From what I can see from a machine translations, users over there only pointed out that what's statistically good on average won't be perfect for everyone. French and Danish, the two languages the user was looking for, should probably be higher in the list for German users: certainly before Greek, for instance. KaiMartin,YMS, please see in the FAQ how you can get the default order improved. We need your help! --Nemo 07:05, 5 May 2014 (UTC)

Needed improvements

 * 1) Ability to set a list of specific languages in user preferences.
 * 2) Always (?) list the "fall-back" languages of the local wiki and the user's home wiki - WMediaWiki already knows what these are, if they are defined.
 * 3) List the language the user has set for the interface - if not the wiki-native language.

For signed in users the wiki has useful knowledge, which we should use.

Rich Farmbrough 11:32, 2 May 2014 (UTC).


 * We're not going to add new preferences.
 * Home wiki perhaps, see below.
 * Interface language... that would be easy, but it would make the distinction between interface and content language even more intricated. --Nemo 20:37, 15 July 2014 (UTC)

Customization
How can I edit which languages are relevant to me? --Wikitiki89 (talk) 18:45, 1 April 2014 (UTC)


 * Hi. If you pick a language once, it'll automatically appear in your list from next time, if an article is supported in that language. You don't need to explicitly select languages. If you're still not satisfied, you could give us some more details here about where you are from, what languages you see, and what'll you like to see for a popular article such as Water. Or file a bug for it on Bugzilla. Thank you. Niharika (talk) 12:44, 2 April 2014 (UTC)

What happens if one clicks many languages once? I assume (hope) they are not all shown afterwards? It often happens to me when checking multiple articles for specific graphics – I just click all languages, even if I don't understand them which is why I normally wouldn't select them afterwards anymore. --Patrick87 (talk) 12:57, 2 April 2014 (UTC)


 * No, not all will be shown afterwards. The most recent 2-3 only. We will increase/decrease this number based on feedback. Niharika (talk) 17:44, 2 April 2014 (UTC)
 * I think it would be better to be able to customize it more. I like to read in many languages and I don't want my most common few (which itself is around 5 or 6) to be kicked out by some random languages I decide to check out. --Wikitiki89 (talk) 00:02, 6 April 2014 (UTC)

I object to the tool learn which languages I prefer from saving my edits. This violates users' privacy. If you introduce a tool like this would you please make it opt-in only. – If you would like to receive more feedback from me please ping me on German or English Wikipedia as I do not read here regularly and I have notifications switched off here. Thx.--Aschmidt (talk) 00:15, 23 April 2014 (UTC)
 * Edits are suggested in the section below but that's not going to happen for performance if anything else. --Nemo 20:37, 15 July 2014 (UTC)

Fetch default language list from user contributions
For logged-in users, can we make it fetch the preferred language list from the list of wikis the user has contributed to? For example, if a user is active in zhwiki and frwiki, the default language list will automatically be populated with links to those wikis when the page available in that language. Or, fetch the language list from a subpage in userspace, like Special:MyPage/PreferredLanguages (Some protection needs to be set up to prevent other users from editing it, like the *.js and *.css files). Anyway, I think the GeoIP solution works well for anons. Zhaofeng Li (talk) 14:27, 9 July 2014 (UTC)


 * The subpage is not feasible; perhaps we could use the babel information as they do in Wikidata, but it's quite hacky. Contributions to other wikis are not known to MediaWiki; the best I can imagine is accessing the "homewiki" from CentralAuth, but it would be a weird dependency on another extension. --Nemo 20:37, 15 July 2014 (UTC)

Language related to the topic
Two more things. [...] And then ideally (although it would need extra information to be provided), an article should have an "article preferred interwiki" (i.e. not user preference). What I meant is, for language related articles, for example, ideally one of the shown interwikis should be from that language's Wikipedia article (when available). Granted it might not work for all articles, but most of the time I want to know what the speaker of the language said about that topic in their own language. Bennylin (talk) 13:32, 20 March 2014 (UTC)
 * I don't think this will be possible. Perhaps a user javascript may do this by fetching some additional metadata from wikidata. Sometimes there may be coordinates associated to the current page, that we could use in theory for a second geolocated language guess, but sounds far fetched as well. --Nemo 20:37, 15 July 2014 (UTC)

Opinion
The idea is really great but I can not see usefullness if there won't be an option to manually select languages by user himself. The user must decided which languages are not needed to him. He also must have an option to sort languages from #1 to #111 (for example) as he wish. With regards, --Janezdrilc (talk) 21:42, 25 July 2014 (UTC)

Question
I turned it on my account at id.wiki, but the iw links didn't change. It worked on my beta-wiki and en.wiki accounts. It didn't work even when I switched the skin from mono to vector. Is this a known bug? Bennylin (talk) 19:53, 14 March 2014 (UTC)
 * Works for me on id.wiki. Probably some local gadget or script of yours interfering? --Nemo 21:23, 14 March 2014 (UTC)


 * Works for me on id.wiki as well. --Niharika


 * I logged in as my robot, and it works. Still didn't work with my main account too even though I've tried deleting my scripts (id:Pengguna:Bennylin/common.js and id:Pengguna:Bennylin/monobook.js). Strange... Bennylin (talk) 12:02, 18 March 2014 (UTC)

Misplaced pop-up
Unfortunately this was a one-time issue I can't reproduce: the pop-up was misplaced, half hidden in the top left corner of the screen. This can be easily avoided by limiting the top and left position to positive integers. (With something like Math.max(0, x).) --TMg 15:17, 14 March 2014 (UTC)
 * Are you facing issue like, http://i.imgur.com/QLyM4sI.png here? --KartikMistry (talk) 15:31, 14 March 2014 (UTC)
 * Yes, exactly. It seems this is independent from the browser. Possible explanation: Parts of the menu on the left side collapse on page load. This may confuse the code that calculates the position of the pop-up. --TMg 14:31, 15 March 2014 (UTC)
 * same her (latest chrome, mac os). --Sebaso (talk) 08:17, 16 March 2014 (UTC)
 * This looks bad. Not exactly sure what's causing the issue. Will look into it as soon as possible. Thanks for reporting this. --Niharika (talk)

Source code?
Where is the source code of this thing? --TMg 16:19, 22 March 2014 (UTC)
 * --Nemo 17:30, 22 March 2014 (UTC)

Accept-Language header
HTTP has an Accept-Language header. Is this used? For those who have configured it, it lists languages which the user should like to be offered. Where a default is offered, it is probably a language the user knows at least to some extent. Using the information is no privacy problem, as the information is there already (and a browser could choose to send the information only to trusted sites). --LPfi (talk) 15:09, 24 March 2014 (UTC)


 * Accept-language header is used. I just checked to tweak it from the browser and the new language I added was appearing. Please, let us know if it is not working in your case. --Pginer (talk) 16:21, 24 March 2014 (UTC)


 * Sorry, I thought it was not mentioned in the documentation. Now I see it. --LPfi (talk) 11:59, 25 March 2014 (UTC)

my comments
sorry but for now i don't like it. shortening the list is one thing but a smart selector is another. maybe after working on the problems it'll be helpful.
 * in general i like seeing the plenty of languages and if there's place i say show the more - its a beauty :)

specific problems/bugs:
 * i cant reach the other languages - the rest of the list - '...' button doesn't work 99% of the time
 * when jumping to another wiki i get the old version, a different display. so beside a short list it adds nothing.
 * for now the selector has no 'sense' of my preferences. and i dont think it'll really have one, cause beside English i check other languages rarely and for different reasons and needs (for example i read also french but its not on my list, but i guess i checked the German wiki as often so...). or the cause might be my privacy settings?
 * The selector haven't got enough data thats sure - shows me afrikaans after english, arabic below that - no logic... so i guess it smart to recognize i read english and beside that its an annoying forced cut or is it something else? im an israeli - might be a relevant data.

GL, Dalilonim (talk) 14:57, 12 April 2014 (UTC)

More languages
The search should also show minor languages like Cree, Cantonese, etc. --Hmmfery (talk) 02:26, 4 May 2014 (UTC)
 * What makes you think that it doesn't? Works for me, e.g. on . --Nemo 06:58, 5 May 2014 (UTC)

Half-hidden in hebrew.
I use the Opera Next browser v21.

Labels look like links but aren't
Please make the blue labels in the UI actual links I can open by clicking the middle mouse button, for example. --TMg 15:17, 14 March 2014 (UTC)
 * Thanks for the feedback. You are right, links on the language list should be real links. I've added this to the list of issues to be fixed. --Pginer (talk) 16:01, 14 March 2014 (UTC)

Two more things. For the extra interwikis, I can't middle click or Ctrl+click the link to open in a new tab too. [...] Bennylin (talk) 13:32, 20 March 2014 (UTC)
 * I split your message across the two sections which deal with it. This one is tracked at 64797. --Nemo 20:37, 15 July 2014 (UTC)

Interwiki titles
One of the good thing of having the old interwikis are for comparing titles between 'pedias. For example in the name of a person, does the majority of 'pedias use X or Y, or in the name of species, Latin or common, or geographic entities. Therefore reducing them to select few limits this functionality. Even after the "..." button is clicked, user still can't see the titles in other 'pedias (not even in mouse hover). A Wikidata-like list would be very useful, and an improvement over the old interwikis.

Also, can we select the short-list through our preferences? The autodetect isn't functioning properly; for example it tend to shows ar.wp and af.wp (alphabetical?), where I would prefer ms.wp and fr.wp. Bennylin (talk) 12:10, 18 March 2014 (UTC)
 * Thanks for your feedback. I added a new issue in our list about preserving the title information on language links. That would make the new language links to behave closer to the current ones. The auto-detect functionality not working is already a known issue, and there is already a fix for it in progress, so it should be working soon. --Pginer (talk) 10:09, 19 March 2014 (UTC)

Besides the articles title being shown in the links pop-up title also remember to restore the translated language name to be shown in the pop-up title that was added this year (5231) – also in the pop-up language select. --Patrick87 (talk) 21:15, 20 March 2014 (UTC)
 * The localised title on hover is working for me. --Nemo 19:22, 15 July 2014 (UTC)

Line height
The gray text at the bottom breaks in certain languages. For example in German it says "20 weitere

Sprachen" with a much to big line-height. --TMg 15:17, 14 March 2014 (UTC)
 * I've tried the Obama article with "195 weitere Sprachen" and it fits on the small window sizes for both Chrome and Firefox with and without the typography refresh, so I could not reproduce that (is there any beta feature / gadget that could be affecting this n your case?). One of the plans for the future is to integrate the label into the button with a shorter text ("X languages") which should reduce the issues. In any case we'll also need to review the line height for those cases that text requires a new line. --Pginer (talk) 16:14, 14 March 2014 (UTC)
 * The line break is not the problem. It can't be avoided in all languages. The line height is wrong. --TMg 14:06, 15 March 2014 (UTC)

Search functionality obfuscated
The search box at the top of the UI doesn't look like a search box. It looks like a headline. The only hint that you can type something is the blinking text cursor. This is bad for usability. And it's strange since the same UI element in the ULS language selection actually does look like an input field (example screen shot). It does have a border. This one does not. --TMg 15:17, 14 March 2014 (UTC)
 * Apart from the blinking cursor, the magnifying glass icon and the "search languages" placeholder text help to identify this as a search bar. The decision of avoiding too many boxes is to try to simplify the UI (the search bar occupies all the space on top becoming the main entry point since the map is not used here and it is more closely connected to the list of languages that it filters). During our tests with users we found no issues identifying and using the search bar, but we'll keep paying attention to it. --Pginer (talk) 16:26, 14 March 2014 (UTC)
 * I can't believe this. This is oversimplifying. Microsoft tried the same in a lot of places in Windows 8 and failed horribly. Nobody understood he can simply start typing without having an input field. Did you told your test users there is a filter functionality or did they found it without knowing it is there? Users are looking for search boxes. That's why every search engine still uses a small input field with a clearly visible border. But in this case there simply is no search box. Neither the icon nor the text make it clear that the list can be filtered by typing. Both look like labels for the pop-up (that's the purpose of the pop-up, to "search for a language", right?). The Winter experiment does have the same major design flaw. And the main question remains: Why do think it's a good idea to make every UI (the Beta checkboxes, the new Special:Search, and basically every pop-up in every extension recently developed by the WMF) look different? I once learned being consistent is a major aspect in usability. --TMg 14:27, 15 March 2014 (UTC)

"More" shouldn't show same languages again
I expected the "..." button to show what it says: more languages. Instead it's like it shows the same languages again (with the completely generic headline "Sprachen" in German), plus some more. I find this confusing. Are these two selections of "common" languages based on two different assumptions? --TMg 15:17, 14 March 2014 (UTC)
 * There are a couple of aspects to consider here. The initial list is supposed to be very short, so the first section of the language list ("Common languages") will leave more room for languages the user is interested in. The reason for keeping the initial languages also on the language list is to allow the language list to be able to find all languages. This is useful if you overlook a language in the initial list or went directly to the more languages list due to muscle memory. Having said that, I can imagine that for cases where there are few languages in addition to those in the main list, the "Common languages" section could possibly be skipped. I'll add a note on the future explorations for adapting the language list to few items. --Pginer (talk) 16:43, 14 March 2014 (UTC)
 * I understand and agree that having the "commons" section in the pop-up is probably a good idea. But it should be the same as the languages in the sidebar. Currently it's almost the same, sometimes with one or two more languages, sometimes with one or two missing, sometimes almost empty with a single language only. I don't see the benefit of this. It feels like it's random (the user can not understand the rules from comparing the two lists). And as I said the headline of the "commons" section is bad in German but I couldn't find the message (?uselang=qqx is ignored for some reason). PS: Found it. --TMg 14:42, 15 March 2014 (UTC)
 * If you take a look at the testing recordings, users were asked the following: "Could you search for the 'Mona Lisa' article, and access it in Spanish, Dutch, French and Russian" (you can see the tester box on the top-right area of the screen). They were asked to access the article in different languages which aligns with the user goal regardless of the technical means provided to do so. Those were part of some tests done through usertesting.com. On one-on-one tests with users we followed a similar script (but also asking a more open version of the question initially: "access the languages you know"). In that case, we were able to have a conversation and ask why users made use of the different entry points, and even the users that didn't used search seemed to be aware of the search capability. Once the "known issues" section gets reduced, I'll plan some tests for the current feature. Then, we could check again if the problem appears. --Pginer (talk) 09:43, 19 March 2014 (UTC)

It keeps annoying me.
The … button stands out too much, distracting from the rest of the page. Please remove it, and instead make the " n more languages" text clickable. Keφr 19:48, 15 March 2014 (UTC)
 * Oppose. I love this extremely simple button with no text. Please keep it and don't make it bigger by switching the "…" with text. --TMg 11:26, 16 March 2014 (UTC)
 * My reflect was to click the 73 more languages instead of the ellipses. Bennylin (talk) 12:16, 18 March 2014 (UTC)
 * Me too. I was somehow subconsciously confused by the "…" at first sight which I think is a bad sign regarding UI design and usability. When clicking "…" I was even more confused since I would have expected the hidden languages to be somehow unfolded (as normally when three dots are used to omit sth. somewhere) but surely not a new UI dialog to pop up. I'd favor the proposed solution below (incorporate number of languages into a button) which will actually make the UI less distracting in my opinion (by saving one UI element). --Patrick87 (talk) 21:06, 20 March 2014 (UTC)
 * There is a benefit in having an entry point for switching languages that is understood in any language, but it is also true that the indicator of the total length could be understood as the entry point. We have explored several solutions:


 * Integrate both (example design) . While keeping the universal icon and avoiding the multiple-entry point problem, the main entry point becomes slightly more complex than it was.
 * Make the "X more languages" also to act as an entry point. Although it could make it work for users that click on it, having two separate entrypoints for the same thing next to each other seems not to be the best solution.
 * Remove the "X more languages", if the "..." is enough to indicate that there are more languages, do we need the specific number? While it is not strictly needed (it is not provided with the current language links), I think it communicates the multilingualism of our project and helps to answer a reasonable question ("in how many languages is the article available?") easier than what we currently are able to. I prefer to keep this info but I'm open to present it in a different way (popup? as part of the search field placeholder?). ---Pginer (talk) 09:58, 19 March 2014 (UTC)
 * The number is totally misleading. Because the extra interwikis are presented per continent basis (in itself is a bit problematic), some languages occur several times in several continents, i.e. France, English, Nederlands, etc. When it said 5 links, I expect to see the 5 links that were not in the short list, instead I get the full list, with the aforementioned redundancies. Bennylin (talk)
 * The list of languages was initially designed to select from all languages, addapting it to work well with fewer languages is something in our todo list (more details on the "Adapt the list of languages to accommodate a reduced number of languages" point on the "Suggestions for improvement" section) --Pginer (talk) 07:48, 4 April 2014 (UTC)

I would like it if the x more Languages would simply expand into a list of the remaining Languages.--Saehrimnir (talk) 18:22, 25 March 2014 (UTC)

Language variants selection
I really like the compact list. This helps me not to scroll down long list for some page to look after Chinese in English Wikipedia. And in Chinese Wikipedia, I also spent less time for looking for English related wiki.

This is a bug(51242) talking about the Support language variant selection at ULS, which suggest adding language variants in the language list instead of top bar right after Page/Discussion. I think it's pretty great to integrate language variants in ULS and looks good to UX transition. But experienced user use this feature heavily. And some technical problem force us to keep this selection in a outstanding position cause some ordinary reader often mislead to a language variant they don't want to, usually comes after a url.--Fantasticfears (talk) 07:32, 23 March 2014 (UTC)

Confused
I know I'm simplifying things, but what is wrong with Use JS to add some knobs and to persist the user's choice in his or her profile, and you should be done. Paradoctor (talk) 21:58, 26 March 2014 (UTC)
 * 1) p-lang li {display:none}
 * 2) p-lang .interwiki-de,
 * 3) p-lang .interwiki-es,
 * 4) p-lang .interwiki-fr,
 * 5) p-lang .interwiki-en {display:list-item}


 * I think that's an excellent suggestion. It'll resolve quite a few complaints. I'll work on it. Thanks! Niharika (talk) 02:53, 27 March 2014 (UTC)


 * Niharika, have you worked on this? Is there a bug report detailing the requirements? --Nemo 17:45, 15 July 2014 (UTC)
 * For context, each bullet currently looks something like this: . So we already have the class interlanguage-link to manipulate all links at once, and classes like interwiki-it to manipulate them on selected languages. --Nemo 21:10, 15 July 2014 (UTC)


 * Nemo, I did this quite some time ago. Patch ID 121296 in gerrit.


 * I think Paradoctor meant you could hide the interwikis via CSS rather than JS manipulation, but that's not trivial to do. --Nemo 06:58, 22 July 2014 (UTC)

Something in this beta feature is incompatible with edit button styling in Fixed header / Winter experimental beta feature
http://imgur.com/pbdD1NK This is currently only enabled on beta labs, but I need to fix it sooner rather than later. Any idea what might be causing this? Any way the styling could be limited to the left menu? Jdlrobson (talk) 21:35, 28 March 2014 (UTC)


 * Hi, I'm not sure what's causing this issue. Could you point me the JS/CSS files you're using for the button styling? I'd like to see if the elements share any class/id by mistake. I'm just guessing here. Niharika (talk) 12:56, 29 March 2014 (UTC)

Not working with SidebarTranslate
This beta feature is incompatible with gadget SidebarTranslate.--Wikiuser13 (talk) 13:21, 2 April 2014 (UTC)


 * Thanks for pointing this out. I'll work on it. Adding it to Known Issues list. Niharika (talk) 17:46, 2 April 2014 (UTC)
 * Related thread there, at en:User talk:Equazcion/SidebarTranslate. (No response, just a note of the bug). –Quiddity (talk) 19:47, 2 April 2014 (UTC)

Screenshots for the docs
Hi. Please add some screenshots to the project page, so that we can see the various components in action. Thanks :) –Quiddity (talk) 16:17, 12 May 2014 (UTC)


 * Hi. Will do that. Thanks! NiharikaKohli (talk) 03:59, 17 May 2014 (UTC)

Is anything happening with this feature?
Is anyone carrying about this getting into live form? – Oxmaster (talk) 16:10, 15 July 2014 (UTC)

Memory
This tool does not remember which languages I use most. Gryllida 03:21, 1 August 2014 (UTC)
 * Use most where, in ULS itself? --Nemo 06:54, 1 August 2014 (UTC)
 * When reading articles, I have to search for a language manually. I do it by clicking '...' and searching for it in the small popup.
 * I have to keep doing this across different sister projects by hand. And since
 * the popup is slower to use than scrolling down a long list, and
 * it remembers only for one sister project at a time,
 * I get a negative impression in short-term. (In long-term, I'd've done this across all sister projects, and I'd be all set. It's a laborious process.) --Gryllida 05:08, 9 August 2014 (UTC)
 * The lack of a global settings system prevents the system to learn from what happens in different wikis. But even in the initial scenario, having the possibility to search for the language provides more flexibility in finding your language than what we currently have. -- Pginer (talk) 07:55, 15 August 2014 (UTC)

I don't like it.
I prefer the old desing and I spent some time to switch off the new. Ich mag die alte Form lieber, und mußte lange suchen bis ich auf die alte Form zurückschalten konnte. --Steiger4 (talk) 15:20, 15 August 2014 (UTC)