Support

Support — Problems? Questions? Suggestions? Write your message below. — See also the FAQ or try to catch us in IRC or in Telegram.

Start a discussion

Removing "old" threads

I don't think it's a good idea to remove threads where no one has answered. Here https://translatewiki.net/w/i.php?title=Support&oldid=prev&diff=12926051 is my thread and I was waiting for a response, but the bot knows better. Could you reprogram the bot to maybe archive threads which has "resolved" status which could be added to threads which are resolved. maro21 (talk) 18:27, 22 February 2025 (UTC) 13:35, 22 March 2025 (UTC) 14:10, 20 April 2025 (UTC)

Request to enable Rajasthani (raj)

Hello everyone,

I would like to request the addition of Rajasthani (language code: raj) to the list of languages available for translation in Wikipedia's software. The proposal for Rajasthani to get it's own Wikipedia is under review, and I believe we now have a strong case for it since we provided lots of textual evidence for modern standardized Rajasthani. One of the requirements there is to translate system messages through translatewiki, so I wanted to start the process by requesting Rajasthani's addition here. It also meets all the defined standards for inclusion

• Rajasthani (raj) is included in the latest standard issued by the International Organisation for Standardisation (ISO 639-3)
• Rajasthani (raj) can be written using Unicode.
• Rajasthani has several active editors working on the wikipedia incubator. They would also work to translate system prompts on translatewiki.
• Rajasthani is a living language and a general purpose language.

Rajasthani is spoken by tens of millions of people in primarily Western India, in states like Rajasthan and Madhya Pradesh. It is a recognized literary language by India's highest literary body, Sahitya Akademi, and the organization promotes the translation of Indian and foreign classics from other languages into Rajasthani and from Rajasthani into others.

The language uses the Devanagari script, and the name of the language in Rajasthani is "राजस्थानी". It is written from left to right (LTR). It is commonly only written in Devanagari, so only one script needs to be enabled. For MediaWiki, the language can fall back to Hindi.

The line in the data/langdb.yaml file should look like this - raj: [Deva, [AS], राजस्थानी] and this is the link to the incubator page for Wikipedia.

Enabling this language will allow native speakers to contribute effectively to Wikipedia in standard Rajasthani, promoting knowledge access and preservation of the language. I know the language well and am ready to start translating and contributing to the localization of Wikipedia’s interface into Rajasthani.

I appreciate your support and guidance on the next steps to make this possible. It would also be helpful for me to understand the issues on why it was disabled in the first place, so I can resolve those issues. Looking forward to your responses! Thanks in advance.

Magarw (talk) 12:41, 4 April 2025 (UTC)

The header on Portal:raj says it’s a “a deprecated macrolanguage”, which is also stated on https://iso639-3.sil.org/code/raj. Are you sure the Sahitya Akademi recognizes it as one literary language? —Tacsipacsi (talk) 16:16, 4 April 2025 (UTC)

Hi. Thanks for your reply. Let me clarify:

Portal: raj -- Yes, it does say it is a deprecated macrolanguage on this page, but I'm uncertain why this was written, as it is still actively supported by ISO639-3 in the very link you shared. There it says clearly that it is an active macrolanguage. On the proposal page, you can check out all the books, documents, blogs etc. I provided evidence for to the language committee. Whoever wrote the proposal didn't include such evidence for the modern Standard Rajasthani which would have made this process faster.

Sahitya Akademi - Yes. Sahitya Akademi recognizes it as one literary language. Here is the official government page that has one catalog for Rajasthani language, just like the other major official languages it publishes in. You may refer to it if you wish. Additionally, you can refer to their About page that clearly indicates that other than the 22 federally official languages, they support 2 more: English and Rajasthani. The exact blurb is shared below for ease of access:

> Languages Recognised: Besides the 22 languages enumerated in the Constitution of India, the SahityaAkademi has recognised English and Rajasthani as languages in which its programme may be implemented. Names of present members of various language Advisory Boards, which have been constituted to render advice for implementing literary programmes in these 24 languages are given in the website Magarw (talk) 16:33, 4 April 2025 (UTC)

I’m pretty sure – although I can’t find it written down anywhere – that macrolanguages are disallowed on Translatewiki. According to the Wikipedia article I linked above, 639-2 uses shared writing systems and literature more whereas 639-3 focuses on mutual intelligibility and shared lexicon. If ISO 639-3 recognize something as a macrolanguage rather than an individual language (as is the case for Rajasthani), SIL’s opinion is that individual languages belonging to it (which may be considered dialects by others) are not necessarily mutually intelligible. This makes software localization difficult – how will you ensure that all Rajasthani speakers understand the translations?

Anyway, it’s not my call whether Rajasthani is accepted at Translatewiki, as I’m just a fellow translator. Also, without being able to find the policy on macrolanguages, I’m not sure if and when exceptions are made. I hope someone else will clarify whether Rajasthani can be enabled or being a macrolanguage makes it a definite no. —Tacsipacsi (talk) 19:49, 4 April 2025 (UTC)

Hi, thanks for reply. Again, there are several points of confusion, so I'm happy to clarify. The summary is that Rajasthani is far from unique from the case of other languages, and I'm unsure why it is treated so differently. It is a standardized variety of a group of closely related lects/languages. That's how all standard varieties are formed. I'll address things point by point

<br>

Macrolanguages:

>> "I’m pretty sure – although I can’t find it written down anywhere – that macrolanguages are disallowed on Translatewiki."

Translatewiki has support for lots of macrolanguages from ISO 693-3. I'll give examples of bigger languages to drive the point home.

(i) Arabic (ara): Defined as a macrolanguage in 693-3 with over 28 individual languages. It has its own translatewiki and wikipedia as "[ar] Arabic - العربية". These are based on Modern Standard Arabic, even though the sublanguages in 693-3 are closely related and have varying levels of intelligibility. Modern Standard Rajasthani is the same, but the only difference is that its constituent speech varieties/lects are not nearly as different as the different Arabics. In addition, for Arabic, the sublanguages is 693-3, specifically Egyptian and Iraqi have their own translatewiki's as well, in addition to the macrolanguage (standardized variety) one. If Rajasthani sublanguages want to have their own Wikipedias over time, that's fine and they can go through the process like everyone else.

(ii) Chinese (zho): Defined as a macrolanguage in 693-3 with 19 languages under it. Despite being a macrolanguage, it has it's own translatewiki. I can see at least two projects under Chinese for both simplified and traditional scripts.

(iii) Serbo-Croatian: Defined as a macrolanguage in 693-3 with 4 languages underneath it. It has its own translatewiki in 2 scripts (latin and Cyrllic) under 'sh' and 'sh-Latn'

(iv) Mongolian (mon): Defined as a macrolanguage in 693-3 with 2 language varieties underneath it. I see that is has its own translatewiki under "[mn] Mongolian - монгол". mn is not the language code of either of the 2 varieties, but solely refers to the macrolanguage.

(v) Malay (msa): Defined a macrolanguage in 693-3 with 36 language varieties underneath it. Like the ones above, the macrolanguage defines a standardized variety that represents all the varieties that fall it. It has its own translatewiki under "[ms] Malay - Bahasa Melayu"

(vi) Sanskrit (san): Defined as a macrolanguage in 693-3 containing two varieties: Classical and Vedic Sanskrit. It has 1 translatewiki under "[sa] Sanskrit - संस्कृतम्".

I hope this clears things up, and at least addresses the first objection regarding Rajasthani being a macrolanguage. The macrolanguage like Arabic, Chinese, Malay, Mongolian etc. represents the modern standard variety.

<br>

Languages under a macrolanguage: intelligibility

>> "If ISO 639-3 recognize something as a macrolanguage rather than an individual language (as is the case for Rajasthani), SIL’s opinion is that individual languages belonging to it (which may be considered dialects by others) are not necessarily mutually intelligible."

Please see the official SIL policy on macrolanguages here. To quote, a macrolanguage contains "multiple, closely‐related individual languages that are deemed in some usage contexts to be a single language." Their opinion is that they use macrolanguages for both purposes. In the case of Chinese languages, there is widespread acknowledged divergence amongst the sublanguages. In case of Arabic, there is divergence among the Maghrebi vs the Khaleeji languages but not as much. In case of Rajasthani, the differences are next to nothing as it is spoken mainly in one state in India, with a concentrated geographical spread. They are often even intelligible to Punjabi and Hindi speakers, so there is no doubt that they are mutually intelligible. This is why there is only one Standard Rajasthani language recognized by the Sahitya Akademi. So, yes, 693-3 recognizes Rajasthani as a macrolanguage, but all varieties are mutually intelligible in its case.

>>This makes software localization difficult – how will you ensure that all Rajasthani speakers understand the translations?

All Rajasthani speakers will understand the translation because there is only one standardized variety that has widespread use across the state and is used widely online and in textbooks, in schools, colleges, and universities. Claims that suggest that Rajasthani speakers can not understand the standard written variety are misplaced.

<br>

Taking the call:

>> Anyway, it’s not my call whether Rajasthani is accepted at Translatewiki, as I’m just a fellow translator.

I hope it is soon, as there is no reason why it shouldn't.

>> Also, without being able to find the policy on macrolanguages, I’m not sure if and when exceptions are made. I hope someone else will clarify whether Rajasthani can be enabled or being a macrolanguage makes it a definite no.

Yes, there is limited clarity on the policy but as I have shared above, Rajasthani is not the only language that has a standard variety covering lots of different speech varieties. This is true for every single language: one (or sometimes more) standard written varieties and several different speech varieties, whose speakers use a shared written standard.

<br>

More evidence about Standard Rajasthani:

There are lots of online materials to indicate standard Rajasthani. The state of written language standardization can be gauged by looking at modern books, study materials, and textbooks being produced within the state - by both government and by regular people. The first will indicate the standard language that has the backing of the state, and the latter will indicate that there are regular people who will also contribute in Standard Rajasthani to Wikipedia.

• Aapno Rajasthan is a small encyclopedic project that has information not only about standard Rajasthani but about important people/personalities, literature, geography, politics etc. This is one fairly substantial sample of standard Rajasthani that is non-governmental.
• Learn Rajasthani is a small website that aims to explain the grammatical standardizations in Rajasthani and teach it to younger kids. It contains information about the language's evolution, standardization, literature, governmental support etc. The entire page is in Standard Rajasthani.
• Rajasthani Sabadkos This website is the web-interface version of the the biggest dictionary ever written for Standard Rajasthani by Mr. Sitaram Lalas. It makes the dictionary accessible by search, and additionally contains a web-accessible version of the Rajasthani grammar written by Mr. Lalas. The entire website and all its texts are in Standard Rajasthani. Since it is a very detailed grammar, it also contains some footnotes about nuances of the sublanguages like Malvai and Bagri, and how they differ in speech.
• Padhesari: This website is meant for students and contains information about the Rajasthani language and literature exams for Class 11, 12, undergraduate (BA), masters (MA), researchers (PhD students), national NET exam (for aspiring teachers/professors). You can see that the blog suggests popular standard Rajasthani books and materials to prepare for these exams. The books cover standard grammar, poetry, literature, etc.
• An example grammar book linked through Padhesari. On the first page, you can see that it is published by the Rajasthani State Textbook Publishers in Jaipur, and is written by the Secondary Education Board, Ajmer, for free circulation among State Universities. It is a standard Rajasthani grammar textbook for grades 11 and 12. It is written in Standard Rajasthani.
• Rajasthani Sahitya Sujas This book is hosted by Rajasthani Education Board on the official state government website (gov.in) and is the 2017-18 version of Part 1 of the Literature (prose-poetry) collection and syllabus for high-school students. It is a 200 page sample of Standard Rajasthani.

I hope these materials help make a decision in favor of granting Rajasthani (raj) its independent translatewiki page where residents of the state and other Rajasthani language speakers can contribute in Standard Rajasthani.

Next Steps

I would love to understand what other concerns folks at translatewiki have, and I am more than happy to clarify any questions that they have about the language. Magarw (talk) 02:11, 5 April 2025 (UTC)

Macro languages are not prohibited on translatewiki. The policy about language inclusion is at Translatewiki.net languages.

There are sometimes differences between translatewiki configuration and Wikimedia Language committee policies, but in this case, it probably makes sense to coördinate them. I brought this to the Language committee's attention. I hope to have an answer in about a week. --Amir E. Aharoni (talk) 15:07, 6 April 2025 (UTC)

Thank you for your comment @Amire80!! I completely agree that it makes sense to coordinate with them for this case. A joint and consistent decision would be helpful. I look forward to the Language Committee's response. Magarw (talk) 02:30, 7 April 2025 (UTC)

Just updating that we're probably going to do it soon, but we need to figure out a couple of technicalities. Thanks for your patience. Amir E. Aharoni (talk) 20:16, 24 April 2025 (UTC)

Sounds good. And, thank you for the update Magarw (talk) 22:28, 26 April 2025 (UTC)

Pazeh language on Translatewiki

Hi all,

Pazeh community here in Taiwan have just asked me about the issue that their language is not available on tranlatewiki and wikidata now.Please see this link. So I am here to help them request to enable the language of Pazeh on Translatewiki.

According to ISO 639-3, Pazeh language has their own code of pzh .

Thank you. Iyumu (talk) 06:10, 16 April 2025 (UTC)

Hi! Would you want to show any other languages as an assistant languages in the sidebar? ToluAyo (talk) 20:57, 24 April 2025 (UTC)

@ToluAyo Hi, thank you for the reply. Adding Mandarin Chinese(zh) to the sidebar will be the users of Pazeh community. Thank you! Iyumu (talk) 03:33, 28 April 2025 (UTC)

Delete

Hello, why are pages with {{delete}} not included in this category? Leo (talk) 17:30, 18 April 2025 (UTC)

@Leo: Categorization is suppressed in translation namespaces (like the MediaWiki namespace). A better way to find pages marked with {{delete}} is to use Special:Whatlinkshere/Template:Delete. This is also the method used in the admins-only gadget that notifies administrators about pending deletion requests. Jon Harald Søby (talk) 16:30, 22 April 2025 (UTC)

Thanks for your answer. Leo (talk) 03:26, 6 May 2025 (UTC)

Hundreds of bad translations

In Lingala, a new user has made in the last ten days dozens of translations worse and contributed over a thousand new translations, sometimes nearly every second (13 in one minute). The translations violate spelling rules, and some words are translated into French rather than Lingala. What should I do next? I can't quickly correct over 1,000 translations by hand. That's 200-300 hours of work! Etienne (talk) 10:07, 19 April 2025 (UTC)

@Eruedin: Hi! I have removed their translator rights now, so they can't make any more translations. Administrators here also have the option to remove all translations from a user – would that be preferrable to keeping and correcting them? We can also mark them as fuzzy, so that they remain here, but are easy to find in the translation interface (i.e. when using the "outated" tab on Special:Translate). Jon Harald Søby (talk) 08:15, 23 April 2025 (UTC)

@Eruedin, do you actually Lingala well yourself? You user page says "ln-1". Amir E. Aharoni (talk) 23:13, 28 April 2025 (UTC)

@Jon Harald Søby I think removing would probably be the saddest and yet the best. If you want to seriously check over 1000 translations and check the spelling (maybe 2/3 can be done with the spell checker, the rest you have to look up in dictionaries[3]), it takes well over a hundred hours. Time I don't have. And there are also some more complex texts that exceed my linguistic limits. That would be a task for someone who is a native speaker or has very good language skills and has the specialised vocabulary of computer science[1] and knows the spelling rules[2]. This person has never appeared here in recent years. And I can probably ask my friends who don't participate here occasionally, but not every other day. The translations were published so quickly one after the other that they were probably working with a bot and an automatic translator. I counted 10-13 translations per minute. That's superhumanly fast. All unfamiliar expressions were replaced by words in French. No spelling rules were observed. This looks very suspiciously like artificial intelligence that has been trained with some forum or other. The following should certainly be revised: (1) all expressions translated into French instead of lingala, (2) the vowels (add open o, open e; lingala has seven vowels), (3) the emphasis (add marked sound), (4) for synonyms: use the term from the glossary. Given the high tempo, probably also (5) how exactly the translation was made. I have contacted a lingala-speaking user group in the Congo and asked for their opinion. Maybe we will leave it pending until we get their response?

[1] e.g. as published in: Lexique informatique en lingála by Floribert Limbaya Litoti and Léon Bukasa Tshibaka; [2] Standardisation et uniformisation de l'orthographe des langues nationales of 1974; [3] https://meta.wikimedia.org/wiki/WikiLinguila/tools

@Amir E. Aharoni I'm not a native speaker. I've been learning Lingala for 20 years and helped develop the Lingala spelling checker for Hunspell, among other things. I know my linguistic limits and have a network of native speakers at my disposal, including dictionary authors and linguists.

Account renaming request

My account in Wikimedia (SRuizR) was renamed to Luigi Nakano, since I may soon become a recognized person in my university (I'm engaged with the student movement). I therefore no longer want my surname and initials to be present in my username. I'd like this account to be renamed too. Thanks in advance. SRuizR (talk) 18:22, 20 April 2025 (UTC)

@Luigi Nakano:  Done Jon Harald Søby (talk) 16:29, 22 April 2025 (UTC)

New project: how much time and work

Let's say I would like to move translations to Translatewiki from https://github.com/taginfo/taginfo/blob/master/web/i18n/en.yml. How much time and work does it take to create a project and messages in English? maro21 (talk) 15:38, 21 April 2025 (UTC)

@Maro21: See a high-level overview at Setup of a new project. The import happens automatically, directly from the YAML file, so creating the messages in English only takes computing time, not human one. (Okay, humans need to press some buttons, but it takes seconds to a few minutes. And it’s done by translatewiki.net administrators, not by you.) The project creation is also fairly straightforward, it’s a Gerrit change (the Gerrit equivalent of a GitHub pull request) to the translatewiki repo, and can be done by experienced users (but this part can be done by you as well). The most difficult and time-consuming part is preparing the repo. Some problems I noticed:

• The messages need documentation so that translators know what they translate. This is conventionally done in a “translation” with the language code qqq, although apparently this isn’t technically necessary: the openstreetmap.org repo doesn’t have a such file, and documentation is maintained on-wiki. However, I don’t recommend this: it’s easier (and less prone to mistakes) to change the English message and the documentation in the same PR than changing the English message in a PR, then wait until it’s updated on-wiki, and then update the documentation separately. If you still want to maintain the documentation on-wiki, then this step happens after the initial import, not before it.
• Translate doesn’t support symlinks, so it would import both Chinese translations twice (in addition to zh-hans and zh-hant, it’d also import zh-cn and zh-tw with the same content). There are three ways to avoid this:
  • Remove the symlinks. Without knowing the inner working of Taginfo, I don’t know how difficult or inconvenient this would be.
  • Manually exclude zh-cn and zh-tw in the translatewiki.net configuration. This should work, but needs manual maintenance in the (I guess unlikely) case of further symlinks appearing.
  • Somehow implement symlink support in Translate. This may be an overkill if no other projects have this problem (but may be useful if other projects avoid this problem only because of the hassle).
• While not technically necessary, I strongly suggest you to use CLDR plurals in messages, similarly to openstreetmap.org, instead of splitting them into two, for two reasons:
  • Some languages use different definition of “singular” and “plural” (e.g. zero counts as plural in some languages, including English, but counts as singular in others), or may even have more than two categories (e.g. three: “one”, “few”, “many”). The separate keys make it impossible to translate these messages into these languages.
  • If they use CLDR plurals, the translatewiki.net interface presents the two variants as one message (example), making it less likely for the variants to end up translated differently.

Tacsipacsi (talk) 21:09, 23 April 2025 (UTC)

Thank you for your detailed answer!! maro21 (talk) 21:57, 29 April 2025 (UTC)

Account renaming request

Howdy! Could someone please rename my username to EGobi? It is unclaimed here, and I would like to claim it to ensure consistency across my crosswiki usernames. TheEduGobi (talk) 07:46, 26 April 2025 (UTC)

@EGobi:  Done Jon Harald Søby (talk) 00:17, 5 May 2025 (UTC)

Edit tracking tools for Translatewiki

Greetings, all! I am asking, are there any edit tracking tools for Translatewiki used for edit-a-thons? Thanks and warm regards, Kambai Akau (talk) 13:11, 27 April 2025 (UTC)

@Kambai Akau: I am not aware of any such tools, unfortunately. If you need some stats for reporting, feel free to contact me in Telegram, and I can help you conjure up some numbers. 😊 Jon Harald Søby (talk) 00:19, 5 May 2025 (UTC)

Lol. Thanks @Jon Harald Søby! I will reach out surely. Kambai Akau (talk) 02:12, 5 May 2025 (UTC)

Request to rename username

Hi there! In Wikipedia, I use NikolasKHF as my username. Is there a possibility to change this account name to NikolasKHF instead? Also, when I change the username, can all of my past contributions refers to NikolasKHF and not this username, or will they still refer to the old username? Thanks in advance. ID Owly01 (talk) 01:53, 3 May 2025 (UTC)

@NikolasKHF:  Done. Your new username will appear in page histories and logs; the only place the old username will remain is in your signature in old discussions (like this one, for example). Jon Harald Søby (talk) 00:16, 5 May 2025 (UTC)

Thank you! NikolasKHF (talk) 01:39, 5 May 2025 (UTC)

Request to enable Puno Quechua (qxp)

I would like to request the addition of Puno Quechua language (qxp) to Translatewiki. Here is the Main Page. Thanks! Elwinlhq (talk) 22:14, 6 May 2025 (UTC)

@Elwinlhq: Sure! What is the language's autonym? The Spanish Wikipedia says "Punu qhichwa simi" – is that correct? Also, what should be the fallback/assistant languages for this language here in Translatewiki? I would suggest at least Quechua and Spanish, but maybe also some or all of the other Quechuan languages linked from Portal:Qu? Jon Harald Søby (talk) 06:18, 7 May 2025 (UTC)

@Jon Harald Søby: Thanks for the quick reply. It is right to say "Punu qhichwa simi", however it mainly corresponds to the geographic place and the macro language, which makes the name redundand. Nowadays, we tend not to use references to clarify the satements, For example:

• "Kastillanupi" (in spanish) intead of "kastilla simipi" (in spanish language)
• "Facebookpi" (on Facebook) instead of "Facebook nisqapi" (on the knwon as Facebook)

Therefore, we do not use anymore Qhichwa simi, we just say "Punu" or "Punu simi" and I would say just "Punu". About the assitant languages, I would appreciate to have Quechua, English, Spanish, and the other Quechua languages. Thanks! Elwinlhq (talk) 08:30, 7 May 2025 (UTC)

There's also the Punu language spoken in Western Africa (code puu). As far as I now, we have never received a request to enable it, but we may receive it some day, so writing just "Punu" is not great.

Would it be OK to write "Punu qhichwa", for example?

"Punu simi" is probably OK, too. Amir E. Aharoni (talk) 19:10, 8 May 2025 (UTC)

@Amire80: I see, well in that case "Punu qhichwa" should be ok. Some consideration to the name:

• The Puno region is populated for various language speakers, like Aymaras, Quechuas, Uros, and more and "Punu simi" would lead to confusion if we assume that it is the only language in the Puno area, although from a Quechua perspective it is right to call it "Punu".
• There are also cases where language autonyms are "adopted" based on the region/delimitations where the are settled. (I do not want to make a discussion about it).

Thanks for your support, I think "Punu qhichwa" sounds good. Elwinlhq (talk) 13:27, 9 May 2025 (UTC)

How to translate translatewiki.net?

I have searched and searched, and even asked ChatGPT, but I simply cannot find where to translate the user interface of translatewiki.net itself. Does anybody know where to do that? jhertel (talk) 17:19, 7 May 2025 (UTC)

It's not documented perfectly well, and it should be in the FAQ. (Or maybe it already is in the FAQ, but it's hard to find it because the word "translate" appears there so many times...)

Basically, translating all the components of the Translate extension (core user interface, page translation, search) as well as the "Translatewiki.net" project is supposed to localize most of translatewiki.net (the links point to translation into Danish, which is your main language if I understand correctly).

Translating other extensions that are used on translatewiki.net is necessary, too, such as Babel, ULS, and everything else on Special:Version.

Finally, there are some templates and documentation pages that can and should be translated, although I don't have a well-organized list.

We should probably organize it better. If you see something that should be translated, but isn't translated yet, please just bring it up here and we'll try to document it.

And since you can edit wikis, you are welcome to start contributing to this documentation and organization yourself ;) Amir E. Aharoni (talk) 18:10, 7 May 2025 (UTC)

Thank you, Amir, for such a pleasant and extensive answer! 🙂

Your links did lead me to some of the places I have tried, but where I couldn't find the strings I was specifically looking for. And I still can't find them. To be more specific, when translating MediaWiki, I stumbled over two specific Danish strings in the interface which are grammatically incorrect. I tried and tried to search for these messages but to no avail. Maybe I should have been more specific about which strings to begin with, but I just thought I was searching in all the wrong places and simply needed to be shown the right place. 🙂

The two specific sentences in Danish (yes, you guessed the language right) are "[redigere denne liste]" and "[udvide disse beskeder]", and they appear for instance at https://translatewiki.net/w/i.php?title=Special:Translate&showMessage=block-view-target&group=core&language=da&filter=&optional=1&action=translate to the right of the text box. The corresponding texts in English would be something like "[edit these messages]" and "[expand these messages]", although I don't know the exact English wording used, as those are just back translations.

Would you happen to know where I can find these? jhertel (talk) 23:25, 7 May 2025 (UTC)

Yes, I found these.

TLDR: You can translate them nicely in the translatewiki.net interface templates aggregate message group.

In more detail, they were in {{Template:Identical}}, which was kind of translated, but there were two problems with how it was done:

1. It was not translatable using the real translation system, but using wikitext tricks, which were hard to read and maintain. It was understandable back then, when the real translation system didn't work well with templates, but now it works much better, so it should be used in templates now. Some templates still use the old messy wikitext, and we replace it gradually.
2. A lot of the translations, including Danish, were written by a user who doesn't actually know the language, which is why I just deleted them now. (I'll restore a few that are likely good, but the rest should be written by people who know the languages.)

Amir E. Aharoni (talk) 00:36, 8 May 2025 (UTC)

Oh my God, that was extremely helpful! Thank you! 🙏

And you even explained where the strange Danish translations came from (I was wondering which Dane would have translated them such).

Thank you so much, Amir! jhertel (talk) 19:52, 8 May 2025 (UTC)

@Amire80: I tried to translate the template, but then I realized that 3 out of the 4 messages are redundant with those in Template:Related. Could we consolidate them somehow, so that there are only five messages to translate in the two templates together, rather than eight? —Tacsipacsi (talk) 10:46, 11 May 2025 (UTC)

Localization best practices recommend against message re-use :)

(For proper disclosure, I should mention that I wrote at least some of that section. However, when I did it, I just put in writing something that I had learned from @Siebrand and @Nike, and since I wrote it, it proved many times to be a good idea. There had been numerous bugs that would have been avoided if people didn't reuse messages.) Amir E. Aharoni (talk) 18:44, 11 May 2025 (UTC)

It’s about duplicating when the same word describes two concepts. “[collapse these messages]” over a list of messages and “[collapse these messages]” over a list of messages are the same concept. By the way, if these messages wouldn’t be overridden, both would display MediaWiki:collapsible-collapse, i.e. the reuse of the same message. —Tacsipacsi (talk) 23:12, 11 May 2025 (UTC)

Jhertel: in the future, if you come across a similar case, you can use the wiki syntax: insource:"redigere denne liste". maro21 (talk) 19:35, 8 May 2025 (UTC)

Ah, thank you, that was helpful! I will remember that. jhertel (talk) 19:53, 8 May 2025 (UTC)

Organizing an Event

I write to acknowledge you that the Anufo Language Wikimedians have an event and would be glad if you could expedite their approval when they create their accounts on Translatewiki.net site. Best regards Hasslaebetch (talk) 03:30, 17 May 2025 (UTC)