Jump to content

Support

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


Proposed script for [crh-ro] Dobrujan Tatar

The Cyrillic script is proposed to be added to crh-ro.

→ code: crh-cyrl-ro

→ native name: татарша

→ name: Dobrujan Tatar (Cyrillic script)

Thank you --Zolgoyo (talk) 15:02, 9 September 2024 (UTC)[reply]

Shouldn’t the native name also include some reference to Dobruja? Of course, the “Cyrillic script” part is not necessary in the native name as it’s obvious from the fact that it’s written as татарша and not tatarşa, but is also the region obvious from the spelling to any Tatar speaker (both Dobrujan and other)? —Tacsipacsi (talk) 10:25, 2 October 2024 (UTC)[reply]
In Dobruja is only the name "tatarşa" used, there is no specific regional name actually. Zolgoyo (talk) 17:11, 5 October 2024 (UTC)[reply]

Add Lingua Libre Django to translatewiki.net

Hello, I submitted a new project on Phabricator. Could someone review / accept it ? Yug (talk) 21:55, 28 September 2024 (UTC)[reply]

cc Amir E. Aharoni Hello All, can someone check this phabricator request ? Should I do something more ? Yug (talk) 18:40, 12 October 2024 (UTC)[reply]

Request to enable translation in [mfa]

Greetings, this is a request to enable Kelantan-Pattani Malay translation in the interface. The language's ISO 639-3 code is [mfa]. The native name should be Baso Klate-Ttaning for the sake of formality, yet it has many names: Kecek Kelate named by the Kelantan people, Baso/Kecek Taning or Baso/Kecek Nayu by the Pattani people. Thank you. Mirlim (talk) 04:04, 1 October 2024 (UTC)[reply]

Welcome!
What do you mean by "for the sake of formality"? Is this the most formal name? Do you have examples of its usage on other books or websites? Amir E. Aharoni (talk) 04:19, 1 October 2024 (UTC)[reply]
Sorry for the late response, we refer to a language with the word 'baso' or 'bahaso' which means 'language', yet we often mention the language as 'kecek klate/taning' but the word 'kecek' means speech/to speak. Here's the article briefly mentioned this as Bahaso Kelate Mirlim (talk) 03:06, 2 October 2024 (UTC)[reply]
The word for "language" actually doesn't have to appear at all, unless it's really necessary. For example, Javanese and Komering asked to use the names "Jawa" and "Kumoring" without the word "Basa". Can it perhaps be just "Kelate"?
The only place where I can find the name "Klate-Ttaning" is mfa Incubator itself, and we usually add names of languages only if we have external references. Amir E. Aharoni (talk) 13:49, 2 October 2024 (UTC)[reply]
The word should be appeared to distinguish with the Kelantan state of Malaysia. Also it should be spelled Klate since the schwa is dropped, creating the consonant cluster. Mirlim (talk) 04:05, 5 October 2024 (UTC)[reply]
OK, but this brings me back to the previous question: are there sources whether the name "Klate" is used? (Other than the Incubator.) Amir E. Aharoni (talk) 04:11, 5 October 2024 (UTC)[reply]
Yeah, as in Kelantanese Dialect Glossary, the word Klate used.
Also it should be named as Klate-Ttaning since Patani people also used the language, (the name Taning is used in media social, such as this page, the T is doubled indicating gemination). Mirlim (talk) 04:25, 5 October 2024 (UTC)[reply]
Where else is it doubled, other than in Wikipedia? That glossary link was quite good—do you have something like this for "Ttaning"? I couldn't find anything myself. Amir E. Aharoni (talk) 04:36, 5 October 2024 (UTC)[reply]
Yeah here at page 112 (in french). Note that the language is not having any official spelling yet, makes it has various spellings for a word (or name). Mirlim (talk) 04:50, 5 October 2024 (UTC)[reply]
OK, I have one more question, and it will probably be the last one. On the page m:Requests for new languages/Wikipedia Yawi, a Wikipedia in this language is proposed, and the name suggested there is "Yawi". Could that perhaps be a good name?
Sorry about asking so many questions—I would really love to get this right. Amir E. Aharoni (talk) 01:24, 9 October 2024 (UTC)[reply]
I think I won't suggest Yawi as the language's name since Yawi is a corrupted form from Jawi which could mean: 1) Malay people themselves, as a phrase "Masuk Jawi" same as "Masuk Melayu" which means to enter malayness (page 30), then "bahasa Yawi" literally means Malay language since Kelantan and Pattani people are also considered as Malay people, 2) Jawi is actually name for Arabic script written in Malay, as Yawi refers not to a spoken language but to the written form (page 110). People on the page seem confused about requesting an "Arabic-written Malay Wikipedia" already available in Malay Wikipedia. Yet, Kelantan-Pattani Malay is quite different from the Malay proper.
Also sorry that I chose Baso Klate-Ttaning as the name, yet the word "kecek" also could mean 'language' as this refer "Kecek Nnayu" as "Bahasa Melayu" (Malay language). Thus, i request "Kecek Klate-Ttaning" as the name. Mirlim (talk) 03:46, 9 October 2024 (UTC)[reply]
OK, I think I'll go for "Kecek Klate-Ttaning" or "Klate-Ttaning" for now, but I'll be open to changing it in the future if a better name is found.
Is it important to include the word "Kecek" or is "Klate-Ttaning" enough? Amir E. Aharoni (talk) 14:39, 9 October 2024 (UTC)[reply]
Yes Mirlim (talk) 15:01, 9 October 2024 (UTC)[reply]
"Yes" to which option: "Kecek Klate-Ttaning" or "Klate-Ttaning"? Amir E. Aharoni (talk) 15:05, 9 October 2024 (UTC)[reply]
I think it should be "Klate-Ttaning" for now. Mirlim (talk) 15:21, 9 October 2024 (UTC)[reply]
OK, thank you for your patience. We'll enable it soon. Amir E. Aharoni (talk) 16:49, 9 October 2024 (UTC)[reply]
Done Done Amir E. Aharoni (talk) 20:26, 9 October 2024 (UTC)[reply]

Request deletion of translation

The above messages have corresponding zh-hant versions. They are duplicate messages and should be untranslated.--铁桶 (Talk) 09:37, 3 October 2024 (UTC)[reply]

@铁桶: Those messages don't exist here in Translatewiki, and as far as I can see, they never did. They appear as blue links because the MediaWiki namespace is a little bit special, and they show the zh-hant messages because of fallback rules, but there isn't actually any content on those pages. Jon Harald Søby (talk) 14:24, 10 October 2024 (UTC)[reply]
Sorry, I didn't carefully see the page history.--铁桶 (Talk) 14:34, 10 October 2024 (UTC)[reply]

Remove translation right

Please remove translation right for user:San1joy23. They made 300+ translation in couple of hours and all are machine translated. Now i am spending hours to fix their mess. আফতাবুজ্জামান (talk) 20:00, 12 October 2024 (UTC)[reply]

Ok sure next time won't be repeated this mistake ,Iam so sorry for that . San1joy23 (talk) 05:49, 13 October 2024 (UTC)[reply]
@আফতাবুজ্জামান: Done. Administrators have a tool to mass delete/revert changes made by a specific user. Would you like me to delete all of their contributions, so you don't have to spend time cleaning them up? Jon Harald Søby (talk) 11:58, 14 October 2024 (UTC)[reply]
@Jon Harald Søby, Thanks. I fixed some, i hope to fix rest in 2-3 days. আফতাবুজ্জামান (talk) 18:56, 14 October 2024 (UTC)[reply]
@আফতাবুজ্জামান: Okay, great. Let us know if you need any help! Jon Harald Søby (talk) 09:53, 15 October 2024 (UTC)[reply]

Please add a new language Medumba (BYV)

Hi,

I wish to translate the Wiki UI in Medumba (byv).

Best,

Ngadou Yopa Ngadou.yopa (talk) 18:20, 13 October 2024 (UTC)[reply]

Mə̀dʉ̂mbɑ̀ Ngadou.yopa (talk) 18:23, 13 October 2024 (UTC)[reply]
Done Done Amir E. Aharoni (talk) 02:52, 18 October 2024 (UTC)[reply]

Disallowing import/submission of translations that don't include the right HTML tags

Hi, I wanted to bring this up for discussion based on a conversation I had with Amir here: User talk:Seanlip#c-Amire80-20241015024400-Seanlip-20241015021200.

I'm the maintainer of the Oppia project, which uses translatewiki for platform string translations. We have been getting some translations whose HTML tags don't match the source tags (sometimes the anchor tags are missing or wrong, or sometimes bold tags are missing, etc.) and this has resulted in our needing to remove those translations manually when we do an import from translatewiki.

I just wanted to check whether there is a way for translatewiki to detect this and block such translations from being submitted (or not include them in the push to the origin repo)? If not, no worries, we are fine with handling it manually, but just thought I'd double-check.

Thanks! Seanlip (talk) 03:47, 15 October 2024 (UTC)[reply]

I don’t think such a validator exists right now, but it should be possible to create one – there’s already a validator that checks that the same links are used in translations of MediaWiki messages than in the English ones, and what you need is basically the same (check that some stuff in the translation is the same as in the original, with no additions or removals), just with different syntax. —Tacsipacsi (talk) 20:19, 17 October 2024 (UTC)[reply]

Translation of Anufo Language into Wikipedia Software

Anufo Language also refered as Chokosi is a language spoken by people from Ivory Coast, Ghana, Togo and some African countries. Due to the growing number of the language speakers and the need to protect the language and cultural heritage from changes and extinction, we are poised to digitalize it on wikipedia. We therefore request that we are assisted to translated wikipedia software to Anufo

The language code is cko.

Best regards Salifu Ramatu (talk) 17:20, 15 October 2024 (UTC)[reply]

Done Done Amir E. Aharoni (talk) 02:51, 18 October 2024 (UTC)[reply]

Torwali - "trw"

Need support Zulfi (talk) 23:58, 18 October 2024 (UTC)[reply]

Sure, how can I help?
Your language is already enabled for translation.
If you want to start translating the software for Wikipedia, do the following:
  1. Go to your user page by clicking your username at the top of the page.
  2. Check the list under "Links for Torwali".
  3. Click the first item in the list: "Most used / Most important".
  4. Type the translation for each item and press "Publish".
I also recommend reading the guides in the "Guides" section in the same list.
If you need any more support, just ask! Amir E. Aharoni (talk) 00:07, 19 October 2024 (UTC)[reply]

Admin rights request

I want to update the templates on this wiki to support Vector 2022’s night mode (and do additional fixes where appropriate). Most of templates are not protected, but stuff like Template:ProcessNavigation isn’t. Can I get admin rights to edit such templates? (I am currently an interface administrator in Russian Wikipedia.) stjn[ru] 14:33, 19 October 2024 (UTC)[reply]

Now thinking about it, unprotecting the page in question would also work. Currently the most Special:LintErrors/night-mode-unaware-background-color hits on the wiki are created by that single template.
If some translation administrator can also approve changes to Template:Related, it would be good. stjn[ru] 11:26, 21 October 2024 (UTC)[reply]
Most templates are fixed now (40,000 lint errors related to night mode before, and only a 1,000 now), but stuff like MediaWiki:Editnotice-10-Identical can’t be fixed by someone without admin access. stjn[ru] 12:07, 22 October 2024 (UTC)[reply]
Can you elaborate on which things you are unable to fix, and which rights (re Special:ListGroupRights) are needed? I think `sysop` might be enough for Editnotice-10-Identical, but are there other things? Nike (talk) 12:21, 22 October 2024 (UTC)[reply]
I think only those types of messages are left now (MediaWiki:Editnotice-10-Identical, MediaWiki:Editnotice-10-Related etc.). It’s a small bunch, so the rights are not necessary any longer, I just initially thought they would be.
The biggest issue was with Template:ProcessNavigation (which for some reason is two separate templates, but that’s beside the point), which is now fixed after Amire80 unprotected it. Thankfully most of the wiki isn’t protected. stjn[ru] 12:32, 22 October 2024 (UTC)[reply]
Also, the fix in Translating:MediaWiki/Statistics in time is pending translation approval. stjn[ru] 12:37, 22 October 2024 (UTC)[reply]
I've approved it. I also don't know how to fix the messages you linked, so I gave you temporary sysop rights. Nike (talk) 10:33, 23 October 2024 (UTC)[reply]

Delete non-translations in hif-latn

Smcnarayan contributed a number of “translations” that are characterwise the same as the English original, and these non-translations somehow went unnoticed for seven years (maybe because most of the translations are different from the English originals, so they at least look like valid translations – I don’t speak Fiji Hindi, so I can’t tell for sure). The following 64 messages repeat characterwise the English originals:

While some shorter ones may actually be correct in Fiji Hindi as well, longer ones like MediaWiki:Api-error-filetype-banned-type/hif-latn certainly aren’t, and we don’t lose anything by deleting the shorter ones either: the same English message steps in. So could someone delete these messages?

I also think that quite a few of the other edits are non-translations, but I couldn’t find an easy way to find those using Pywikibot. Here’s what I did; if someone has an idea for finding further non-translations, I’d welcome it.

>>> site = ... # got a pywikibot.Site object for Translatewiki
>>> contribs = list(site.usercontribs('Smcnarayan'))
>>> messages = [c['title'].partition('/') for c in contribs]
>>> msgs = [msg for (msg, slash, lang) in messages if lang == 'hif-latn']
>>> len(msgs)
640
>>> contents = {msg: (pywikibot.Page(site, msg + '/hif-latn').get(), pywikibot.Page(site, msg + '/en').get()) for msg in msgs}
>>> bad = [(id, en) for (id, (hif, en)) in contents.items() if hif == en]
>>> len(bad)
64

Tacsipacsi (talk) 22:51, 19 October 2024 (UTC)[reply]

Msg- templates

I rewrote Template:Msg-meta to use Module:Msg, mostly to fix the issues with multi-line messages (which broke any lists before) and to make the template code a bit more understandable. The template should work and look pretty much the same as before (as far as I understand it).

msgnw: is not directly available in Lua, so the module now uses a more roundabout way of doing the same. There might be some differences in display compared to the previous wikitext version as a result. Additionally, messages which do not exist in the user language now show (page does not exist). Let me know if anything is displaying not as it should’ve been. stjn[ru] 19:13, 21 October 2024 (UTC)[reply]

  • That not existing part makes an assumption on how Special:Translations/MediaWiki:Red-link-title looks like (the parameter is at the very beginning). This assumption stands in 498 out of 511 languages, but fails in 11 (and in another two, where translators simply skipped the parameter for some reason). For example, in Japanese, the page name is in quotation marks (This-message-does-not-exist」 (存在しないページ)), and in American Sign Language, it should be in the middle of the message (M531x516S15a37501x485S1f550507x492S20e00487x496S26a02470x489 This-message-does-not-exist M524x543S33500476x483S15a01471x520S2890a487x513).
    • Is this really necessary? Couldn’t the message simply be dropped, i.e. nothing parenthesized shown if the message doesn’t exist?
    • If it is, could you please make it so that it uses the parameter, fixing the above-mentioned eleven languages?
  • It also falls short for empty messages: for example, {{msg-mw|word-separator|lang=zh-hant}} results in Word-separator(空), stating that the message doesn’t exist – it does, it’s just (intentionally) empty.
  • While it properly marks up the message key to be in English (although I probably would’ve chosen zxx, no linguistic content, as the message key is more like software code than real English text), it doesn’t mark up the whole as being in the target language. This means that in my above examples, there’s no machine-readable indication that the translations are in Japanese, American Sign Language and Traditional Chinese respectively. This should probably be an easy fix.
  • According to the template documentation, it should add a tracking category by default if the message doesn’t exist, but I don’t see that category being added. (I’ve added a test case to the module documentation about this.)
  • There are 426 pages in Category:Pages with script errors, likely most if not all of them are due to your module. (I haven’t looked into them, except for the message documentation, where I intentionally caused script errors using edge case test cases. While the parameters I made up are clearly broken, I’m not sure if Lua errors are the best way to handle them.)
Tacsipacsi (talk) 18:24, 23 October 2024 (UTC)[reply]
1) Good on noticing that. It is not ‘necessary’, but previously there was an indication that the message is not present in the user language specifically, so I implemented it like this since msgnw: isn’t a thing. So I’ll make it pass the parameter for now.
2) I guess module needs to check for nil specifically. Will be fixed.
3) I didn’t add it on the assumption that this template is mostly used with user language and so it didn’t make sense to increase the page code. But I guess that’s a minor concern and that’s better to add. Will change to zxx.
4) The code in {{Msg-mw}} does not do checks for the existence of the messages by default. I assume it has to do with the fact that Translatewiki’s limit on the number of such checks is low (100 pages total) and so MW messages would exhaust it. I didn’t change anything about it, if the template is configured to check for existence of the messages, it does, see {{Msg-osm}} / Category:Message maintenance/msg-osm.
5) I’ll add the error tracking for such cases. Though it is a bit problematic here on Translatewiki that Category:Message maintenance does not display the total amounts of pages in subcategories, I assume because of the technical limits.
Thanks for taking the time to review! stjn[ru] 22:41, 23 October 2024 (UTC)[reply]
Updating initial reply now that I think I’m done with fixes. 426 Category:Pages with script errors hits were there because of this configuration error in {{msg-translating}}. Putting actual namespace name in that template fixed them. I’ve added error handling to the module, but it is obviously only available in English now. stjn[ru] 23:40, 24 October 2024 (UTC)[reply]
Writing down another problem with the current implementation: uselang=zh would display ‘Page does not exist’ for every message because, obviously, there are no page contents in those cases. That seems like a big problem since users can technically set and see pages in non-variant languages (unless I am misunderstanding it), so some workaround for msgnw: is actually going to be needed.
Update: switched to using frame:preprocess calling msgnw: for now. stjn[ru] 23:22, 23 October 2024 (UTC)[reply]

Translating Wikipedia software to Mampruli

Please I want to translate Wikipedia's software into Mampruli, and the language code is "maw" Christian Yakubu (talk) 01:29, 22 October 2024 (UTC)[reply]

Done Done Amir E. Aharoni (talk) 16:58, 22 October 2024 (UTC)[reply]

Request to translate the Wikimeda software and Wikipedia into Maguindanaon/Basa Magindanawn

Hello, I would like to request the translation of the Wikimeda software and Wikipedia into Maguindanaon, and that the language code of the language is "mdh". Thanks! (talk) 16:48, 22 October 2024 (UTC) Bangsa Manusia (talk) 08:49, 22 October 2024 (UTC)[reply]

Done Done Amir E. Aharoni (talk) 22:03, 22 October 2024 (UTC)[reply]

Template translations

While updating things for night mode, I’ve noticed that templates here are all over the place in terms of their localisation. Some have translation syntax in their code, like Template:Related, others are localised page by page, like Template:Desc or even MediaWiki:Editnotice-8, and some have their translations in their code directly, like Template:Identical.

  • 1st approach looks the least problematic, though you do have to ask translation administrators to approve any changes to templates.
  • 3rd approach is a bit problematic since the template code increases exponentially with the amount of translations.
  • 2nd approach is the worst out of three since any changes to the head template are not actually guaranteed to be synced to the translations, and any substantive code changes have to be done 10+ times on every subpage. Most of this comes from uses of Template:Localized (but for some reason Template:Optional also uses that template while having the 1st approach system).

Since converting them all is a lot of work, it would be great if the more forward-facing templates which users actually see a lot while translating would be converted to Special:Translate-based system, like Template:Related. Then maybe a common group for templates specifically could be made under Translatewiki.net documentation. I want to, for example, update Template:Flagged Revs or Template:Doc-markdown (among others) but they use the 2nd approach, so any changes I’d do on those pages would need to be done separately for all the 10+ translations. I’ve already done it that way for edit notices and it is very, very tedious.

Maybe someone with translation administrator experience on this wiki or other wikis would want to assist with an effort to convert some templates? stjn[ru] 02:22, 24 October 2024 (UTC)[reply]

It's mostly been stuck on not having an easy way to display translated templates in user language. I'm hoping this will change in the coming year. Nike (talk) 19:29, 24 October 2024 (UTC)[reply]
As far as I can see, Template:Related displays in the user language without much hacks. stjn[ru] 23:00, 24 October 2024 (UTC)[reply]

Replacing British English messages with American spellings

User:Samthecrazyman has been continuously editing the British English message pages (/en-gb) to replace them with American spellings.

I have warned them, but they continue to do so. Shirayuki (talk) 00:20, 26 October 2024 (UTC)[reply]

Username change request

Hello. A while ago, I changed my username from Zapipedia (WMF) to IZapico (WMF) in the Wikimedia projects. To be consistent in all the spaces, I would like to have my username also updated here in Translatewiki to IZapico (WMF). Is it possible? Thank you! Zapipedia (WMF) (talk) 15:57, 28 October 2024 (UTC)[reply]

@IZapico (WMF) Done. Raymond 21:01, 28 October 2024 (UTC)[reply]

Openstreetmap

When i open the page Statistiques de langue — translatewiki.net to see what translations are needed, there is a line "OpenStreetMap" with 3 untranslated messages.

When I want to see these messages (by clicking on "OpenStreetMap"), the new page shows a message "Nothing to translate".

Where are the 3 untranslated messages ? If there is nothing to translate, why the first page shows 3 untranslated messages ?

For information we have this incoherent information for several days.

Could someone fix it ? Mahabarata (talk) 17:24, 30 October 2024 (UTC)[reply]

There are three outdated optional messages, I think that’s what the table means. (Of them, Osm:Site.copyright.legal_babble.contributors_at_cc_by_at_with_amendments_url/fr should probably be deleted, since it has no French-specific customizations; the other two need to be updated.) —Tacsipacsi (talk) 09:50, 31 October 2024 (UTC)[reply]
I improved translation of your second link.
Your first link still shows me nothing to do (when stats now show 2 things to do) : is it an issue with my user settings ? Or I have no auth to translate some special texts ?
Could you copy the 2 other links I cannot see ? Mahabarata (talk) 17:43, 31 October 2024 (UTC)[reply]
It’s not a settings or permission issue, but probably a bug in how the translation interface interprets the URL. The &optional=1 at the end of the URL should automatically tick the Optional messages checkbox in the three-dot menu (which is next to the Translated tab), but apparently it doesn’t, so you have to tick that checkbox manually. In case that still doesn’t work for you: the two messages are Osm:Accounts.edit.contributor_terms.link/fr and Osm:Users.new.by_signing_up.contributor_terms_url/fr. —Tacsipacsi (talk) 22:05, 31 October 2024 (UTC)[reply]
I’ve created phab:T378804 about the URL interpretation bug. I hope the fix will be installed on Translatewiki sometime next week; until then, you need to check the checkbox manually. —Tacsipacsi (talk) 10:22, 1 November 2024 (UTC)[reply]
Thanks a lot for your explanations, very clear : I fixed all outdated messages. Best regard Mahabarata (talk) 15:11, 3 November 2024 (UTC)[reply]
I think there is another problem with facultative messages : I'm not sure but it seems that we don't need to translate these messages. But sometimes someone did it. When the message is changing, it appears as a outdated message. Rather than to replace the facultative outdated text by a new one, the best solution should be to remove the useless translated text. But when we remove the translated text, it is impossible to save the change because the button is disabled. I tried to remove the translation on the page (see « MediaWiki:Drawioconnector-tag-drawio-title/fr » : historique des versions — translatewiki.net) but I suspected that now nothing will appear on french MediaWiki for this message so I cancelled my change. The best solution should be to remove the page itself but I cannot do it and I didn't find a template to ask for that. Mahabarata (talk) 16:27, 3 November 2024 (UTC)[reply]

Thanks a lot for your explanations, very clear : I fixed all outdated messages.

What apparently wasn’t clear for you: these translations exist to provide better user experience – to link to the French version (which, as far as I understand, is just as official as the English one). I’ve fixed them to use the new domain but once again link to the French page.

Rather than to replace the facultative outdated text by a new one, the best solution should be to remove the useless translated text.

Outdated doesn’t mean useless. Whether the the outdated translation (whether of an optional message or not) is more useful than the English original depends on (at least) three things:
  • How much extra value the translation provides. Optional messages often provide less extra value than non-optional ones (e.g. just some extra formatting), but this is not always true. In case of this OSM terms link, it makes users have to click one more and have to figure out how to get from the English page to the French one (which may be challenging for people who don’t speak English). In case of the tirol.gv.at link, the translation provides zero extra value, since it’s exactly same as the English text (so it shouldn’t have been created in the first place).
  • How much trouble the outdated translation causes (e.g. not applying typo fixes causes no trouble, not applying naming changes causes little trouble, not adding extra information added in English causes moderate trouble, leaving incorrect/misleading information there can cause a lot of trouble). In case of the OSM terms link, the old URL automatically redirects to the new one, so the outdated translation caused no trouble. In case of the tirol.gv.at link, the two versions point to two completely different pages, which may cause a lot of trouble (although I have no idea where the link appears, so it may not be).
  • How much easier it is for translators to update rather than re-translate. We don’t want to waste translators’ time; if a single word changed in a whole paragraph, changing that single word in the translation is much quicker than re-translating the whole paragraph. In case of these URL changes, the translator needs to check the linked page anyway, so it’s neither easier nor more difficult to update rather than re-translate.
  • In case of optional messages, an extra factor is preserving the piece of information that the message does need translation in that particular language. Someone has already determined that it does; if we delete the translation, someone will need to discover that again (and it’s quite possible that no one will do so, at least within a reasonable time).
Currently there are three ways to handle changes, one of which needs to be selected based on the above criteria:
  • If outdated translations should really not appear, create a new message (with a new name) and drop the old one. In this case, all translations are lost and need to be redone from scratch. (This may not be possible if some external constraints dictate the message name.)
  • If outdated translations are okay but should eventually be fixed, keep the message name but mark the translations outdated. In the vast majority of cases, this is the preferable approach.
  • If the changes to the English text don’t make the translations outdated (e.g. only typo fixes), keep the message name and don’t mark the translations outdated either.

But when we remove the translated text, it is impossible to save the change because the button is disabled. I tried to remove the translation on the page (see « MediaWiki:Drawioconnector-tag-drawio-title/fr » : historique des versions — translatewiki.net) but I suspected that now nothing will appear on french MediaWiki for this message so I cancelled my change. The best solution should be to remove the page itself but I cannot do it and I didn't find a template to ask for that.

I’m not sure how OSM works, but in MediaWiki indeed blanking a message is not the same as deleting it (e.g. MediaWiki:Word-separator/zh-hant is intentionally blanked to override the English message). If you want a message to be deleted, I think the most appropriate way is to just ask on this very page. ({{Delete}} does exist, but using that in messages would make {{Delete}} to appear on OSM, so it should only be used in non-message namespaces or messages that are no longer exported.) —Tacsipacsi (talk) 18:53, 3 November 2024 (UTC)[reply]

Fur Wikipedia

I would like to translate into Fur, ISO 639 code "fvr". Dinkawiki (talk) 11:49, 31 October 2024 (UTC)[reply]

Done Done. Amir E. Aharoni (talk) 15:41, 3 November 2024 (UTC)[reply]

Inquiry is related to Old Mon (omx)

I would like to know if it is possible to build an Old Mon wiki like the Old English wiki, but I wish to build an Old Mon wiki for the preservation of the Old Mon language. I myself am an ancient researcher, and I want to preserve the Old Mon language so that it does not disappear, but I would also like to know the views of the wiki officials, thanks.𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 08:41, 3 November 2024 (UTC)[reply]

It will not be enabled for interface translation on translatewiki according to the policy on Translatewiki.net languages: "Our current policy for accepting a new language for localisation at translatewiki.net is [...] that it should be a living language and a general purpose language".
It's not directly related to translatewiki, but I will also mention that the Language proposal policy for creating new Wikipedia sites says that a Wikipedia site cannot be created in ancient languages. It is possible to create a Wikisource site in ancient languages, but the recommendation is that such languages should be bundled with the modern equivalent Wikisource project. There is already a start of a Wikisource in the Mon language: Main Page/mnw. I recommend writing texts in both Modern and Old Mon there. If you and your friends organize many Mon texts there well, a full-fledged Mon Wikisource site will be created at its own domain: mnw.wikisource.org.
Some ancient languages, like Old English and Pali, have their own editions of Wikipedia. They were created long ago, and the current policy doesn't allow creating new ones. Amir E. Aharoni (talk) 15:41, 3 November 2024 (UTC)[reply]
Okay thanks 𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 07:13, 4 November 2024 (UTC)[reply]