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.
Archives
2023
  • Jan
  • Feb
  • Mar
  • Apr
  • May
  • Jun
  • Jul
  • Aug
  • Sep
  • Oct
  • Nov
  • Dec
2024
2025
  • Jan
  • Feb
  • Mar
  • Apr
  • May
  • Jun
  • Jul
  • Aug
  • Sep
  • Oct
  • Nov
  • Dec


Category:Supported projects

Is there any reason why some projects in this category are under * and some under letters A,B,C...? maro21 (talk) 13:01, 11 January 2025 (UTC) maro21 (talk) 18:29, 22 February 2025 (UTC)[reply]

@Maro21: I don't see any logical reason for why it's like that, no. Feel free to reorganize it so everything sorts by letter instead of * if you want! Jon Harald Søby (talk) 15:29, 25 February 2025 (UTC)[reply]

Proposal to change nl to informal tense, revisited

References:

In June 2024, the community discussed the possibility of transitioning Dutch translations to use informal language as the default, citing societal trends (formal 'u' being increasingly perceived as archaic), current linguistic norms, inconsistenties in translations within projects, and practical challenges using the {{#FORMAL}} magic word. See the discussion linked above. Despite general support for the proposal, no action was taken at that time. I would like to revisit that discussion.

The proposal is to adopt nl-informal as the default variant; to semi-automatically (with human oversight) move current nl-informal translations to nl, overwriting the latter; to deprecate nl-informal; and to introduce nl-formal as an optional secondary variant. Portal:Nl/Richtlijnen and other documentation should be updated accordingly.

I have invited the Dutch Wikipedia community to share their thoughts on this proposal.

Ping: McDutchie, Romaine, Sjoerddebruin, Vistaus, Mainframe98, Robin van der Vliet. Jeroen N (talk) 12:26, 28 January 2025 (UTC)[reply]

I support this request. Using "U" is not what I expect from a project like Wikipedia and related. Mbch331 (talk) 12:56, 28 January 2025 (UTC)[reply]
Strong support. Even banks now address their customers in the informal. The formal default wasn't appropriate for the wiki culture two decades ago, and is less so now. We need to make the informal form of address the default and stop looking like dinosaurs or tax authorities (but I repeat myself). McDutchie (discussion) 13:57, 28 January 2025 (UTC)[reply]
As long as there'll be a nl-formal, I'm happy to support this proposal. —Mainframe98 talk 15:36, 28 January 2025 (UTC)[reply]
Support. In common language "je" is the normal form. In formal language "u" is the normal form, but often perceived archaic. In most system messages already "je" is used and not "u". Practically: Most maintenance to system messages goes to the ones with language code "nl" and often system messages with language code "nl-informal" are forgotten and those can be outdated. Overriding the system messages in "nl" with "nl-informal" will be not a good idea as then outdated system messages can be implemented. This needs to be done manually or semi-automatically, and I am used to do bulk requests like these, so I am happy to work on this. Romaine (talk) 20:22, 28 January 2025 (UTC)[reply]
They are not outdated any more. I've updated all the outdated messages, so they are ready to be moved over. McDutchie (discussion) 00:11, 29 January 2025 (UTC)[reply]
I am wondering how you did do that. Also I would like to know how you catched all outdated messages. Still I am not feeling much for just overriding system messages with language code "nl" by "nl-informal", also because all the system messages with language code "nl" are much often used and seen and therefore more often corrected when spelling/language mistakes have been made as well as inconsistencies. In the past decade the Dutch community has in various occasions indicated to be annoyed by such issues, so avoiding that is seems to me a very good idea. Romaine (talk) 13:39, 29 January 2025 (UTC)[reply]
By fixing the messages marked as outdated and proofreading everything else. McDutchie (discussion) 17:35, 29 January 2025 (UTC)[reply]
I'm in support of this proposal. One minor thing to point out is that informal address is much more common in The Netherlands (18 million speakers) than it is in other parts where Dutch is spoken. I'm thinking of Belgium (6 million speakers), Suriname (roughly 400k?) and the Dutch part of the Leeward Antilles (fewer than 300k?). A few opinions from Belgium in particular would be welcome. Frank Geerlings (talk) 21:26, 28 January 2025 (UTC)[reply]
Comment: I have renewed the request for input from contributors to the Dutch Wikipedia, to make sure that we cannot be accused of not giving enough opportunity for the community to voice their opinions on the proposal. Jeroen N (talk) 11:19, 19 February 2025 (UTC)[reply]
Support for informal language usage, especially on translatable pages for for instance the Gender Gap this has been a major annoyance of mine. Exceptions should be made for fundraising related pages though. Asking for money is a big thing, and one should use formal address there. Ciell (talk) 20:23, 19 February 2025 (UTC)[reply]
Also ping for @HanV for visibility and fyi. Ciell (talk) 20:55, 19 February 2025 (UTC)[reply]
In fact, the MediaWiki people maintaining the donation system insist that the informal form should be used to ask for donations, even in the nl locale that currently uses formal. My corrections to change it to formal were reverted. This was the last straw that prompted me to propose changing nl to the informal. McDutchie (discussion) 22:59, 19 February 2025 (UTC)[reply]
Interesting, thanks for the insight. Ciell (talk) 07:35, 20 February 2025 (UTC)[reply]

Is it possible to require Chinese translator to read Portal:Zh/Translation_guidelines before they can contribute?

We have come across some situations where a newcomer submitted problematic translations without knowledge of Portal:Zh/Translation_guidelines. Is it possible to require Chinese translator to read Portal:Zh/Translation_guidelines before they can contribute? Diskdance (talk) 08:46, 29 January 2025 (UTC)[reply]

@Diskdance: We don't have any technical capability to do this, no.
My suggestion would be to build a bot that can ask new users who translate into Chinese to read the page, and ask them acknowledge that they have read and understood it somehow (maybe a list of signatures on the page itself, or its talk page?). Jon Harald Søby (talk) 15:25, 25 February 2025 (UTC)[reply]

Wikimedia:Portals-language-name/sr-ec

Smal с insted capital С

Regards Milicevic01 (talk) 16:25, 8 February 2025 (UTC)[reply]

All the language names in the Portals are written with capital letters, even if the grammar doesn't require it. Amir E. Aharoni (talk) 16:49, 8 February 2025 (UTC)[reply]
My mistake Milicevic01 (talk) 18:17, 8 February 2025 (UTC)[reply]

username change

hellooo!! :3

can you change my username to Əkrəm? thanks in advance!! :3 əkrəm. 18:55, 10 February 2025 (UTC)[reply]

Done Done. Amir E. Aharoni (talk) 19:54, 10 February 2025 (UTC)[reply]

Limits on amounts of translation entries?

Hi, are there any hardcoded limits for how many keys you can translate per minute? I do 4-5 in a row, it marks them as translated, then it starts to show "Unpublished", after that I have to wait for a minute or so before I can proceed again. I understand it is to prevent spam, but it is extremely frustrating. I just want to bomb it and do couple of hundred keys in one go, not do four, get angry, wait, do other four, get mad, wait, and so on and on... Is there a way I can change that? Czech translation of Bluespice needs a lot of love, but how am I supposed to translate so many entries effectively? Allow an enthusiast to contribute without losing mind (and interest)!

Anyways, rant over. Thanks in advance for any help/advice. Jrobicek (talk) 15:52, 12 February 2025 (UTC)[reply]

@Jrobicek: It is because your user account is new. When it reaches a certain age*, you will get a much higher rate limit (currently 8 edits/minute for you, the limit will be raised to 90 edits/minute).
* From my investigations, this limit is 14 days, though that seems quite high to me. Also, I (as an administrator) cannot override this for a certain user, which I can in Wikimedia wikis (by adding them to the "Confirmed users" group). Maybe @Nike can provide some guidance here. Jon Harald Søby (talk) 08:36, 13 February 2025 (UTC)[reply]
Thanks for looking into it, @Jon Harald Søby! It seems like I am still on 4 edits a minute, just tried. But anyways, if the only thing I need to to is to wait for two weeks to get these restrictions removed, then so be it. Lets see what @Nike says. Worst case, I will just come back later. In any case your help is much appreciated! Jrobicek (talk) 09:08, 13 February 2025 (UTC)[reply]
@Jrobicek: Your problem uncovered a bug that I've been trying to help untangle today (the limit is supposed to be 8 edits/minute, but something makes every edit count twice, so it is effectively only 4). But regardless of that bug, I think we should raise the rate limit here in translatewiki.net, so I filed a task and submitted a patch to increase the limit, so hopefully we will have this solved before 14 days. :-) Jon Harald Søby (talk) 23:20, 13 February 2025 (UTC)[reply]
You are a gentleman and a scholar, @Jon Harald Søby! Thanks a lot! Jrobicek (talk) 08:43, 14 February 2025 (UTC)[reply]
@Jrobicek: 😊 The patch to increase the limit for new accounts was merged yesterday, so hopefully you won't run into these rate limits any more! Jon Harald Søby (talk) 15:24, 15 February 2025 (UTC)[reply]

Does translatewiki joined the LQT remove programme?

Mediawiki is currently removing Flow and LQT in all wikis. The programme consists of moving boards to subpages, setting them to read-only, convert the LQT pages into wikitext, and finally completely remove the extension from the wiki. It seems there is no existing plan for translatewiki. Will the local wiki joined this programme? If not, will translatewiki do the same thing as mediawiki does? 阿南之人 (talk) 11:51, 16 February 2025 (UTC)[reply]

See for example https://phabricator.wikimedia.org/T332104#10413640. Looks like the developers are not going to provide a migration path that makes sense to us. This will likely lead us to situation where we have to suddenly undeploy LQT at some point because it stops working completely, losing access to old conversations. Nike (talk) 12:17, 16 February 2025 (UTC)[reply]
@Nike: Well, he wrote a very crude liquidthreads->wikitext converter at https://public-paws.wmcloud.org/46222050/WMF%20Cleanup/LQTW.ipynb. You may use this. 阿南之人 (talk) 12:39, 16 February 2025 (UTC)[reply]
It looks like at least in theory the LQT->Flow maintenance script can convert LQT pages from a remote wiki using the LiquidThreads API (although the code that does that is scarily labeled "This is *only* for use in testing, not production"), so in theory one could install Flow on a temporary test wiki, run that script there, and then run my export with history script to produce XML which can then be imported. I may get around to playing around with this idea sometime, but probably not for a very long time. Pppery (talk) 17:26, 19 February 2025 (UTC)[reply]
@Pppery Well, English Wikinews, English Wiktionary and Hungarian Wikipedia are all struggling with the same problem. You may take a look at them. 阿南之人 (talk) 04:36, 22 February 2025 (UTC)[reply]
My plan is to let the WMF install Flow there and convert to Flow, and then convert to wikitext from that. Pppery (talk) 16:52, 5 March 2025 (UTC)[reply]

What's up with MediaWiki:Wikimedia-license-links? I can find it on search and Special:Translate ([1]) and but I can't save a translations. It does have translations in many languages (e.g. en, et) and but the main message gives a red link and nothing comes up on the deletion log. It is used on Discussion Tools and Structured Discussions, and now I get the English message displayed on wikis instead of Finnish. Samoasambia ✎ 18:47, 18 February 2025 (UTC)[reply]

The link "in other languages" results into an error: "Fatal exception error of the type “TypeError”" Raymond 20:41, 18 February 2025 (UTC)[reply]
It was a database inconsistency. Fixed now with details in https://phabricator.wikimedia.org/T386803. Nike (talk) 11:56, 19 February 2025 (UTC)[reply]
Thanks! Samoasambia ✎ 13:01, 19 February 2025 (UTC)[reply]

Changing wp/cop/ Main page title

The title currently used in Coptic Incubator is ⲡϣⲉⲣⲡϩⲟ which is a very tricky and i'd say ungrammatical choice. It should either be ⲡϣⲉⲣⲡⲛ̀ϩⲟ but it's still quite far fetched with the literal meaning of "the early page". I'd suggest using a "safe" option, directly translating the English term - ⲡϩⲟ ⲛ̀ϩⲟⲩⲓⲧ "the first, main page". Bloomaround (talk) 12:16, 19 February 2025 (UTC)[reply]

Done Done, please check. Amir E. Aharoni (talk) 12:53, 23 February 2025 (UTC)[reply]

Colors of translations

I can see that you changed today colors of translations. Yesterday translated messages had grey background and untranslated ones white. Today they have the same color on my screen. Is there any way to change the colors back? maro21 (talk) 23:43, 19 February 2025 (UTC)[reply]

@Maro21: Hi! They are still gray, but a lighter gray than before. I have submitted gerrit:1121307 to make them a bit darker (about the same as before). Jon Harald Søby (talk) 09:11, 20 February 2025 (UTC)[reply]
Thanks! I hope they'll fix it. maro21 (talk) 18:24, 22 February 2025 (UTC)[reply]

Removing "old" threads

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

Request for translatewiki

I would like to request the link of the Margi language on TranslateWiki. Galdiz (talk) 04:28, 1 March 2025 (UTC)[reply]

As for the language name, if it is used as a short name, it will easily cause others to misunderstand, and in the future, the literature may be damaged. If use တႆး for the language name, it can have different meanings. Shan and Mon people use their ethnic names by abbreviations, but these abbreviations should not be used in literary writing. if ၽႃႇသႃႇတႆး is used in a literary context, it can only have one meaning, thanks--𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 12:32, 2 March 2025 (UTC)[reply]

With which thing can တႆး be confused? Amir E. Aharoni (talk) 12:50, 2 March 2025 (UTC)[reply]
@Amire80 okay, I will explain it as best I can so you can understand. if use the name တႆး for the Shan language, it no longer means the Shan nation, but also includes thirty-four other ethnic groups (example: ethnic groups such as the Tai Nuea (tdd), Tai Daeng (tyr), Tai Dón (twh) also call themselves တႆး (Tai) by their acronym), The real name of the Shan people is တႆးလူင်, for the Shan language, the name တႆးလူင် is not complicated, but it is a bit more appropriate. the name တႆး (Tai) in Shan language has many complications that make it difficult for people to understand. if name the Shan language ၽႃႇသႃႇတႆးလူင်, it would be very appropriate for a language name. if name it ၽႃႇသႃႇတႆးလူင် for the Shan language, it will be easier for people to understand and will also be very beneficial for literature. I've explained this much, I hope you understand. 𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 02:36, 3 March 2025 (UTC)[reply]
Retrieved from "https://translatewiki.net/w/i.php?title=Support&oldid=12962353"