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.


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]

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]

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 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 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 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 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]
In addition to assistant languages (which are used by the translation interface), there can also be fallback languages, which are used by MediaWiki in case a translation is missing. The default (and ultimate) fallback language is English, but you can specify other fallback languages as well. For example, nds and stq fall back to German before English, nds-nl falls back to Dutch, while fy doesn’t have any extra fallback languages. These languages define only one fallback language, but there can be more – for example, Lower Sorbian (dsb) falls back to Upper Sorbian (hsb) and Upper Sorbian falls back to Lower Sorbian, before both falling back to German (and ultimately to English). Do you think fallback languages would make sense for East Frisian Low Saxon, and if yes, which? (Please note that unlike assistant languages, the order of fallback languages is very important, since the first language that has a translation wins.) —Tacsipacsi (talk) 15:05, 21 November 2024 (UTC)[reply]
That, in any case, will only become relevant after crossing the 13% threshold. (Although some translators into new languages are so quick that it happens after just a few days.) Amir E. Aharoni (talk) 15:13, 21 November 2024 (UTC)[reply]
I supposed that, but I figured it’s easier to collect all necessary information in this topic rather than having to reach out once the threshold is reached. (Also, fallback languages are the most important just after crossing the threshold, since that’s when the most untranslated messages there are.) —Tacsipacsi (talk) 15:44, 21 November 2024 (UTC)[reply]
I think English as fallback language will be sufficient. VanModers (talk) 13:09, 22 November 2024 (UTC)[reply]
Sorry, it took a bit of time because of the holidays in the U.S., but now it's Done Done
I deleted a lot of old translations that were identical to English or were invalid for some other reason. I left a few that looked like real translations, but marked them all as "outdated".
I added a list to your user page under that title "Links for East Frisian Low Saxon". I recommend using that list to start translating and cleaning up.
Good luck! :) Amir E. Aharoni (talk) 19:38, 4 December 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]

@GianAntonucci: Hello! The translation of the name of the main page is protected, because if you would change it, it would change the name of the actual main page of any wiki in that language. So if you had changed this, the main page of the Sicilian Wikipedia (and the Sicilian Wiktionary) would go from this to this the next time translations are imported to Wikipedia (which happens once a week). And since the latter page doesn't exist, every visitor to scn.wikipedia.org would get that empty page.
We can change the translation, but for languages with established project, we need to be very careful about how we do it. So in this case, I would like to at least see a discussion in the Sicilian Wikipedia about renaming the Main Page. There are four possible outcomes of such a discussion:
  1. No, don't change the translation --> we do nothing
  2. Yes, change the translation and move the Main Page in the Sicilian Wikipedia & Wiktionary --> move main pages from "Pàggina principali" to "Pàggina mastra", and leave a redirect
  3. Yes, change the translation, but don't move the Main Page in the Sicilian Wikipedia & Wiktionary --> create redirects from "Pàggina mastra" to "Pàggina principali" on those projects
  4. No, don't change the default translation, but move the pages on the Sicilian Wikipedia & Wiktionary --> move main pages and leave a redirect
Perhaps even more importantly, this will affect external wikis in the Sicilian language as well. I don't know if there are any other MediaWiki wikis in Sicilian, but as a Sicilian speaker, you might know of any, and/or know how to find out if there are any. If there are, they too should be informed about this change and asked about their opinion.
Sorry for the loooong message! Please let me know if anything is unclear. Jon Harald Søby (talk) 10:20, 22 November 2024 (UTC)[reply]

Template name

This template doesn't work. There is a link in this template, these link shows a translatewiki.net page when it should show the page of the wiki where the extension is.

Example with this message : Traduire — translatewiki.net. The template is used in the documentation, the link shows this page Version — translatewiki.net when it should show this page Version - Miraheze Meta Mahabarata (talk) 13:47, 21 November 2024 (UTC)[reply]

(To clarify, the discussion is about the template whose name is {{name}}.) --Amir E. Aharoni (talk) 14:07, 21 November 2024 (UTC)[reply]
Also, I don't think that it's a problem. It's just a general link to Special:Version. This special page has the same name on all wikis, whether the extension is not installed there or not, and the name of all the extensions that are installed on that wiki is shown on that page. These messages usually shouldn't be translated. Amir E. Aharoni (talk) 14:11, 21 November 2024 (UTC)[reply]
I'm agree with this particular case but the text talks about "a mediawiki extension or skin" : I think that this template should have at least 1 parameter to be able to indicate where (on which wiki) the "extension or skin" is. Mahabarata (talk) 11:42, 22 November 2024 (UTC)[reply]
Every extension and skin can be used on many wikis. Occasionally they are made for specific wikis, but most of the time they are general. Amir E. Aharoni (talk) 05:18, 23 November 2024 (UTC)[reply]
Not this template : the template begins with the special text "This is an optional message. Do not translate it if it would remain unchanged in your language."
It means that this template is a translatewiki template (see Template:Name — translatewiki.net) used only for documentation on translatewiki.
And when used on translatewiki documentation, the link to "Special:Version" arrives always on translatewiki website and never on the appropriate MediaWiki extension or skin.
In another way of speaking, this template currently never works. Mahabarata (talk) 20:02, 25 November 2024 (UTC)[reply]
I think that there's a misunderstanding here.
Any MediaWiki extension can be used on any MediaWiki site whose administrator chooses to install it. The Special:Version page appears on every MediaWiki site. The link in this template points to translatewiki to give an example of what the Special:Version page is. It will look a bit different on every site, but the general idea is that it has a list of installed extensions, and the Special:Version page here on translatewiki.net is an example. Amir E. Aharoni (talk) 20:26, 25 November 2024 (UTC)[reply]
Sorry but when I see a link in a documentation, I think that the link is useful and will give more information. This one doesn't.
I propose to replace this useless link by a link to mw:Special:MyLanguage/Help:Special_pages#V. Mahabarata (talk) 12:24, 4 December 2024 (UTC)[reply]
The way in which this link provides information is that it shows how this page look like: a table of extension names and descriptions. Amir E. Aharoni (talk) 17:14, 4 December 2024 (UTC)[reply]

Clones of globally blocked user

User:Trotinel_Iftode is a clone of Marianiftode1, which is globally blocked. See here. I think his translator rights should be revoked. Strainu (talk) 23:22, 21 November 2024 (UTC)[reply]

Google translation

Hello! Google machine translation does not work for Chechen and Avar and other languages ​​that were added recently, please sort this out. Умар (talk) 09:25, 25 November 2024 (UTC)[reply]

They probably just haven't made them available via the API yet. Nike (talk) 20:20, 26 November 2024 (UTC)[reply]
@Nike, Sorry, but the translator has recently worked. Умар (talk) 11:07, 3 December 2024 (UTC)[reply]
I don't understand. This is the list of languages that the API currently supports:
ab, ace, ach, af, ak, alz, am, ar, as, awa, ay, az, ba, ban, bbc, be, bem, bew, bg, bho, bik, bm, bn, br, bs, bts, btx, bua, ca, ceb, cgg, chm, ckb, cnh, co, crh, crs, cs, cv, cy, da, de, din, doi, dov, dv, dz, ee, el, en, eo, es, et, eu, fa, ff, fi, fj, fr, fy, ga, gaa, gd, gl, gn, gom, gu, ha, haw, he, hi, hil, hmn, hr, hrx, ht, hu, hy, id, ig, ilo, is, it, iw, ja, jv, jw, ka, kk, km, kn, ko, kri, ktu, ku, ky, la, lb, lg, li, lij, lmo, ln, lo, lt, ltg, luo, lus, lv, mai, mak, mg, mi, min, mk, ml, mn, mni-Mtei, mr, ms, ms-Arab, mt, my, ne, new, nl, no, nr, nso, nus, ny, oc, om, or, pa, pa-Arab, pag, pam, pap, pl, ps, pt, qu, rn, ro, rom, ru, rw, sa, scn, sd, sg, shn, si, sk, sl, sm, sn, so, sq, sr, ss, st, su, sv, sw, szl, ta, te, tet, tg, th, ti, tk, tl, tn, tr, ts, tt, ug, uk, ur, uz, vi, xh, yi, yo, yua, yue, zh, zh-CN, zh-TW, zu Nike (talk) 12:00, 3 December 2024 (UTC)[reply]
Participant @Amire80 remembers that the translator worked. At the moment the translator works in Content translation. Maybe it was temporarily disabled. Thanks for the answer. Умар (talk) 15:16, 3 December 2024 (UTC)[reply]
The language code for Chechen is ce (two letters). I don't see it in this list. It is definitely supported by the Google Translate interactive website now. Is it not supported in the API?
I'm not sure that it ever worked on translatewiki, but maybe it did. Amir E. Aharoni (talk) 15:58, 3 December 2024 (UTC)[reply]
This is the list of supported language codes from the API. Nike (talk) 21:42, 3 December 2024 (UTC)[reply]

New user script for translators

I just released Translator Buddy, a new user script to simplify working with MediaWiki messages for translators and non-translators alike. It adds links to translatewiki.net from interface messages on other wikis and extends uselang=qqx debugging mode to include popups that have message keys linking to translatewiki.net and local message page. (Most useful for other wikis, though the script can also be used on translatewiki.net itself.)

Initially I wanted to host and document it here but decided to host it on mediawiki.org instead as it is more accessible for Wikimedia users who might not be registered here. Please try it out using instructions on Translator Buddy and let me know what you think! stjn[ru] 20:09, 26 November 2024 (UTC)[reply]

Translation tool link in sidebar

Is it intentional that in MediaWiki:Sidebar, link to translation tool is actually a link to Special:LanguageStats instead? Would it be possible to make it so that there is a separate link to Special:Translate itself, preferably under ‘Translation tool’ label, and the language stats are under ‘Language stats’ link?

I understand that some people might prefer that table to pick and choose what they might translate, but for me personally, it just makes me do more clicks since I always just go to Special:Translate tab. Especially since the table interface is pretty clunky in comparison with the group picker at Special:Translate. It would also be good not to use a different label from ‘Navigation’ in the second subsection since that one gets hidden in Vector 2022 by default. Pinging @Nike for feedback on these proposals. stjn[ru] 14:18, 28 November 2024 (UTC)[reply]

It's very intentional. The idea is that people will pick what they want to translate, instead of ending in the default view of recent messages and translating across random projects. I agree that some power users want a different work flow. Nike (talk) 14:44, 28 November 2024 (UTC)[reply]
Maybe then there could be at least both links, for example Translate ("Translate") linking to Special:LanguageStats as it is now and Bw-sidebar-translate ("Translation tool") linking to Special:Translate itself? I think it can be added before FuzzyBot item so people use them more intentionally. stjn[ru] 15:39, 28 November 2024 (UTC)[reply]

Dot removal by bot (sugestion)

Can this be done by a bot in the futre. Its simple task. Milićević (talk) 11:39, 3 December 2024 (UTC)[reply]

Enable translation to Baltic Romani (rml)

I would like to translate into Baltic Romani (code: rml) in Cyrillic script (rml-Cyrl), native name in Cyrillic: романы. Danvintius Bookix (talk) 12:52, 4 December 2024 (UTC)[reply]

Retrieved from "https://translatewiki.net/w/i.php?title=Support&oldid=12772498"