Mon, Mar 11
Sun, Mar 10
Sorry, I thought I had closed this. It turned out to be a browser issue with Chrome – IIRC, the thing I needed to do to fix this (on my machine) was to enable "GPU rasterization" on chrome://flags, and everything went back to normal. So it wasn't actually a Wikimedia-specific problem at all.
Feb 16 2019
Probably because of the gadget "maintenance-menu" having it as a
dependency. I'm on mobile so it's difficult to link it, but you can see it
Jan 11 2019
But this Herald rule doesn't affect Norwegian users. It only affects what Jeblad subscribes to. If he doesn't want to be subscribed to tasks about <nowiki>, then he knows what and how to change it. I still fail to see why this would be an issue for you.
I don't see why this would be a problem for anyone other than Jeblad…? Why is this an issue for you, Liuxinyu?
Jan 9 2019
Oh ok, that's good!
Looking at the en.json file, I think it would be necessary to flatten it. So instead of a nested structure like you have, the strings should all be at the same level.
Jan 2 2019
The edit right is assigned to the group "Users", which means that nothing has really changed (since only that group could read and edit before this change). All the patch did in reality, then, was to put a strike through internal in Special:SiteMatrix …
What does "close" mean in this context? I was able to make an edit there just now.
Dec 7 2018
Dec 2 2018
The index and page namespaces are defined in the Proofread Page extension, for which I just submitted a patch above. In addition to this, you can localize the names of the following special pages:
Dec 1 2018
Nov 14 2018
Nov 8 2018
Hmm, I just checked in Firefox and the problem is not there. That led me to believe it was a browser issue, and it turned out it had something to do with GPU rasterization in Chrome. Enabling that solved the issue. So it is apparently not a Wikimedia problem after all.
I just came across another example of this: The Wikinews logo. Here as well it is more noticeable in small sizes, see e.g. where the logo is used on this page. It seems like there is a sort of green glow around the sides that shouldn't be there.
Nov 5 2018
Oct 26 2018
Nope, all good. Thanks for the reminder!
Oct 2 2018
Oct 1 2018
Sep 27 2018
Sep 10 2018
Sep 8 2018
Sep 7 2018
Sep 4 2018
Well yes, I know what "test" means. But what the hell is a squasher in this context?
Thanks @Jonas et al. Community consensus is already there, see https://wikisource.org/wiki/Wikisource:Scriptorium#Enable_arbitrary_Wikidata_access_for_oldwikisource .
Sep 1 2018
This may be the case for more languages in that list. Do you have time to look into that and amend this task to reflect that if necessary?
Aug 27 2018
List of languages with valid language codes and at least some content in oldwikisource:
Since the translate extension was enabled (T201814), which includes this feature by default, I believe this can be closed. I don't think setting the default page language to mul is possible without changing the wiki language itself, and that would probably have really bad side-effects, so it's probably better to keep it at English. But please feel free to reopen (and possibly change the task description/title) if I'm wrong.
One thing that needs to be figured out is how to add languages to language-data where we don't know the native name of the language. Right now, the design of language-data makes that a requirement to be added, but there are many languages that could (and should) be supported in e.g. Wikidata and mul.Wikisource where we don't have that, making it impossible to add them properly.
Aug 25 2018
Looked some more into it, and it seems that the list of languages you can choose corresponds directly to the list of languages in Names.php.
Well, changing page language is part of the Translate extension, so I think someone from Language-Team could tell us that. I'm not sure if changing it in language-data is enough – I added a few languages there six months ago, but those are still not available to choose as page languages, so there must be something more to do. Maybe @Nikerabbit or @Amire80 could shed some light on the matter?
Aug 23 2018
Also made a pull request in wikimedia/language-data on GitHub.
Aug 22 2018
(Sorry about my confusion up there, when marking this as a duplicate I got an error message which led me to think action wasn't performed, while it turned out it actually was.)
Aug 21 2018
Aug 14 2018
Aug 13 2018
All done now, please have a look @Baloch007 !
Thanks @zeljkofilipin , all seems to be in order!
Aug 9 2018
Shouldn't the logo be on the right side of the text, since Pashto is a right-to-left language?
Aug 8 2018
I actually totally agree with that. The system needs a rethinking and reworking, so we should start a task for that instead (if there isn't one already?).
I am sceptical of this one, as Zapotec is a language group, not an individual language. I'm therefore inclined to reject this.
@Baloch007: As you can see, the change was merged, so it should start working some time after the 14th of August. Note that since the Saraiki Wikipedia is still in the Incubator, I'm not sure it will work properly in articles there or not. However, in the user interface it should be working (after that date), and when the Wikipedia is eventually created it will work in articles as well. But please let me know if you notice any problems.
Some suggestions for possible groupings:
Aug 7 2018
It would be ideal if Special:MyLanguage for anonymous users would follow the browser settings of the user in my opinion. Not sure how easy that is, though.
I have posted about this in the Albanian Wikipedia village pump now, so unless there are objections I think the change can be made in one week. The other Albanian-language projects have such low activity that I don't see the point in even posting there, I think there the change can just be made.
Sure, will take a closer look when I get home from work today.
Jul 24 2018
Jun 8 2018
May 28 2018
Probably upstream when I think about it.
Apr 5 2018
Alright, the import is finished, so I'm closing the task. Some work remains to be done, but I think that's better done and coordinated on the Basque Wikipedia itself as it shouldn't require any developer attention/coding/etc. (Perhaps except this linking issue – but that should probably be a different task in case code is needed, instead of being part of this task itself.)
We did! :-)
I have already fixed all of this when preparing the import. 😊
- I've already prepared the import, and I think it's ready to go, but I need importer rights. That's not something local bureaucrats can give, it needs to go via [[m:Steward requests/Permissions]], but for that we need some community consensus for that. Where should I go to request that?
- The tab code is working, we just need to translate the line with "tooltip-ca-nstab-txikipedia" into Basque. When done you can move that page to [[MediaWiki:Gadget-TxikipediaTab.js]], and put the necessary CSS for the tab in [[MediaWiki:Gadget-TxikipediaTab.css]]. Then create [[MediaWiki:Gadget-TxikipediaTab]] with a description of what the script does, and add the following line to [[MediaWiki:Gadgets-definition]]:
- That's easy to add by bot once the import is done.
Apr 4 2018
Alright, done! It worked this time. :-)
Thanks for looking into it too, @Urbanecm!