Hello, how to add interwiki in new articles, for example there: https://szl.wikipedia.org/wiki/Aktywacyjno_funkcyjo?
User talk:SGrabarczuk (WMF)
Cześć! Przepraszam, że nie odpowiedziałem wcześniej. To pytanie jest proste, ale odpowiedź chyba nie jest :D Jak sobie z tym poradziłeś? Pytam, ponieważ widzę, jak dodać artykuł do istniejącego już elementu Wikidanych, ale nie jestem pewien, jak to zrobić w przypadku nowego elementu Wikidanych. To jest technicznie poza samą skórką, stąd nie wiem, czy tu nie było jakichś zmian.
Cześć! Dzięki za odpowiedź, nie ma problemu, nie śpieszy się. Problem rozwiązałem dodając [[en: ... ]] na końcu artykułu. Następnego dnia EmausBot przerobił to na poprawne łączenie wikidata: https://szl.wikipedia.org/w/index.php?title=Aktywacyjno_funkcyjo&diff=prev&oldid=366471. Najszybsze rozwiązanie chyba obecnie, aczkolwiek niezbyt ładne.
Problemem jest właśnie jak dodać artykuł do istniejącego już elementu Wikidanych. Na polskiej Wikipedii np. tu: https://pl.wikipedia.org/wiki/W%C5%82adys%C5%82aw_Szyma%C5%84ski_(muzyk) jest przycisk "Edytuj linki pomiędzy wersjami językowymi". Na śląskiej np. tu: https://szl.wikipedia.org/wiki/Niklaus_Pieron takiego przycisku nie ma :/ wiadomo z czego to wynika?
Na śląskiej w biogramie Niklausa (oglądałem trochę, szanuję) jest "Dodaj linki wersji językowych". W wyróżnionym dziś artykule o piramidzie w Gizie jest w tym miejscu "Edytuj metajynzykowe linki".
Swoją drogą, można to przetłumaczyć na śląski, edytując MediaWiki:Wikibase-addlinkstitle/szl na Translatewiki.
O jaa, dobra, teraz znalazłem :D Wcześniej szukałem przy przycisku Dodaj języki/Przidej godki obok nazwy artykułu, tam jest taka sytuacja jak opisałem. To problem rozwiązany, dziękuję za pomoc!
Hey, it's Alex H. I had to reset my phone and even though I had you in WhatsApp somehow you're not there anymore. Can you send me a WhatsApp message when you have a chance? (I will make sure to save you into my contacts this time).
Hi there! You left a message in our community area asking our approval for making Vector 2022 the default skin. After a lot of discussion we agreed. Much internal changes has been done including revamping our Home page. Many thanks for your work on this. Llywelyn2000 (talk) 08:06, 6 April 2023 (UTC)
With the new design please be aware that not everybody wants things stuck to the page or over the contents. I find that very distracting and annoying. I class it as spammy behaviour when they are in the way and can't be closed. I find i can't concentrate on the article. I would like to see an option to hide it like a slider, Google maps have one for the side pane. DuckDucko has a setting and Archive.org has a close button which gives me a choice. I have to rely browser extensions to hide/show these things and they don't always restore properly.
Will there be a setting?
Overall, we:
- Are aware that in such a diverse and tech-savvy group as Wikipedians, there will always be people who dislike a particular feature
- Will build this in MediaWiki which is highly customizable/adjustable anyway. One "only" needs to know how to adjust something. How to change CSS, or to write a user script, etc.
So I suspect the question isn't really "whether this would be possible" but "how easy this would be for individual users". I'll ask my colleagues.
Well I see the new design, appreciate the left slider can be hidden and other stuff and I don't see any fixed headers yet. I appreciate that.
Thank you.
When I see large headers stuck on the top of the page that I find I don't need and don't want them, can't hide whenI am trying to scroll away from them they make me loose my temper and this from the start in 2015 before I used element hiders to hide them and a Bookmark killer before that i manually removed them from developer tools. I am now at the liberty of browser extensions Firefox "Stickyducky" and Chrome, "Sticky Header Hider aka Fixed Header Fixer" Chrome auto hide stuff on scroll and I shouldn't to depend on those.
Hypothetically: If you went into a shop on the high street and everytime you go in there you have something stuck in a fixed part of your vision, with the store's logo, and toolbar in the way and distracting and no matter where you look you can't get rid of it until you leave. Now how would you feel? Wouldn't that put you off?
I like my freedom to scroll the page, whether everything scrolls inline, it makes it to me spacious and this what got my into browsing and doing many things and research back many decades.
Archive.org has a header that can be hidden and Duckduckgo too as i have choice like before the change to adjust it.
.
I find the fixed headers (uncloseable) or things stuck there a violation over my viewing area. I take great offence the same as when I use to remove malware decades ago for customers, like the excessive browser toolbars, that use to reinstall through hidden processes (free games) that customers couldn't see, and injected stuff over webpages with things that interfered whether they'd be watching some on youtube, which included dimming overlays (lightboxes) advertising or scaring them into some unknown anti virus program and through a fake looking mozilla yellow bar on Firefox back in the day.
I read a lot of people in the comments on the development page and the EEVBLOG board that they are unhappy with the the white spaces so on that they saw recently, but I don't care about those, only that my viewing area is left alone on scroll and things are not stuck in the way.
It's a bit like Channel logos, in the UK we have like hundreds of freeview channels and some BBC too but I don't watch any of them for that reason as I'd notice them more than the anything else and can't pay attention due to the distraction of seeing it there all the time constantly over the picture.
Thanks again for listening.
Hi, I translated Reading/Web/Desktop Improvements/Updates/2022-11 for the mid-size wikis/el and I was bold to replace in the translation File:Desktop Improvements - how to enable - greek.png to File:Desktop Improvements - how to enable - greek.png. I have a minor question: what is the checkbox in the left in your screenshot?
Thank you, that was an excellent idea! The checkbox is there because that’s a screenshot of the global preferences. I can add the “global preferences” words as the description to that screenshot. I’d use {{int:}} so you wouldn’t need to translate that manually. What do you think?
Dear Mr. SGrabarczuk!
I'm from the diq.wikipedia. After your change, the language links appear at the top of the page. The old position would actually have been better. Because the connection to the page list on Wikidata is now missing at the end. Kind regards! -- ~~~~
Hello! Thank you for writing to me. The Wikidata link (Unsurê Wikidata) is now in the Haceti section of the sidebar. What do you think of this solution? Greetings.
Thank you for your reply. I have now selected the old version. Because I can usually deal with it better. Kind regards!
Greetings @SGrabarczuk (WMF)
Soon after the new skin Vector 2022 was applied on our wiki a week ago, all templates pages are showing an error "TemplateStyles' src attribute must not be empty."
Before the Vector 2022 skin was applied, all was as usual - smooth and normal, no errors.
Can you help us?
Thank you.
Hello @Tumbuka Arch. Apologies for the late reply. Thanks for letting me know about this problem. Could you share a link to a page where you see this? I'd like to find out if it's related to Vector 2022, or is it a coincidence. We'll try to help. Thank you!
Hi SGrabarczuk,
While using the new skin on Dutch Wiktionary (nl.wiktionary.org) I noticed it changes the name of the project from WikiWoordenboek into Wiktionary. The perceived domination of English is for some a recurring source of criticism on WMF initiatives. I expect the acceptance of a new skin will benefit from showing the correct text as early as possible. As the French Wiktionary is showing Wiktionnaire I suppose this can be done, but I don't know how.
Hello. I understand you, I'm not an English native speaker myself. In this case, it's only because the team hasn't made all the logos for all wikis yet. We will definitely do that before we change the default skin on more wikis.
Thanks for the reply. I guessed this would be solved before making it the default skin. But I would like to generate some enthusiasm for that change and having the correct name show up would be helpful in this stage already. Could we speed things up if I created the adapted logo text myself?
If you think it's possible, we can even make the skin default sooner, and then we'd provide the logo. If you only prefer to make the logo, here's the instruction. It requires some purely technical things I'm not an expert at, so if you have any questions, you'll need to wait until I get answers from my team mates.
Your message in our Village Pump did not say anything about using the correct logo. Changing the name of a project as part of a new skin is clearly unacceptable. When our present logo was designed, the available width put a real constraint on the legibility, and some time was needed to find the optimal solution.
So I strongly suggest you add an adapted logo to the test version before deploying it. If you want to stick to Oct. 3rd for deployment, it would be reasonable for you to show the adapted logo on Sept. 27th and provide for the possibility to make improvements in the period before deployment. If this proves too difficult, I suggest you state the date on which the new logo will be part of the test version and allow for 4 weeks time to react before deploying.
Although I do expect some long-time users preferring the old skin, after using the new skin for 3 months myself I'm quite happy with the improvements. So I hope my first suggestion will be feasible. This is also the reason for this message instead of asking for a later deployment right away.
Hi. Thanks for the message. I'm sorry that in the message, I didn't include information on the logo. You are absolutely right. Of course we will create it before making the change. I've been told that a few of my colleagues would sit down together and have a few-hour session of creating all the logos needed.
Apart from that, I'm happy that you appreciate the new skin. I'll let my team know about your suggestion.
Is there somewhere we can see what the WikiWoordenboek logo is going to look like yet? Or is it safer to request more time to discuss the change? We are in no hurry to change the default skin.
I suspect the logos aren't public yet. Also, since other things are moving, we have more flexibility than we thought. Today, our team decided that next week, we wouldn't make the change for the largest wikis among those which received the message. Dutch Wiktionary is among these wikis. So - we have time! :)
That's great! Is it okay if I mention this extension in our De kroeg (Village Pump) or are you planning a general notification to the wikis concerned?
I just got an email from the Dutch Wikimedia chapter (I'm also moderator of nl.wikimedia.org). They have a similar request as WikiWoordenboek: to view the new version of the logo before the skin becomes the default one. Even though this is a really small wiki, would it be possible to add them to the list of wikis that will be changed later on? I have given them an explanation why I think the new skin is an improvement, and I don't think they have any other objections. If it's better to use the button in your message, I can of course do so.
It's fine, we can have the discussion here. Thank you for being our advocate here! I'll let the team know and get back to you.
Hello, SGrabarczuk.
Recently you posted a message on the general discussion page (fy:) of the Western Frisian Wikipedia (fywiki) about the new Vector 2022 skin becoming the default there in the week of October 3rd. I pinged you last Saturday to ask a question about that, but I'm starting to think you didn't get the message. So I'll ask again here.
I tried the new skin out and I'm not a fan. I see some advantages but a lot more disadvantages. So here's my question: you say we can get more time to discuss the changes, but is there an actual choice here between "Yes, let's do it" en "No, this is not for us so we're going to opt out and keep the old skin on our Wikipedia"? Because if we can't refuse the new skin, then there really is no sense in discussing things, is there? ~~~~
Hello! Thanks for writing to me here. Indeed, somehow, I didn't get the ping, so your message here helped. I'll answer on fywiki and we'll have the discussion there, ok?
:ja:利用者:SGrabarczuk (WMF)の案内に従って:ja:利用者‐会話:SGrabarczuk (WMF)に要望を書きましたが、どうも読んでおられないようなのでこちらに書きます。あなたは:ja:Wikipedia:井戸端 をお読みでしょうか。Vecor (2022)については表示の問題が発生していてIPユーザーから苦情が寄せられています。あなたはこの問題はVector (2022)の技術的問題ではなく他の個所の問題だとお考えなのかもしれませんが、開発者チームの中の役割分担がどのようになっているかは、一般の利用者には関係ありません。あなたの権限でとりあえずデフォールトのスキンを元のVector (2010)に戻すことはできるはずなので戻してください。その権限がないのなら、何らかの改善提案を:ja:Wikipedia:井戸端 にお書きください。なお、その際はGOOGLE翻訳による日本語訳をお付けください。DEEPLは権利問題が発生するので使わないでください。-: ja: User: Follow the guidance of SGrabarczuk (WMF): ja: User-Conversation: I wrote a request to SGrabarczuk (WMF), but I can't seem to read it, so I will write it here. Have you read: ja: Wikipedia: Well Edge? IP users have complained about Vecor (2022) due to display issues. You might think that this issue isn't a technical issue in Vector (2022), but something else, but what the division of roles within the developer team is is for general use. It doesn't matter who you are. You should be able to revert the default skin to the original Vector (2010) for the time being with your privileges, so please do so. If you don't have that authority, please write any suggestions for improvement at: ja: Wikipedia: Idobata. In that case, please attach a Japanese translation by GOOGLE translation. Do not use DEEPL as it will cause rights issues. --~~~~-~~~~
ihave seen all what you wrote and I appreciate~~~~