Incubator:Import requests

Archives

---

See /Archive

Requests for importing of closed projects belong to the page Incubator:Coordination for importing closed projects‎.

Here you can request importing pages with the full history from another Wikipedia/Wiktionary etc. to translate them into your test language.

Imports from the following wikis can be done by every administrator:

• Meta-Wiki
• Wikimedia Commons
• English Wikipedia
• German Wikipedia
• French Wikipedia
• Spanish Wikipedia
• Portuguese Wikipedia
• Dutch Wikipedia
• Russian Wikipedia
• English Wiktionary
• English Wikibooks

From other wikis only import users can import.

A log of import actions is at Special:Log/import.

Requests here

Example: Please import en:Example to Wp/de/Beispiel. ~~~~

Wy/ja

Please import Wikitravel data dump. This is the database dump / back up of Wikitravel in all languages, including Japanese. Download here. The file is compressed using 7zip.--Other languages (talk) 09:53, 11 July 2020 (UTC)

User:Tmv: what do you think of this request? --MF-W {a, b} 12:22, 12 July 2020 (UTC)

@MF-Warburg: I guess that the problem is that we have no policy on importing. Therefore, we should discuss and create a policy on this subject. We'll keep you updated on the situation. Once the policy is in place, we'll be able to decide what to do.

I will also inform Wikitravel community on the discussion. I have an account there.--Tmv (talk|Contributions) 07:57, 13 July 2020 (UTC)

report - Wy/ja/Wikivoyage:ウィキトラベルからのインポート--Tmv 03:17, 28 July 2020 (UTC)

Hi, I'm the one who created the data dump. If the decision is made to import Wikitravel's content (which I support) I can create an updated version of the backup.

User:Tmv: I read the import policy you wrote and that's not going to work... I can't account for those criteria when importing. My suggestion is to import everything, that's what was done when we imported the other Wikitravel languages. The articles come with the entire history preserved so there won't be any copyright issues. Acer (talk) 00:03, 31 July 2020 (UTC)

@Acer: Thanks for the comments. Let me ask you a question. I'm in favor of importing all the pages, but what about the articles that already exist in Wikivoyage? I'm not familiar with importing from Wikitravel so I don't know. Could you please enlighten me?--Tmv (talk|Contributions) 23:33, 31 July 2020 (UTC)

@User:MF-Warburg What's the plan here? Import directly to ja.wikivoyage? Or to the incubator? Is this going to get fast tracked like the original imports?

@User:Tmv Let's see what MF-Warbug says. If we can import directly to ja.wikivoyage then we could just import everything there and after that you can replace Wikitravel pages with the ones here from the Incubator very easily if you want. It's not a problem Acer (talk) 15:31, 1 August 2020 (UTC)

How many pages would this be? Also, do you really want to import pages from 2016? --MF-W {a, b} 16:50, 1 August 2020 (UTC)

5810 articles (18272 total pages). And no, not from 2016. Japanese Wikitravel is still active, I can generate a new, up-to-date, datadump. Acer (talk) 19:51, 1 August 2020 (UTC)

I am active in Wy/ja. If we can get a new data-dump that reflects the pages in the present Wikitravel, we should do that, I think. The data dump in 2016 must have gotten old. --Atmark-chan <^T/_C> 10:17, 2 August 2020 (UTC)

It's outdated in the 2016 dump data. If you import that dump data, it's hard to fix it.So I think you should make sure the dump data is up to date.The revision process is easy and you can use your time for other tasks.-- Object＊tofu (Benutzer / erzählen) 11:31, 2 August 2020 (UTC)

Yes, I will create a new updated data dump (August/2020) Acer (talk)

Let me make the following suggestion. We do not fast-track Wikivoyage versions anymore. However, Wy/ja is sufficiently active to be approved. Importing more than 5000 pages into Incubator, only for them to be exported shortly afterwards again, would make no sense. I have now proposed approving Wy/ja in Langcom, and when the wiki exists, you, the community, can import the articles you want, saving the need for adding prefixes etc. --MF-W {a, b} 15:25, 2 August 2020 (UTC)

Great, thank you. But wouldn't it be better to have the data dump used as the basis for creating the Wiki? It's much easier to add in the Incubator pages afterwards than the other way around, given the size differences. Remember how we did it for Finnish Wikivoyage? (and here) Acer (talk) 16:16, 2 August 2020 (UTC)

But the community here is working on their own pages. That should be the basis. Wikitravel forking is second. --MF-W {a, b} 20:18, 2 August 2020 (UTC)

Sorry.I don't know Langcom.What is it?-- Object＊tofu (Benutzer / erzählen) 10:56, 3 August 2020 (UTC)

@Object＊tofu see meta:Language committee--Tmv 01:18, 4 August 2020 (UTC)

Comment The work necessary for Wikivoyage to become independent is not finished. We are not in a position to become independent any time soon. --Tmv 01:26, 4 August 2020 (UTC)

What does that mean? What are you still planning to do? --MF-W {a, b} 01:42, 4 August 2020 (UTC)

I will continue to work on it. But it will take some time to prepare the page import. Because the translation is not finished in translatewiki. It's difficult to finish it quickly because of the volume. If you can wait for me, I will finish it, but I still need time. --Tmv 02:06, 4 August 2020 (UTC)

see [1]--Tmv 02:13, 4 August 2020 (UTC)

If you first want to completely translate the interface, that's fine of course. But for Langcom, it would be ok to already approve the project as it is. I mean, jawiki or jawiktionary are also functioning without a completely translated interface. --MF-W {a, b} 02:29, 4 August 2020 (UTC)

Comment Let me ask a question. The contents of the technical messages that should be translated to Japanese are common among the all Japanese language projects? If they are, probably we don't need to translate the all contents because "jawiki or jawiktionary are also functioning without a completely translated interface," like MF-Warburg said. --Atmark-chan <^T/_C> 10:21, 4 August 2020 (UTC)

Comment It's true that translation work is not mandatory. I don't know if the message is the same for all sites. But if translation is not mandatory, I am very much in favor of independence. --Tmv (talk|Contributions) 11:06, 4 August 2020 (UTC)

Strong Support I want independence from Incubator very much, too, if we can. --Atmark-chan <^T/_C> 11:41, 4 August 2020 (UTC)

I'm all for independence, but the site icon is still an old one. --Tmv (talk|Contributions) 07:12, 5 August 2020 (UTC)

Comment Isn't it OK to use the English logo instead temporarily? I want to use new Japanese logo if we can, but if we can't, the English logo is better than the old Japanese logo. English logo is also used in RUWY. If we create new Japanese logo after independence, reflection of the new logo may take time and effort, but it's better than we can't independent until creation of the new logo. --Atmark-chan <^T/_C> 11:07, 5 August 2020 (UTC)

P.S. I have tried to create a new Japanese logo, but I don't finish it now. We have discussed about it here. --Atmark-chan <^T/_C> 11:13, 5 August 2020 (UTC)

Comment MF-Warburg made a suggestion on approval at Langcom; you have objections to that based on the language proposal policy, please tell us here on this page in the next seven days.

But I think so the policy needs to be adjusted before Independence...-- Object＊tofu (Benutzer / erzählen) 11:50, 5 August 2020 (UTC)

For the record, that is here. But I also read everything here. --MF-W {a, b} 12:34, 5 August 2020 (UTC)

We've worked hard to create a policy so far. I'm concerned about the lack of content on the page explaining how to edit it, but I think it's okay. I'm all for independence; the meta page was edited by me: meta:Special:Diff/20342060--Tmv (talk|Contributions) 22:05, 5 August 2020 (UTC)

Question I have some question. First, will legal documents, for example, documents about license, in the new wiki be created by the foundation? Second, where can we request alias of the namespaces? --Atmark-chan <^T/_C> 18:08, 6 August 2020 (UTC)

No. - At m:Requests_for_new_languages/Wikivoyage_Japanese, currently. --MF-W {a, b} 11:17, 12 August 2020 (UTC)

As the discussion died down, I will mark this as Not done for now. --MF-W {a, b} 11:49, 28 March 2022 (UTC)

Wikitravel datadump

@User:Tmv @User:Atmark-chan @User:Object＊tofu @User:GZWDer

The updated datadump is ready.

@User:MF-Warburg Your plan to let the community import by themselves after Ja/Wy has been created is not going to work. The dump is too big. There are 9814 mainspace articles. Special:Import is limited to batches of 100 pages at most. This needs to be done by someone with shell access using importDump.php. Then there's over 4000 images that need to be uploaded to Commons. This is going to be an involved process. If we don't import the dump at creation-time it's going to be nightmare to do it later... Assuming that's even feasible. Acer (talk) 05:51, 14 August 2020 (UTC)

@Acer: Thanks, we have an agreement on importing on Wikitravel as well. see [2]--Tmv (talk|Contributions) 07:06, 14 August 2020 (UTC)

I don't think this is a good idea. The wiki is going to be created based on the Incubator activity, and with the Incubator pages. We are not creating the wiki primarily as a fork of Wikitravel, though their pages can be integrated. In order to not to get confused between two large import processes, I would prefer if first the import from Incubator gets done. That was the initial reason why I proposed to first get the project to its own wiki, and then to see about what can be done to integrate the Wikitravel content.

Then afterwards, other pages can be imported, according to what the community actually wants. That can surely also be done in a separate phabricator task for a server-side import later on. For example, surely there will be duplicates in articles, but also categories and templates, between the dump and the test-project. They can't just be overwritten, the community should decide what it wants to do in these cases. --MF-W {a, b} 08:20, 14 August 2020 (UTC)

Is it possible to import the dump first and then the Wikivoyage articles, avoiding overwritings by renaming the article names? --Tmv (talk|Contributions) 09:48, 14 August 2020 (UTC)

@User:Tmv Yes. I think that would be the best way. @User:MF-Warburg It's not two large imports. It's a big one and a small one. Ja/Wy here on Incubator has 922 pages total (all namespaces). The dump is way bigger. It's much easier to incorporate the few hundred pages here afterwards than the other way around. The XML file by itself is over 3gigs (without images). Its unwieldy and hard to work with, to pick and choose from that is not practical. At all. Acer (talk) 10:43, 14 August 2020 (UTC)

It is also very unwieldy to throw such a large number of pages at the community at once. What's the motivation here? --MF-W {a, b} 11:43, 14 August 2020 (UTC)

My general motivation is to preserve all the work that's been done writing those 9000+ articles from obliteration when Wikitravel inevitably goes under. If you mean why I'm defending a particular way of going about this, it's because I know it works. That's how we imported all the original Wikivoyage projects back in 2012. A backup was made, imported and the projects launched. Then in 2016 we did the same thing again for Finnish Wikivoyage, this time there were also Incubator pages. We imported the backup, launched the site, then added the Incubator pages afterwards. You say it's unwieldy to throw so many pages at a new project but once its up and running its very easy to delete/archive anything that is unwanted. Whats very hard to do is to work with large XML files offline. I had to cut it up in chunks just to do some basic editing. No one is going to comb trough a huge file like that to pick and choose what to import or not. But none of this really matters, its up to the community to decide what to do and I believe they've spoken in favor of importing. Acer (talk) 22:14, 14 August 2020 (UTC)

I'm going to ask the Japanese community for their opinion. --Tmv (talk|Contributions) 01:33, 15 August 2020 (UTC)

@Acer Sorry, we also made a page like Help:Wy/ja/目次. Were those counted on page 992 as well? --Tmv (talk|Contributions) 21:04, 14 August 2020 (UTC)

Yes, those are counted. See here. These are the page numbers by namespace:

Ja/Wy Incubator

Namespace	Number
Mainspace	321
Talk	43
Mediawiki	1
Mediawiki talk	2
Template	287
Template talk	10
Help	18
Help talk	1
Category	173
Category talk	1
Module	64
Module talk	2
Total	922

Acer (talk) 22:14, 14 August 2020 (UTC)

(outdent) Comment Sorry, I cannot agree to importing the all pages (not page-by-page) in mainspace from JAWT.

If we do that, we will have to modify a lot of template tranclusions, upload a lot of files to Commons (and modify names of a lot of files as needed), and so on, with too much time and effort.

In the first place, importing from WT means that not only imformation but also custom comes from WT into WY. In other languages, WT community itself moved to WY so it wasn't a problem that custom of WT came into WY. But JAWY started to grow it own custom already. I fear that the custom of JAWY that has grown for several years may be broken by importing from JAWT.

Letting custom of JAWT come into JAWY makes JAWY something like a archiving site of JAWT; we have little manpower for letting the pages are adjusted to JAWY. Inevitably, page quantity will talk and custom of JAWY must be absorbed to custom of JAWT. To grow a WY that be similar to WT cause that people flow to not JAWY but JAWT; JAWT must be better than a archiving site of JAWT. We should seek and grow good of JAWY itself. To be able to grow up freely is a good point of new project. --Atmark-chan <^T/_C> 17:16, 15 August 2020 (UTC)

As the discussion died down, I will mark this as Not done for now. --MF-W {a, b} 11:49, 28 March 2022 (UTC)

Wp/sro

Please import the page sc:Mogoresu ([3]) from sc:wikipedia to the wiki project in Campadinese (Wp/sro). Grazie--Fausta Samaritani (talk) 10:59, 30 March 2022 (UTC)

Done: Wp/sro/Mogoresu. --MF-W {a, b} 23:30, 30 March 2022 (UTC)

Please import the page sc:Casteddu/campidanesu ([4]) from sc:wikipedia to the wiki project in Campadinese (Wp/sro). Grazie--Fausta Samaritani (talk) 07:38, 4 April 2022 (UTC)

Wp/sat/wq

Please import Santali Wikiquote on mainspace. ᱵᱤᱨᱢᱚᱞ (talk) 05:50, 15 September 2022 (UTC)

Please be more precise. --MF-W {a, b} 17:20, 15 September 2022 (UTC)

Hello, @ᱵᱤᱨᱢᱚᱞ I guess you want to contribute to Wikiquote for Santali language, which is still in incubator. I have already created a Wikiquote page here.Santali Wikiquote It is start of Santali wikiquote, feel free to add as much quotes as possible under authors name. Rocky 734 (talk) 12:06, 16 September 2022 (UTC)

Santali Wikiquote Main page (Incubator) Go here Rocky 734 (talk) 12:10, 16 September 2022 (UTC)

Wp/isv

Greetings! I would appreciate it someone would be so kind to import the following datadump from Medžuviki at Miraheze: http://steen.free.fr/Export.rar. Everything is grouped by namespace in XML files of maximally 100 articles/categories/etc. One important note: A number of articles have already been copied manually, and in these cases, it's important that both histories are merged instead of overwriting anything. If this is too much work, I'd like to request the right to do it myself. Thanks in advance! Best regards, IJzeren Jan (talk) 12:41, 29 August 2024 (UTC)

As time is currently an issue to me, I have no objection to temporarily grant you import status, unless anyone else disagrees (maybe User:MF-Warburg has the time?). But please be sure that all pages and links use prefixes (Wp/isv/). So update the xml prior to importing it.

Don't worry about overwriting, in case an import is overwriting an existing page, the newest revision will be the current one.

Also, reading from your request for test-adminship, what is the exact benefit of importing the separate wiki into here? --OWTB (talk) 05:51, 30 August 2024 (UTC)

Good morning to you, Ooswesthoesbes! Well, the answer to your question is quite simple: that wiki has been in existence since 2007 (from Wikia via Orain and Wikinet to Miraheze), and from the beginning, the idea was that, should the language become successful, it would be transformed into a real Wikipedia one day. The reason why I want to import its contents instead of simply copying it, is twofold. First, the article histories tell a lot about the history of the language itself. But more importantly, some people have already started copying content from Medžuviki, and much as I appreciate their good intentions, I believe the original authors should be properly credited for their work (especially since some of them are no longer among us). Since Medžuviki won't be necessary anymore once the operation is done, I intend to close or even delete it, and that's why a simple "Copied from" edit summary won't do. At last, a third reason is that Medžuviki has an elaborate infrastructure for facilitating automatic transliteration between Latin and Cyrilic, and somehow I couldn't manage to make it work in the Incubator. I didn't want to ask people to continue working in the Incubator before everything works the way it should. Does that answer your question? Cheers, IJzeren Jan (talk) 08:17, 30 August 2024 (UTC)

Implementing the automated transliteration is possible if the request is accepted, but implementing that here is not possible.

That is actually also why I don't really understand the move. I understand the reason for importing if you continue here, but I don't understand why you don't just continue on Medzhuviki until the request is accepted on Meta. Then you only have to move everything once, instead of twice. (I believe there is a precedence for that with Lingua Franca Nova.) --OWTB (talk) 13:19, 30 August 2024 (UTC)

Aha, now I understand what you mean! Yes, as a matter of fact, that's precisely what I'd been hoping for. As you can see here, I even asked if the whole Incubator stage couldn't be skipped, because indeed, moving everything from Medžuviki to Incubator and then from Incubator to (hopefully) isv.wikipedia.org would create a tremendous amount of extra work. That's also why I didn't even touch the Incubator for a few months. But since no one responded to my question, and in the meantime people have started writing articles here as well, I suppose there's not much point in waiting for an answer that may take years.

But why do you think implementing automated transliteration is not possible here? I remember having seen examples of it working here, for example here. Cheers, IJzeren Jan (talk) 20:18, 30 August 2024 (UTC)

I don't think creating gadgets that are limited to a testwiki is possible, but I may be wrong (I've never seen such thing happen, but I've only been here for 4 years).

Serbo-Croatian works because it is implemented directly on the MediaWiki software, so if you were to create your selfhosted Wiki using Serbo-Croatian as main language, it'd already come with the transliteration "gadget".

Best regards, Iohanen (Garcez) (talk) 00:08, 31 August 2024 (UTC)

Hmm, if that is the case, then transferring everything to the Incubator might indeed not be a good idea. For Interslavic, automated transliteration is of critical importance. It that can't be done, the move would not only entail a lot of unnecessary work, but also a serious deterioration of it functionality. But on the other hand, don't you think it's worth giving it a try? Theoretically, it should be doable if all calls are made correctly, shouldn't it? Of course, it would be best if LangCom would take a quick decision—I honestly cannot think of any counterindication—but we all know that such a decision might as well take multiple years. Best, IJzeren Jan (talk) 09:18, 31 August 2024 (UTC)

Yes, Iohanen is right that it is code specified, so eventually it can be implemented, but I don't think they are going to do it, unless the new wiki is accepted.

My advice would be that you drop a message at Talk:Langcom to increase visibility. As I said, I believe LFN also skipped the incubator stage, so I don't expect that to be a problem for Interslavic, as both languages belong to the same type of conlang. --OWTB (talk) 12:00, 31 August 2024 (UTC)

Thanks, I'll certainly do that! But in the meantime, could I be granted importer rights for a few days or so? I guess giving it a try won't hurt anybody! :) Cheers, IJzeren Jan (talk) 23:33, 31 August 2024 (UTC)

Ah, I didn't know it was bad that I copied the pages from Medžuviki myself, I only wanted it to be better, sorry. But if it works out to import the entire editing history from Medžuviki to Vikipedija, with all the authors, that would be very good. Władysław Krzywiec (talk) 10:43, 25 September 2024 (UTC)

Don't worry about that. I was a bit worried about that myself, but that was before I realised that editing histories could be merged afterwards as well, and that can be done anytime. It only become problematic when two versions of the same article are being edited in both projects. Cheers,  IJzeren Jan (besěda) 20:37, 25 September 2024 (UTC)

Since IJzeren Jan decided to contact the LangCom directly in the regard of this topic (check here), I'll mark this discussion as Not done for now. Iohanen (Garcez) (talk) 17:05, 4 September 2024 (UTC)

Unfortunately, none of the LangCom members have responded to MF-Warburg's or my post. Please read second mail about the subject. In short: at this point I think we better stay in the Incubator, and I'd really like to at least try to get automated transliteration working. But apart from that, import is not a pressing issue. After all, importing articles and page histories can be done anytime. Cheers, IJzeren Jan (talk) 17:28, 5 September 2024 (UTC)

Getting a LangCom response might take some time, because there were many topics at discussion at the time you sent your message, but it doesn't mean they won't answer it ;). Now, the problem with automated transliteration is that it would need direct implementation in the code of the software, something to be done in the Phabricator, and this could take very long.

Now, what I would actually recommend is that you keep activity on one of the wikis, choosing between the test wiki here or the Miraheze one, since the requirements in the Incubator are 3 active users making contentful (and maintaining) articles in the Wiki, where active means at least 10 edits in the last month.

As for your import rights, I really don't have a say on that since it's not part of my permissions, and then I can't change the state of Not done for now (because, for a fact, it is), unless someone decides to grant or not grant you Importer rights.

Best regards, Iohanen (Garcez) (talk) 19:36, 5 September 2024 (UTC)

You know, what I'd really like to know is WHY automatic transliteration should be impossible. My gut feeling is that if it can be implemented at Miraheze, it can be implemented anywhere else as well, including the Incubator. I mean, if it hasn't been tried before, that doesn't make it impossible, right?

Another thing is that I don't quite understand what the LangCom has to do with importing rights. For now, I think we'll stay on the Incubator, and we'll have a discussion about what to do with the old wiki. And of course, it's always possible to copy things manually and import history afterwards, but a) it is a lot of unnecessary extra work, b) import would demonstrate that activity hasn't just started in August. But okay, none of these things are vital. We'll manage anyway! :) Cheers, IJzeren Jan (talk) 21:57, 5 September 2024 (UTC)

I'll go by topics so you may be able to understand, I think you got some things wrong:

1: About the transliteration: The transliteration tool can't be implemented because otherwise it would apply to the entirety of the Incubator, not only to the Wp/isv prefix, that's why it can't be implemented here. @Jon Harald Søby might have a better answer for this, since he has dealt with gadgets in the past.

2: About the Importer rights: The LangCom has nothing to do with Importer rights, what I meant is that I, as an administrator, cannot (it's impossible) give Importer rights, this type of thing is dealt by a bureaucrat, such as MF-W or Oostweshoesbes. I marked it as not done because you had then sent a message to the LangCom, requesting the isv.miraheze.org to be used instead of the Incubator, which would mean a halt in the discussion here.

Best regards, Iohanen (Garcez) (talk) 00:25, 6 September 2024 (UTC)

I don't have time to answer everything here right now, but I'll answer a quick point about transliteration: If a language converter (transliterator) is added properly to MediaWiki, it would not apply to all languages of the Incubator. It will work automatically in the Incubator, but only for pages that are tagged as being in Interslavic (i.e. they have a Wx/isv/ prefix). You can see that in practice in e.g. Wt/zgh/ⵜⴰⵙⵏⴰ ⵏ ⵓⵙⵏⵓⴱⴳ, where there is a transliterator from the Tifinagh alphabet to the Latin alphabet. Jon Harald Søby (talk) 09:03, 12 September 2024 (UTC)

Yes, indeed. What I mean was if the gadget was implemented locally. But we already solved the transliterator problem ;) Iohanen (Garcez) (talk) 13:13, 13 September 2024 (UTC)

@IJzeren Jan: It might actually be possible to implement a transliterator for Wp/isv. I've tested an older code from isv.miraheze.org and it seems to work just fine. It would be needed to implement it in MediaWiki:Wp/isv/Common.js. The code itself is in User:Iohanen/common.js.

Best regards, Iohanen (Garcez) (talk) 01:09, 6 September 2024 (UTC)

@Iohanen: It's better to consider this as on hold, until we hear from either Langcom or a definite decision by the Miraheze Community to move here without transliteration (for now), as I don't believe prefixed JS/CSS actually works. --OWTB (talk) 05:47, 6 September 2024 (UTC)

@Ooswesthoesbes: Prefixed JS/CSS works as long as I know, check MediaWiki:Wp/hrx/Common.css which applies, for instance, to Wp/hrx/Citrus_×_latifolia (Template:Wp/hrx/Info/Taxonomie), that's why this fix could work, at least as long as they are here.

I do agree on keeping it on hold until we hear from the LangCom or a definite decision, this seems to be an unneeded turmoil Iohanen (Garcez) (talk) 05:54, 6 September 2024 (UTC)

That is interesting. I suggest we try to implement it at Wp/isv and see if it works. --OWTB (talk) 06:06, 6 September 2024 (UTC)

@Iohanen: That's wonderful, thank you for that! This is precisely what I had in mind myself, too, so if we can make it work, then by all means let's try implementing it for Interslavic. There are a few other .js and .css files on Medžuviki, so if necessary, they can be moved here as well. Thanks again! Cheers, IJzeren Jan (talk) 20:31, 6 September 2024 (UTC)

@IJzeren Jan @Ooswesthoesbes The transliterator seems to work just fine, although whenever you use it, it leaves a clone from the original text below the transliterated text, but this shouldn't do any harm. I'll try and see if I can make the most recent code from isv.miraheze.org work ;)
Best regards, Iohanen (Garcez) (talk) 15:36, 7 September 2024 (UTC)

Wow, excellent! Many thanks, Iohanen!! As for the clone (and a few other details), there might be a few other gadgets in MediaWiki space involved here. I'll try and see if I can find them for you. Cheers, IJzeren Jan (talk) 16:27, 7 September 2024 (UTC)

@IJzeren Jan: I've got the most recent transliterator version from isv.miraheze.org (here: User:Iohanen/common.js) working, now it's just waiting until it's updated at MediaWiki:Wp/isv/Common.js ;) Iohanen (Garcez) (talk) 18:19, 7 September 2024 (UTC)

Of course, I'll be waiting patiently. In the meantime, would it be possible to upload this code as well: https://isv.miraheze.org/wiki/MediaWiki:Gadget-alphabet.js? I don't really understand how these two transliteration programs communicate with each other and other parts of the software, but this one contains elements that will be necessary, too. Cheers, IJzeren Jan (talk) 18:38, 7 September 2024 (UTC)

@IJzeren Jan: This one you sent is exactly the one that is to be implemented ;) Iohanen (Garcez) (talk) 21:24, 7 September 2024 (UTC)

:)) IJzeren Jan (talk) 21:42, 7 September 2024 (UTC)