Gebruikerbespreking:JMK

Page contents not supported in other languages.
in Wikipedia, die vrye ensiklopedie
Argief
Deel 1 Deel 2 Deel 3
Hoe word 'n argief aangelê?

Translation request[wysig bron]

Hello.

Can you translate and upload the article en:List of mammals of Azerbaijan in Afrikaans Wikipedia? Or is there a specific translation request page in Afrikaans Wikipedia where I can add it?

Yours sincerely Karalainza (kontak) 18:22, 27 April 2020 (UTC)Beantwoord[antwoord]

That is not a small job as we do not have ready made Afrikaans names for all those animals, but it is a good project to consider, thanks. I don't believe there is anybody on Afrikaans wikipedia who can immediately execute it, but given time, yes, good idea. JMK (kontak) 11:47, 28 April 2020 (UTC)Beantwoord[antwoord]

Valse vriende[wysig bron]

Goeie dag, waarvoor hierdie wysiging? Is daardie terme nie valse vriende nie? – K175 (skil 'n appeltjie) 16:52, 19 Augustus 2020 (UTC)Beantwoord[antwoord]

Het nie gedink dat hulle voorbeelde daarvan is nie. "Dutch" is bv. 'n valse vriend van wat? Van Duits? Ons het ook "Nederduits" en "Diets" in Afrikaans, wat albei Nederlands (of iets in dier voege) beteken, en dit beteken nie dat enige van die twee, of drie, valse vriende is nie. Hulle is eerder sinonieme, of verwante begrippe. En "Germany" is 'n valse vriend van Germanië? Ek voel hulle is effektief dieselde woord vir nouverwante onderwerpe. Wie se Germanië is in elk geval ter sprake, dié van die Romeine of dié van Hitler, of dalk nog iemand anders se idee daarvan? Sal versigtig wees om valse vriende toe te pas waar landsgrense of volksgroepe van toepassing is, want dis subjektiewe onderwerpe. JMK (kontak) 18:28, 19 Augustus 2020 (UTC)Beantwoord[antwoord]

Ontkiemingskompetisie is oop[wysig bron]

Hi JMK, die Wikipedia:Ontkiemingskompetisie/2020 is nou oop. Sal bly wees indien jy ook deelneem! Groete, -- Aliwal2012 07:14, 23 Desember 2020 (UTC)Beantwoord[antwoord]

Ek sien ek het in my TV onderhoud verkeerdelik na bogenoemde as SAS President Steyn verwys. Ouderdom... Groete! Oesjaar (kontak) 05:38, 4 Maart 2022 (UTC)Beantwoord[antwoord]

Ja, ek wou sien wat die offisier toe wel genoem word. In ieder geval, goeie inligting wat jy aan die publiek gegee het. En wat die teks betref, skuif ek maar die werkwoorde nader aan die einde van die sinne, soos die taalkundiges dit graag wil hê. JMK (kontak) 07:30, 4 Maart 2022 (UTC)Beantwoord[antwoord]
Dankie, ek lankal al agtergekom wanneer ek vertaal dat die Engelse grammatika my beïnvloed. Groete! Oesjaar (kontak) 11:55, 4 Maart 2022 (UTC)Beantwoord[antwoord]

Die vygies![wysig bron]

Dankie vir hulp die afgelope paar jaar! Sien vygies op Plants of the World Online. Ek gaan hulle lys van genera (geslagte) oordra na ons artikel oor vygies. Laasgenoemde is jare agter... Enige beswaar? Groete! Oesjaar (kontak) 14:16, 26 Julie 2022 (UTC)Beantwoord[antwoord]

Dit lyk reg, ons moet hulle net siteer. Ek het 'n paar fotos by die botaniese tuin geneem van een van die Beesvygies, Ruschia maxima, wat nuttig mag wees om daardie spesie of genus te beskryf.
Ek dink nie die individuele Ruschia-spesies het Afrikaanse name nie, miskien moet mens maar begin by Beesvygie/s, genus Ruschia. JMK (kontak) 14:26, 26 Julie 2022 (UTC)Beantwoord[antwoord]
Ruschia is geskep, ek het die vierkantige hakies vergeet! Miskien beter so! Geniet! Oesjaar (kontak) 18:39, 26 Julie 2022 (UTC)Beantwoord[antwoord]
Dankie! Sien nou hoekom hulle nie individuele volksname het nie, daar is net te veel. JMK (kontak) 07:42, 27 Julie 2022 (UTC)Beantwoord[antwoord]
En almal lyk amper dieselfde! Oesjaar (kontak) 07:43, 27 Julie 2022 (UTC)Beantwoord[antwoord]

Language switching[wysig bron]

Hello! When you pinged me about the issue with the order of the language links, I was not at work. But I'm back now.

Thanks for pointing at this problem. Personally, I'm not the subject matter expert but I know something based on what my colleagues have already posted.

Our team (Web) has only moved the language switcher from the sidebar to a separate menu. So we've only changed the location to increase the discoverability of any language(s). How the language switching works exactly (how relevant languages are suggested to a user) is within the area of the Language team. And what I know from them is this (this is a quote from this discussion):

  1. The language selector uses different clues to figure out which are the recommended languages. For example, top priority is based on the previous selections. That is, a user that frequently reads in French, Japanese and Igbo would get those always in their suggestions for pages available in those languages. Similarly, the browser languages are considered next if it was not possible to fill the suggestions with the previous criteria. Additional criteria can be considered in cases where it is hard to fill the suggestions because of the languages in which content is available (something which will vary significantly from page to page).
  2. Some of the criteria based on location or relation to content may need some polishing in some cases (data is based on CLDR [perhaps this is about Extension:CLDR? - SG] and can be improved). In any case, as mentioned above, for a user that speaks and uses a given set of languages, in practical terms the suggestions are going to surface those (even if some of the additional suggestions are sub-optimal at times). In contrast, with the classical approach of a flat list, a speaker of a language with low Wikipedia coverage would have to scan long lists of languages to find whether the content is available in theirs (which may not be in mosts cases), and they would have to do that every single time without the system making it easier after the first try.
  3. More detail about the criteria for suggested languages is described here. We also have some mockups of a more expanded feature.

Does this help you understand our thought process and how the software works? Please let me know what you think and if you have additional questions. Thanks, SGrabarczuk (WMF) (kontak) 22:38, 23 Januarie 2023 (UTC)Beantwoord[antwoord]

As usual you miss the whole point completely and it is a waste of time to communicate with you. The PLACE where you are hiding the language links now is unacceptable, BESIDES the ridiculous way that they are organized. PUT the language links BACK in the very visible left hand column WHERE THEY WERE FOR YEARS, and DO SO FOR EVERYBODY, otherwise we have to search for language links at a different place in every language version of wikipedia. If I try to work on a wikipedia version of a language that I don't understand I CANNOT EVEN SEE WHERE THE LANGUAGE LINK BOX IS! BECAUSE I CANNOT READ THEIR LANGUAGE! AND THEY CAN'T SEE US! You are meddling with things that worked perfectly for decades. AND THIS IS BY FAR NOT THEY ONLY PROBLEMS WE HAVE! JMK (kontak) 17:30, 19 Augustus 2023 (UTC)Beantwoord[antwoord]
Thank you. I want to make sure I understand your arguments, so I'd like to ask a few questions:
  1. "We have to search for language links at a different place in every language version of wikipedia" - what versions are you referring to? Eventually, we want all the versions to have Vector 2022 as the default. Now, only several don't have it.
  2. "I cannot even see where the language link box is! because I cannot read their language" - which wikis are you referring to? The location of the language button is the same regardless of the language, unless the old skin is the default.
"Things that worked perfectly for decades" - I don't remember now, but I think I might have shared the link to the page about the new language switching. In the section User testing, you'll find information that with the previous skin, (1) people weren't necessarily aware that interwiki links existed and they used other search engines instead (2) it took more time for people to switch between languages. Of course you may disagree as you have grown accustomed to the previous skin, but to the team, these findings meant that the old Vector did not work perfectly.
Last but not least, I'd like to add that the changes and projects the Foundation works on are not based on arbitrary choices of one individual, but on our annual plans (see the latest one). You are welcome to take a look at the next project of the Web team (it's a draft right now, the name may be temporary) as well as take part in the next annual planning. I hope that in less than a month, we'll officially invite communities to work on "Accessibility for reading" together. By taking part in the next annual planning, you'll be able to tell us what problems we should work on.
Thanks, SGrabarczuk (WMF) (kontak) 08:47, 21 Augustus 2023 (UTC)Beantwoord[antwoord]
The above answer in itself does not help either, but I am preparing some screen grabs which I'll post here. Of course I'll just waste my time again. JMK (kontak) 08:51, 21 Augustus 2023 (UTC)Beantwoord[antwoord]
Sorry for barching in, just bring back the previous skin. The current one is a disaster. Typical Wikipedia, a solution looking for a problem! My experience: 13200 articles later. Regards! Oesjaar (kontak) 08:53, 21 Augustus 2023 (UTC)Beantwoord[antwoord]