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.

In T189459#4109101, @Theklan wrote:

That could be interesting. Another solution, but maybe more difficult, is that links INSIDE Txikipedia namespace always point to Txikipedia if w: is not added.

We did! :-)

I have already fixed all of this when preparing the import. 😊

1. 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?
2. 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]]:
   1. TxikipediaTab[ResourceLoader|default|dependencies=site,mediawiki.api,mediawiki.util|type=general]|TxikipediaTab.js|TxikipediaTab.css
3. That's easy to add by bot once the import is done.

Alright, done! It worked this time. :-)

Thanks for looking into it too, @Urbanecm!

Sorry, I meant to comment sooner but I got preoccupied.

Just 104 and 105, the next unused numbers for the Basque Wikipedia in wgExtraNamespaces.

Alright, patch is ready and I added it to the upcoming SWAT, so it should be done in a couple of hours.

I don't think a separate tab for the Txikipedia talk would be necessary, one could just use the normal talk page for that, don't you think? If you want a separate tab for it that's relatively simple to achieve, but I think it would look a bit messy.

Just to confirm, the talk namespace should be "Txikipedia eztabaida", correct? The talk namespace won't get any links, so probably very minimal use, but it needs to be there nonetheless – I fear it will complicate things a lot if it isn't.

Ah, never mind me, I confused featured lists and good lists, they're two different levels in eswiki and ptwiki. Then indeed, that should be made available in Wikidata.

This has already been an option for a long time, practically since those marks were introduced. See this edit.

The end result would be pretty much the same, but an extension would be preferable since adding the tab(s) is done server-side instead of client-side by a javascript. However, it seems that extension is in need of a maintainer, which I wish I could do, but I don't have the know-how. Until that happens, the JavaScript can be used and if the extension gets revitalized and approved then you could switch to it, that would be simple once the extension is approved/set up.

Alright, I finished the script, you can test it by adding importScript( 'Lankide:Jon Harald Søby/VikidiaTab.js' ); to your common.js. It substitutes the wikiproject namespace for Vikidia, since the Vikidia namespace doesn't exist yet. You can test it on a page like Arkitektura or any other article to see that it works.

Yeah, to create a namespace you need to file a task here (preferrably when the discussion is finished). You also need to figure what should be imported – Vikidia naturally has several namespaces, but with this solution I think only the main namespace content should go into the new namespace, so you need to figure out what should be done with the other content. Looking at the stats, there are only four talk pages, some user & user talk pages (probably shouldn't be imported), a few images (all without any licensing info; should probably try to find from Commons instead, so not import), around 150 templates (many of which seem to be copied from Wikipedia, and therefore probably identical to existing ones), and just a small handful of pages in other namespaces. All in all I'll say it's very doable, and I'd be happy to help you with the import itself, since I have done similar things a couple of times for Incubator wikis to Wikipedias, so I know what steps to take.

It doesn't create namespace 114, but points the tab link to a page in that namespace (which happens to be 114 in this case) with the same pagename. So yes, if you use this system the pages from Vikidia should be imported so that the pages from Vikidia's main namespace go into a new namespace (probably called Vikidia), and the script needs to be adapted to point to that namespace. One question is if you want there to be a (red) link to Vikidia on every page that doesn't have one, or if it should be restricted to only the pages that have a Vikidia page – I can imagine quite a few articles that shouldn't necessarily have a "kid's version". There are multiple possible solutions – only showing the links when a Vikidia page exists; implementing a template like {{NOVIKIDIALINK}} with some code that trigger the tab not to be shown; etc.

It's happening because TemplateStyles isn't enabled yet on sewikimedia, while it is on svwiki. This should only affect the documentation template, so the button template itself should work as it should. 😊

Did you check the box to import included templates as well? If so, try unchecking it.

@Tpt Any plans to add this to a SWAT?

BTW, header tabs is not the right extension for this. To see it in practice, see e.g. this page.

On the English Wiktionary they achieve this for the "Citations" namespace using a gadget called "DocTabs" (js, css).

Maybe related to T54180?

In T188776#4021634, @Varnent wrote:

In T188776#4021611, @Bawolff wrote:

That said, I would certainly prefer it wasnt a raw html wiki. At first glance it sounds like this move will elliminate most of the need for raw html and also provide a good excuse to disable raw html.

There is nothing currently planned for this wiki after the launch of the new site that would require it to maintain support for raw html.

There have been some discussions on the eligibility of cnr for a Wikipedia (the consensus in the committee seems to be "no"), but I don't see why that should incluence including the code in Wikidata, so I'll say yes.

That's it, this is finally resolved. Thanks @thcipriani and others!

Yay! @BukhariSaeed et al, let us know if everything looks good and we didn't make any typos/errors in the namespace names!

In T186393#3992524, @jhsoby wrote:

I've made some edits to the patch now. It was almost correct, @Zoranzoki21, the only thing was that the spaces needed to be changed for underscores.

@BukhariSaeed The patch doesn't contain the namespaces "Summary" and "Thread". What is the purpose of those namespaces, what do you intend to use them for if I may ask? I'm especially wondering if the "Thread" one is the translation of the Topic namespace from the Flow extension, or if it is something different related to Wiktionary.

@Jogi_don Like I said, please read my previous comment (T186943#3992652) that explains that this is waiting to be merged. You just need to have a bit of patience.

@Jogi_don … please read my previous comment.

In T186943#3992610, @mehtab.ahmed wrote:

NS_WIKIPEDIA => 'وڪيپيڊيا',
NS_WIKIPEDIA_TALK => 'وڪيپيڊيا_بحث',
NS_PORTAL => 'باب',
NS_PORTAL_TALK => 'باب_بحث',
These things have got changed. However, we are still waiting for other namespaces.

I've made some edits to the patch now. It was almost correct, @Zoranzoki21, the only thing was that the spaces needed to be changed for underscores.

In T186393#3992298, @BukhariSaeed wrote:

@Zoranzoki21 If you know that you do not able to handle this task so why you interfere?

Adding the tag Wikimedia-maintenance-script-run because I believe the script needs to be run for all four patches. @MarcoAurelio, maybe you have some insight there?

Alright, patch added as you can see. Please check it to see if I made any errors (the Wikipedia, portal and gadget namespaces were changed in other commits further up this thread).

@BukhariSaeed No problem! BTW, did you want to change one of the template namespaces too? Currently NS_TEMPLATE uses "سانچو" while NS_TEMPLATE_TALK uses "سنچو" – the second one is missing the alif.

@mehtab.ahmed and @BukhariSaeed Thank you very much, will submit a patch shortly.

In T186943#3983456, @mehtab.ahmed wrote:

@jhsoby just to tell you that
https://translatewiki.net/wiki/MediaWiki:Nstab-user/sd has been translated months ago.

@mehtab.ahmed Changes in TranslateWiki usually take a day or two before they go live on Wikipedia, but it will happen very soon.

@mehtab.ahmed Okay, thanks! That is not a namespace name, that is a normal MediaWiki message which can be translated here: https://translatewiki.net/wiki/MediaWiki:Nstab-user/sd (but I suggest waiting to do that until the namespace name has been changed).

Alright, I've made several patches now as you can see, but I'm struggling to understand what you mean with these, @BukhariSaeed:

The patch I uploaded just fixes the meta namespace (Wikipedia), the rest of the namespaces are localized somewhere else – trying to figure out where.

Hehe, you beat me to that last part by 1 minute!

What should the attached talk namespace (and alias) be named?

Just wondering, why do you need to rename it at all? You could call it "aoushndaousnh" and it wouldn't matter, normal users will only ever see the name you use for it in MediaWiki:Gadget-DeluxeHistory. That can be changed without renaming the gadget messages.

Deployed, seems to be working well. Let me know if there are any problems, @Reptilien.19831209BE1!

I've added it to the SWAT window for Monday.

In addition to looking into MassMessage integration, I think it would also be worth looking into integrating it with Notifications (Echo). That was actually something I wanted when the extension was made, the problem was just that Echo didn't exist yet. :-) Right now I think the threshold for sending out a notification is very high since it's posted to many user talk pages, but being able to send out notifications via Echo should lower that threshold significantly I think.

Fixed, after enabling one needs to create the template and module named "AboutTopic". I just copied the ones from sewiki, and it's working well now.

@MarcoAurelio What do you think, can this be deployed? Wrt. my comment above.

Many wikis use Yair rand's WikidataInfo.js as a gadget, it's worth taking a look at that.

How did you encounter this warning? How can one reproduce?

If you find stuff like this in the future, you should ask somewhere like Wikipedia:Technik/Werkstatt or Wikidata:Forum, since this is not actually a bug/software problem. :-)

@tstarling Thank you very much for looking into this! It's much appreciated.

@MarcoAurelio, when we did that (rename namespace) for the Walloon Wiktionary all we needed to do was change config and then run namespaceDupes. However, since cawikimedia doesn't have any pages in the "Project" namespace or any pages in the main namespace with the prefix "Wikimedia:", I'm not even sure you'd have to run that script. Should still do it just to be safe though.

Oh no, I didn't know that about Purodha. Very sad, and a big loss for Wikimedia. :-(

Added pull request.

In T133766#2268213, @MusikAnimal wrote:

Should be all set! Feel free to use {{PLURAL}} and {{GENDER}} for any messages that have parameters. I didn't add support for other less common magic words, but if something isn't working for you just let me know I can probably fix it.

@Reptilien.19831209BE1 I am correct in assuming the talk namespaces should just be "X copene", correct?

@Urbanecm I don't mind taking this one.

Hmmm, it seems to bo working now, so it must have been a temporary fluke I guess. All good now.

1. On any item, click add new property
2. Type in "family name" (or the equivalent in your language)
3. Type in "Jünge" or "Ekaas" – no results
4. Alternatively, type in the Qids Q47454217 or Q47454218 – no results

@jeblad Hmm that's weird, the first one still doesn't work for me even with Qid. (Are you sure you're seeing "Jünge" and not "Junge"?)