Where can I find the discussion that led to the decision to reverse the use of "night" over "dark" explained in phab:T351307#9353379, which was linked in Reading/Web/Accessibility for reading/Frequently asked questions?
SGrabarczuk (WMF)
Joined 6 March 2017
This was directly in result of this user testing. Specifically:
Color, and the Color label
Most participants felt it met their expectations to some extent.
1 seemed unsure about what the ‘automatic’ setting was based upon.
5 participants felt ‘color’ was confusing in some way, and suggested changing to ‘day/night mode’ (2), ‘screen color’ (2), ‘dark/bright mode’ (1), and ‘background color’ (1). 1 mentioned that changing would make it “how it is in … normal phone settings”.
Hi SGrabarczuk, you wrote "Accessibility for Reading (Vector 2022) is already translated as Accessibility for Reading (Vector 2022). Consider this translation for consistency." with this edit. Could you please point me out where I may find this translation? Thanks, ~~~~
Hey! The translation is here: https://translatewiki.net/wiki/MediaWiki:Vector-2022-beta-preview-label/nl
If you decide to translate this page, the update will be visible on wikis early next week because the translations are pulled from translatewiki once a week.
To edit translatewiki, you need to have an account there, and if you haven't edited translatewiki before, you'll need to create a new account with its own password.
Thanks, I will use that term. There seems no need to translate on that Wiki.
I will repost you the same letter I wrote Olga Vasileva
"Hi. First of all excuse me if this isn't the right channel to talk to the team. I am an admin at Spanish Wikisource and have a big concern about this skin, but couldn't find anywhere else to express it. I personally love Vector 2022 and would very much like to continue using it!
My issue is that interproject (e.g. English Wikipedia to English Wikisource) links are not visible anymore! This affects profoundly to the reach of sister projects.
With the old vector, interproject links had the same salience as interlanguage links. They both were in the same column. Now, interlanguage links have their own shiny button, but interproject links are buried in the "Tools" menu (collapsable out of view).
The "Tools" menu is for editors, 1% of people that interact with the page. Interproject links are primarily for users. There is some redundant linking, though: In some Wikipedias, interproject links are down in the "Authority Control" table (a visual mess) inside the "External links" tab (collapsable out of view).
Maybe interproject links should have their own shiny button. Regards,"
Is it possible to talk to someone on this team?
I made a comment on the project's talk page six months ago, and I see it was archived without any answer (https://www.mediawiki.org/w/index.php?title=Talk%3AReading%2FWeb%2FDesktop_Improvements&oldid=prev&diff=6106839).
Oh, I'm really sorry! In principle, we try to respond, and this shouldn't have happened.
The answer to your question is not easy, and perhaps that's why you didn't get it instantly. I will ask the team to address it this time. And yes, you've pinged the right people - me and Olga.
Hi, I wish you happy holidays and a happy new year, may it be full of beautiful wiki things!
Grazie, @Patafisik! (I'm replying late because I'm just back from the holidays.) Felice anno nuovo, and see you around!
@SGrabarczuk (WMF): just a gentle nudge. A weak objection is present at Water hole on Wikivoyage/ja.
Have a look at under the section title: "The Vector 2022 skin as the default in three weeks?（情報周知）". The poster is the admin. Cheers,
Thank you so much for letting me know! Today, I'll have a look at more Japanese sister project discussion pages.
In regards to your ping: first thing first, and is there any clever way to localize those images which should be instructive or intuitive to grasp what you are talking about? I have always wondered how we could hook up users’ interest to tech subject, and, aha, images! Sadly, our best educational asset to be, the images stands out in the translated page: they are foreign, not only conveying new ideas, but alienated as they are presented in non-local language. Mind you, visual aspects catches your attraction faster and, it lingers in your mind if you are shared the delicious idea or also alienated. We need to change how we present new ideas, esp if we are eager to gain feedback from those reading our pleas.
Katakana transcription is a trap that will alienate the readers, as well. We would be better off by treating each other as peers on the same planet, not like green monsters extraterrestrial, don’t we? (;
Now. Allow me and I have added plain language explanation to the term typography at the end of the paragraph.
Oops, and as translation goes with the original writer, we are not supporting the idea to add (NB: bla bla) kind of addendum.
Kindly add short phrases to techy terms, depending on how far we wish to reach out: only admins who need no such pampering, or -500 edit count fresh minds without much superstitious wisdom they have gained or been forced to swallow. Cheers,
Hello, thanks for the messages! I'd like to address everything, but since I'm unsure about some of your points, I'm going to ask you a few questions instead. So:
Yes, I can upload the Japanese version of the prototype, that's a very good idea! I need to have the translations ready first, though.
Thank you for your plain language tweaks!
I'm not sure what you mean in the part about the Katakana transcription, and in the second message about not supporting addenda.
Where do you think I should add short phrases to techy terms?
This message is made for the village pumps and all Wikipedians, and the banner will be shown to all logged-in users, regardless of the experience in the wiki world.
I'd better start as: I am among them who expands wikis to 130% on FireFox. So thrilled that dark mode as well as typography could be adjusted to each users' preference and needs, yey. (;
I have this web page in mind translating the test notice. Sorry you need a translation tool to help you, and do you think that in general it conveys what this testing covers?
For the second part or addendum: we translators are not advised to add parentheses and translators' note as I did at Community_prototype_testing/ja: タイポグラフィ（字組み）. But as far as jawp has an article about it, users will be confined to what jawp tells them, a small picture. IMHO your team is targeting more advanced state than that, am I right?
So, the addendum needs to explain at least those three points we show users in the image. https://upload.wikimedia.org/wikipedia/commons/5/5b/Accessibility_for_reading_prototype_1_widget.png
png and en-ja translation.
- Font size: 文字の大きさ
- Line height(†): 行と行の間隔
- Paragraph spacing(‡): 段落と段落の間隔
Like line height(†). It is a bit tricky to those who are not familiar with paper publication, or a web native seldom needs to think about it, like writing on wikis including Diff, WordPress or posting on x or any such. Even those who grew up on Win98 are not expecting line height to webpages, while they know how to handle it on Windows Word/Google Doc.
Paragraph spacing (‡): I am curious to know what users will react to. I guess if we don't allow adjusting line height, and allow paragraph spacing, users will get used to it as on Google Doc. As I've come from paper printing media, this is nonsense basically, if you allow users to adjust line height. Ja language uses on non-wiki sites simply divide paragraphs by adding extra margin to the first line in the new paragraph, or indent the first line a width of a Chinese character. That is much easier to scan a page, as that dent catches your eyes.
Technically, I sometimes find newbies are hen-pecked to write in that style of paper media indents-paragraphs. While elementary school education has been supplying PCs and notepads to classrooms after 2015, and to schoolkids (not 1-1 ratio yet) after COVID-19 outbreak in Japan. So are we going to include digital natives as our main editors/contributors, and starting when?
Oh, okay, thank you for clarifying all that.
Fist of all, perhaps translators aren't encouraged to be creative, but I wanted to emphasize that I always welcome any tweaks, addenda, anything you think will sound better, clearer, etc. for Japanese speakers. I trust you! In particular, this applies to translations of messages that are to be sent to wikis, like this one, but it's also fine if you improve pages like this one.
Regarding the website about the automated kerning, tackling this is not part of our basic plan, but we may end up working on it after a discussion with your community.
I'll share the link to this conversation with our designer, Justin - your last three paragraphs may be interesting for him!
Please see Talk:Reading/Web/Accessibility for reading#How do I close the "Wikimedia reading tool" window?
Hello, how to add interwiki in new articles, for example there: https://szl.wikipedia.org/wiki/Aktywacyjno_funkcyjo?
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)