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

Archives

2023

Jan	Feb	Mar	Apr
May	Jun	Jul	Aug
Sep	Oct	Nov	Dec

2024

Jan	Feb	Mar	Apr
May	Jun	Jul	Aug
Sep	Oct	Nov	Dec

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]

Could someone do something about this? —Tacsipacsi (talk) 21:42, 20 November 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 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 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]

Ok, thanks for your fixes and these explanations Mahabarata (talk) 11:47, 7 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. 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]

ccorg:

Can an administrator add an interwiki prefix ccorg: that matches the one that was added to the Wikimedia farm? Several messages in Wikimedia Creative Commons License Texts now use this prefix, including MediaWiki:Wm-license-cc-conditions-share alike-text/en. Translators are getting confused because it produces a redlink while the previous raw URL results in a fuzzy string. Thanks! Minh Nguyễn ^💬 06:16, 5 November 2024 (UTC)[reply]

@Minh Nguyen Thank you for your suggestion. I added the interwiki prefix now. Raymond 07:59, 5 November 2024 (UTC)[reply]

Thank you! Minh Nguyễn ^💬 08:00, 5 November 2024 (UTC)[reply]

Kindly rename my account!

Hello crats!, Kindly rename my account to Aafi. Thanks and regards. ─ The Aafī ^{^(talk)} 06:52, 5 November 2024 (UTC)[reply]

@Aafi done now. Raymond 08:01, 5 November 2024 (UTC)[reply]

Thanks @Raymond! _signed,Aafi ^(talk) 17:08, 9 November 2024 (UTC)[reply]

About Phabricator:phabricator-project-98fd625c4504ea59/fr

When i follow the documention link in https://translatewiki.net/w/i.php?title=Special:Translate&showMessage=phabricator-project-98fd625c4504ea59&group=phabricator-phabricator-project&language=fr&filter=&optional=1&action=translate, I can see that the text is on several lines with a maximum number of characters for each line.

I would like to know if we have to keep this formatting in the translated text (in this case, what is the maximum number ?) or if we may keep only line breaks for paragraphs ? Mahabarata (talk) 17:14, 5 November 2024 (UTC)[reply]

You can use standard formatting here - the message is postprocessed by code at https://phabricator.wikimedia.org/source/phabricator/browse/wmf%252Fstable/src/applications/config/option/PhabricatorApplicationConfigOptions.php$153 which replaces any single linebreaks with spaces. Phabricator's i18n style tends to result in messily-formatted strings like that, and I'm sorry, but there's nothing I can do about it. Pppery (talk) 18:05, 8 November 2024 (UTC)[reply]

OpenHistoriCMap

After OpenStreetMap (see a previous post), it is OpenHistoricMap which has been showing for several days 9 untranslated texts but nothing when I want to see these texts (even if I check facultative messages). Where can I find these messages ? Mahabarata (talk) 12:21, 7 November 2024 (UTC)[reply]

In this case, I have no idea. I hope someone else will be able to help you, or to fix the bug in the software if there’s one. —Tacsipacsi (talk) 16:50, 8 November 2024 (UTC)[reply]

When you say "the software" do you mean a bug on translatewiki.net or a bug in OpenHistoricMap ? Mahabarata (talk) 17:52, 9 November 2024 (UTC)[reply]

I mean translatewiki.net – however broken OpenHistoricMap is (probably it isn’t at all, but even if it was), the translatewiki.net software shouldn’t tell you there are things to translate at one place but tell otherwise at another place.

I can imagine it’s the same root cause as T378913: Translation statistics didn't update after translation unit deletions, although a bit differently manifested – nine messages were deleted in English (rather than in French, like what the bug report says), and the statistics wasn’t updated to account for them. This theory is supported by the fact that there are two languages in which exactly 9 messages are untranslated, and only one (apart from English) where less. Furthermore, it says there are 13 untranslated messages in Danish, but if I go there, I see only four untranslated non-optional messages, i.e. there are once again exactly 9 ghost messages. —Tacsipacsi (talk) 07:14, 10 November 2024 (UTC)[reply]

I don't know if it is the same issue, if there is a bug report about this issue or if someone should create a new bug report : if you look at Statistiques des groupes de messages — translatewiki.net, you can see, in the second column, that there are 42 messages for en and qqq, 41 messages for next ones and 40 for last ones. When you open qqq, select all, check facultative messages and count lines, there are 42 lines, perfect. But if you do the same for ia, there are 42 lines too, not 41. Same with languages with 40 messages, open any lines, select/check to see all lines, count and you will find 42 lines not 40. Mahabarata (talk) 13:34, 10 November 2024 (UTC)[reply]

Process of changes in source texts

What is process to get patches merged if they [just] modify original messages? Sometimes there are typos or rewordings in source language and it needs to be done in code. Is there common phabricator task or where to notify about waiting patches? I'm asking because I don' think they need separate phabricator tasks and I don't know about patches can be noticed if they are not mentioned in Phabricator Tasks or somewhere else.

Example: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/FlaggedRevs/+/1060931 Woytecr (talk) 00:28, 8 November 2024 (UTC)[reply]

There’s nothing special about message changes in this regard, other patches can also exist without Phabricator tasks – although such patches are indeed less visible. However, they’re not invisible: they can be seen on Gerrit, either on the main page (this is what you get if you go to https://gerrit.wikimedia.org/ logged out), or on repo-specific pages, e.g. for FlaggedRevs. It’s also possible to enable notifications in the Gerrit preferences (although I haven’t used it, so I don’t know how it works). So reviewers are able to find them if they want, although this can take a while. —Tacsipacsi (talk) 17:03, 8 November 2024 (UTC)[reply]

About Phabricator:phabricator-auth-aaf6ad0fa99fb063/fr

There are several messages (the one in the subject and others) with similar texts :

"**Redirect URI:**"
"copy the **Client ID** and **Client Secret** to"
"by clicking 'New Secret' first".

I want to know if the texts "*Redirect URI", "Client ID", "Client Secret" and "New Secret" are shown in any languages or if there are translations, and if any, what are the french translations ? Mahabarata (talk) 15:42, 8 November 2024 (UTC)[reply]

These pieces of text appear in the authentication providers, in this case on Twitch. I was able to set Twitch to French from the user menu, so I guess they’re translated, but I don’t have a Twitch account (nor do I want to create one), so I can’t tell what exactly the translation is. On the other hand, we can’t be sure what language the admin uses on Twitch, so including the English texts would definitely be helpful (as would be the French if we knew what they are). —Tacsipacsi (talk) 17:21, 8 November 2024 (UTC)[reply]

Ok, thanks : these texts are also in Phabricator:phabricator-auth-db5f7f275fe9cd24/fr. If you follow the link in the documentation, you will see the code. But I don't know where, when and how this code is executed. I was thinking maybe here Phacility - Phabricator but the page is in English and I found nothing in French. So where are the messages we have to translate ? It is really useful to spend time to translate when the first line in this link says "Phabricator is no longer actively maintained" ? Mahabarata (talk) 17:33, 9 November 2024 (UTC)[reply]

The Phabricator project on translatewiki is a hacked-together add-on that is used only by Wikimedia's instance and nowhere else, and plans to promote it further have not gone anywhere. Since this specific string is only displayed if you're an admin, there's no place to test it unless you set up your own local Phabricator instance which is a lot of work, and the translation is unlikely to be displayed to anyone.

Wikimedia's instance, despite being called "Phabricator", actually uses Phorge, which is still actively maintained, so old upstream's maintenance status isn't relevant.

I'm sorry that Phabricator's i18n setup is a mess and unlike most other projects, but it is. Pppery (talk) 01:18, 10 November 2024 (UTC)[reply]

Ok, very clear explanations, thanks. Just another question : why not to remove Phabricator from translatewiki, espacially when you look at Statistiques des groupes de messages — translatewiki.net ? Mahabarata (talk) 12:42, 10 November 2024 (UTC)[reply]

Why should it be removed? Despite all the jankiness it's still serving a useful purpose - if you have an account on Wikimedia Phabricator you can set French as your language setting and will see (almost) all of the interface on French - those translations come from the translatewiki.net project (albeit with an unfortunate delay of weeks to months between being made here and being deployed).

There was a point between mid 2022 and April 2024 when the translations on translatewiki.net weren't being deployed at all (because the one person who knew how to do it quit), but then I took up the mantle myself and plan to continue to do so. Pppery (talk) 17:58, 10 November 2024 (UTC)[reply]

Ok : I have an account on wikipedia phabricator but I never looked at settings : I just changed language and yes, I can see translations now ! Thanks for your explanations. Mahabarata (talk) 14:36, 11 November 2024 (UTC)[reply]

Some texts are missing in translatewiki: for example all texts on the main page Wikimedia Phabricator are missing Mahabarata (talk) 15:33, 11 November 2024 (UTC)[reply]

True. The reason being here that the Phabricator project translates code but those are data not code. It's similar to how if you go to https://en.wikipedia.org/?uselang=fr you see the content in French but the interface in English, except that unlike with Wikipedia the software development and source code is only done in English. I told you it's a janky mess, and I stand by that, but it at least minimally works. Pppery (talk) 01:22, 12 November 2024 (UTC)[reply]

Ok, thanks. Have a nice day. Mahabarata (talk) 12:08, 12 November 2024 (UTC)[reply]

Edit translated messages

Hi, I can not edit some messages (MediaWiki:Mainpage/crh-ro, MediaWiki:Mainpage-nstab/crh-ro), but they need to be translated to "Baş Sayipa". Or alternatively just delete this pages?Zolgoyo (talk) 21:06, 8 November 2024 (UTC)[reply]

Done. Amir E. Aharoni (talk) 14:47, 11 November 2024 (UTC)[reply]

I wrongly translated optional text

Hello, I accidentally translated a text into my local language with the note "Do not translate it if it would remain unchanged in your language.". Can you undo this?

Best, Jelican9 (talk) 08:57, 9 November 2024 (UTC)[reply]

@Jelican9 deleted now. Raymond 13:47, 9 November 2024 (UTC)[reply]

MediaWiki:Block-user-label-count-exceeds-limit/en

I think this message should be {{optional}}, as “10+” is fine in most languages. If someone agrees, can you set it as such? —Tacsipacsi (talk) 09:45, 10 November 2024 (UTC)[reply]

@Tacsipacsi Was wrongly done by me and fixed by Amir last night. Raymond 06:26, 11 November 2024 (UTC)[reply]

@Raymond: Thanks, but I wrote {{optional}}, not {{ignored}}. The intention of the authors is clearly to make this message translatable on Translatewiki – it’s just that it doesn’t need translation in most languages. —Tacsipacsi (talk) 07:55, 11 November 2024 (UTC)[reply]

@Tacsipacsi Ouch... 2 errors in the same patch. Note to self: don't commit before breakfast :-( Fixed now with https://gerrit.wikimedia.org/r/c/translatewiki/+/1089803 Raymond 15:10, 11 November 2024 (UTC)[reply]

Phabricator:phabricator-settings-3fff18ee881011d9/fi

Please delete Phabricator:phabricator-settings-3fff18ee881011d9/fi as identical to source. Thanks. Pppery (talk) 18:01, 10 November 2024 (UTC)[reply]

Done. Nike (talk) 18:13, 10 November 2024 (UTC)[reply]

Translate into Fur

I want to translate into the Fur language, ISO 639 code "fvr". Dinkawiki (talk) 16:09, 11 November 2024 (UTC)[reply]

It is already enabled. Please use the links on your user page to start translating. Amir E. Aharoni (talk) 02:07, 12 November 2024 (UTC)[reply]

Bamum Wikipedia (bax)

Please add new language Bamum (ISO639-3:bax), also known as Bamun, Bamoun, or Shupamum. It is distinct from an artificial language called Shü-mom, but draws from the same script (ISO15924:Bamu) as well as Latin with some IPA and diacritics. CharlesLRiley (talk) 01:54, 13 November 2024 (UTC)[reply]

"ꚶꛉ꛰꛲ꚫꛦꚳ", according to @Calvin Gbetnkom. Thanks! CharlesLRiley (talk) 00:15, 14 November 2024 (UTC)[reply]

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

Rename (PinkAmpersand→Tamzin)

Hi! toki a! Salut ! My account was renamed on WMF wikis a few years ago to Tamzin. Could someone please make the corresponding rename here? Thanks. sina pona. Merci bien. — PinkAmpers&^{(Je vous invite à me parler)} 03:36, 13 November 2024 (UTC)[reply]

Done Amir E. Aharoni (talk) 05:00, 13 November 2024 (UTC)[reply]

I am writing in the Incubator for likpakpaanl and I want to localize the software. The language code is xon.

N bi WUMBEI ALBERT (talk) 18:56, 16 November 2024 (UTC)[reply]

Done Amir E. Aharoni (talk) 14:26, 19 November 2024 (UTC)[reply]

Addition of language East Frisian Low Saxon (ISO639-3: frs)

Hi, could you please add the language East Frisian Low Saxon.

ISO639-3: frs

native name: Oostfräisk (also: Oostfräisk Plat)

script: Latin LTR VanModers (talk) 21:04, 18 November 2024 (UTC)[reply]

Hi!

Just to verify: Ethnologue says that the autonyms are "Oostfreesk" and "Plattdüütsk", but https://oostfraeisk.org/ says Oostfräisk, as you suggest. Do you prefer the https://oostfraeisk.org/ spelling? Amir E. Aharoni (talk) 19:08, 19 November 2024 (UTC)[reply]

Also, should I define any default assistant languages? We have many Germanic languages defined, and I'm not sure which ones to choose. I can think of de, nl, nds, nds-nl, stq, fy, and gsw, but I might be wrong. Amir E. Aharoni (talk) 19:10, 19 November 2024 (UTC)[reply]

Hi!

Yes I prefer the spelling at https://oostfraeisk.org/. Is far as I know https://oostfraeisk.org/ is currently the largest online dictionary for East Frisian Low Saxon. As for the assistant languages, I think en, de, stq, frr, fy, nl, nds and nds-nl would be fine. And is it possible to delete the old translations that are already in the wiki? We would like to start fresh.

Thanks! VanModers (talk) 10:00, 20 November 2024 (UTC)[reply]

Fix translation of "Main page" for Sicilian (ISO693-3: SCN): Pàggina principali > Pàggina mastra

I've tried to fix the translation of MediaWiki:Mainpage-nstab/scn and MediaWiki:Mainpage/scn, but the system wouldn’t allow me to. Instead, it directed me to write here on the Support page. Could you please update it from "Pàggina principali" to "Pàggina mastra"? The current translation is an unnecessary influence from the Ausbau language. Thanks! GianAntonucci (talk) 09:12, 19 November 2024 (UTC)[reply]