Support

please update translation for MediaWiki:Nstab-mainpage/pa from ਮੁੱਖ ਪੰਨਾ to ਮੁੱਖ ਸਫ਼ਾ. thanks! KuldeepBurjBhalaike ^(Talk) 11:29, 4 August 2024 (UTC)[reply]

Was there a discussion about it with other people who edit in Punjabi? Amir E. Aharoni (talk) 20:25, 10 August 2024 (UTC)[reply]

No, but for all other wiki projects we are using ਮੁੱਖ ਸਫ਼ਾ KuldeepBurjBhalaike ^(Talk) 07:04, 20 August 2024 (UTC)[reply]

I see ਮੁੱਖ ਪੰਨਾ on https://pa.wiktionary.org at the moment :) Amir E. Aharoni (talk) 17:02, 20 August 2024 (UTC)[reply]

@Kuldeepburjbhalaike I would support this change, it would be good to get feedback from other pawiki users as well. Bgo eiu (talk) 12:50, 21 August 2024 (UTC)[reply]

on translatewiki or any other punjabi wiki project? KuldeepBurjBhalaike ^(Talk) 13:07, 24 August 2024 (UTC)[reply]

Other projects :) Amir E. Aharoni (talk) 19:47, 24 August 2024 (UTC)[reply]

TL;DR: Can anyone think of an easy way to review new and old English messages?

Details: Over the last twelve years or so, I met a few potential contributors who know English well and who may have good suggestions to improve the wording of English messages.

Many English messages have issues: inconsistencies, spelling and punctuation errors, ambiguity, lack of clarity, etc. This happens even though at least some of them are written by professional designers and product managers. It's ok—everyone makes mistakes, and correcting each other is literally what wiki editors do.

I translate all the new MediaWiki messages into Hebrew (or review all other people's translations), and it has a side effect of reviewing all the new English messages (and often many old ones). Because of that, I quite often suggest improvements in English messages myself. Quite often, they are accepted. However, I'm not a native English speaker. It is not necessarily a problem, but I'm also not a professional English editor, and I met several people who are professional English editors and who want to make this kind of contribution!

And in general, it's always better if it's done by multiple people: reducing bus factor and bias, being more efficient, etc.

By "easy" I mean:

• Web-based, without having to deal with files. (Although it doesn't have to be on translatewiki.net itself.)
• Not having to deal with Git or Gerrit. Setting up a notification to go over Gerrit changes that involve en.json files could theoretically work. However, there are people who can review English text, but are very scared of Git. Knowing Git and diffs is a useful skill to have, but it's too much for some people, and I don't want to give up on their potential contributions.

There's "Recent additions", but it shows all projects, which is overwhelming. I thought of hacks like going over British English, but I don't totally like it—a lot of them are identical to "en" and I'm not a fan of just creating copies.

So can anyone think of an existing way to do it, within translatewiki or with something external?

One last random thought: If there's nothing else, perhaps we could allow something like the review action for the source language? Amir E. Aharoni (talk) 23:37, 6 August 2024 (UTC)[reply]

• The RSS feed https://translatewiki.net/w/api.php?action=feedcontributions&user=FuzzyBot&namespace=8 gives all recent FuzzyBot edits in the MediaWiki namespace (including message documentation and eventual other languages). This is very rough, but it already exists. You can control the namespace by manually editing the URL parameter; one feed can only yield edits in one namespace (or all namespaces), for two namespaces, you need two feed URLs (but hopefully your feed reader can aggregate them).
• The new message group subscription feature is, as far as I know, language-agnostic, so you can get notifications even if you don’t actually translate. However, the notifications don’t indicate what messages were added (only the number of them), so unless you have a language with less than a few dozens of missing translations, it’s pretty difficult to find out what changed. (This actually bothers me as well as a real translator, so maybe could be changed?) Also, there are no notifications yet about updated messages.
• Based on the contributions list of FuzzyBot, it should be possible to build a Toolforge tool that generates an RSS feed fulfilling all requirements (only English messages, filtering by message group rather than just namespace, as many or few message groups in one feed as you want). If it builds upon the contributions list, the scary Git interface is not a problem, since it can only ever link to translatewiki.net (since sadly there’s no direct connection between Git commits and translatewiki.net edits). The tool could also send emails, but that’s more difficult because emails need a database to store subscriptions and the user logging in; I don’t even know if it’s possible and/or permissible to allow users to log in using translatewiki.net accounts (as opposed to WMF accounts).

Tacsipacsi (talk) 19:07, 11 August 2024 (UTC)[reply]

Hi,

Could you please add the Nguiemboon language from Cameroon. The language code is nnh. 

Thanks. Serieminou (talk) 15:13, 7 August 2024 (UTC)[reply]

 Done Amir E. Aharoni (talk) 21:35, 9 August 2024 (UTC)[reply]

Thank you! Serieminou (talk) 19:11, 2 September 2024 (UTC)[reply]

Greetings. Could you please add Duala language fro Cameroon. The language code is dua . Thank you in advance. Serieminou (talk) 22:50, 8 August 2024 (UTC)[reply]

 Done Amir E. Aharoni (talk) 11:13, 15 August 2024 (UTC)[reply]

Thank you very much. Serieminou (talk) 19:11, 2 September 2024 (UTC)[reply]

while I was checking my old translations at most important messages, I reached the "Main menu" message (the one with a red warning at documentation), when I changed it to a better translation, it refused because the message is "highly visible". I want to update the message now. MRidhaAJ (talk) 14:10, 13 August 2024 (UTC)[reply]

I can fix it for you. What should it be? Amir E. Aharoni (talk) 14:17, 13 August 2024 (UTC)[reply]

Actually, which message are you talking about? "Main menu" is this message, and as far as I can see, it's not protected. Amir E. Aharoni (talk) 14:22, 13 August 2024 (UTC)[reply]

It's not from Vector group, It's from mediawiki most important messages like what I said before. MRidhaAJ (talk) 14:26, 13 August 2024 (UTC)[reply]

The same message appears in both groups. Can you please give a direct link? Amir E. Aharoni (talk) 15:54, 13 August 2024 (UTC)[reply]

See it. MRidhaAJ (talk) 15:59, 13 August 2024 (UTC)[reply]

Thanks. It says "Main page", not "Main menu". What translation do you suggest? Amir E. Aharoni (talk) 16:12, 13 August 2024 (UTC)[reply]

I suggest of "الصفحه الرئيسيه" (not with the ""). MRidhaAJ (talk) 08:30, 15 August 2024 (UTC)[reply]

 Done Amir E. Aharoni (talk) 11:19, 15 August 2024 (UTC)[reply]

This user is translating into multiple languages. Their translation for Translations:Template:Optional/1/az is wrong, I am not sure about other languages. Nemoralis (talk) 10:55, 14 August 2024 (UTC)[reply]

I removed this user's translation permissions. Thank you for the notification. Amir E. Aharoni (talk) 14:50, 19 August 2024 (UTC)[reply]

Thank you @Amire80. Can you restore Translations:Template:Optional/1/az? I already fixed it. Nemoralis (talk) 14:56, 19 August 2024 (UTC)[reply]

Nevermind. Nemoralis (talk) 15:00, 19 August 2024 (UTC)[reply]

Greetings,

Translatable pages allow contents such as project documentation on Mediawiki.org to be multilingual. Currently a flat list with all languages in which the content is available is listed above the page contents. As the content is translated into more languages, this makes it hard for users to find the content in their language (they have to scan a long list or rely on the browser search), clutters the page, and pushes the content down.

To address this issue, the Language and Product Localization team is implementing a change to use the Language selector from ULS for language selection on Vector 2022. This aims to ensure consistency with the way languages are selected on other projects, such as Wikipedia.

Specifically, the configuration option ($wgPageTranslationLanguageList = 'sidebar-only';) that we are planning to use would display languages as interlanguage links only and ignore the tag even if present on the page. You can see this in action on translatewiki.net:

1. Vector 2022: https://translatewiki.net/wiki/Project:About?useskin=vector-2022
2. Timeless: https://translatewiki.net/wiki/Project:About?useskin=timeless
3. Vector legacy: https://translatewiki.net/wiki/Project:About?useskin=vector  

We’re planning to enable this on Test Wikipedia first, and then roll-out on all wikis where Translate extension is enabled based on community feedback. Feel free to leave your feedback here, or on the Phabricator task.

FAQ

Q: Why are we making this change?

A: Currently a flat list of all languages to which the page is translated is displayed at the top of page contents. As the content is translated into more languages, this makes it hard for users to find the content in their language (they have to scan a long list or rely on the browser search), clutters the page, and pushes the content down. Using the Language selector from ULS, makes the available language list searchable and clears up the top of the page to display the actual content. It also brings uniformity to how content language selection is done across our sites.

Q: Will I still be able to see the translation progress for each language?

A: Yes, translation statistics for each language will be displayed within circles in the same manner that it is displayed currently. The special page Special:MessageGroupStats can also be used to view per language translation statistics.

Q: Where can I see this in action?

A: This change is already active on translatewiki.net. You can see it in action there:

1. Vector 2022: https://translatewiki.net/wiki/Project:About?useskin=vector-2022
2. Timeless: https://translatewiki.net/wiki/Project:About?useskin=timeless
3. Vector legacy: https://translatewiki.net/wiki/Project:About?useskin=vector

Q: How will this change affect the ULS for other projects like Wikipedia? Currently, the ULS in Wikipedia shows and links to Wikipedias that have the translated version of the same article in other languages. How will this new workflow affect the Wikipedia User Interface?

A: This change will not have any impact on projects that do not use the Translate extension and as such Wikipedia and its sister sites will not be impacted.

Q: This new ULS menu design shows 20 languages before scrolling. Does it mean I have to scroll and skim through maybe 90 languages to access my language if it is the last on the list?

A: No, you won't have to scroll all the way. You can type the two or three letters of your language in the Universal Language Selector for the search to fetch your language translation.

In addition, the Universal Language Selector uses different techniques to determine which languages will be most relevant to you, and displays those at the top.

Q: What is the roll-out plan?

A: We’re planning to enable this on Test Wikipedia first, followed by MediaWiki.org and then roll-out on all wikis where the Translate extension is enabled.

Thanks! Abijeet Patro (talk) 13:16, 14 August 2024 (UTC)[reply]

Looks nice!

But what about the edge case of language-specific wikis that have the Translate extension enabled, like frwiktionary and ptwikisource (those are the only two I find)? Jon Harald Søby (talk) 13:54, 14 August 2024 (UTC)[reply]

Actually (and as far as I remember, I’ve already said this a few times), it’s quite not an edge case. mw:translatewiki.net has interlanguage links, m:Wikimedia Foundation has interlanguage links, c:Help:Automatic edit summary has interlanguage links, s:mul:Wikisource:WS Export has interlanguage links, and I could probably list dozens more if I ran an SQL query. Putting translation links to the interlanguage links is simply not a good solution on wikis that can have genuine interlanguage links – and all WMF wikis are such. —Tacsipacsi (talk) 19:35, 14 August 2024 (UTC)[reply]

Thanks for your feedback, Jon.

I was not aware of this use case. This will have to be handled differently, not something that I had considered. I'll check with team.

Regards, Abijeet Patro (talk) 09:40, 16 August 2024 (UTC)[reply]

As I translate a lot on Wikimedia Commons it is currently very useful to see the translation status of German directly on the page. Now I need one click more to see the status, is this right? I would prefer to see the translation status of at least my user language, maybe my babel languages too, directly. Raymond 16:34, 14 August 2024 (UTC)[reply]

Thanks for your feedback. You are right. You'll have to click on the language selector to see the translation statistics for your preferred language.

> I would prefer to see the translation status of at least my user language, maybe my babel languages too, directly.

Acknowledged.

Regards, Abijeet Patro (talk) 09:20, 16 August 2024 (UTC)[reply]

This should be "Ana səhifə" per this consensus from 2021. Nemoralis (talk) 22:00, 14 August 2024 (UTC)[reply]

@Nemoralis:  Done Jon Harald Søby (talk) 09:20, 15 August 2024 (UTC)[reply]

Hi, could I have my username changed please? Target username: Ceirios

Thank you in advance. Afalau (talk) 15:49, 16 August 2024 (UTC)[reply]

 Done Amir E. Aharoni (talk) 16:35, 18 August 2024 (UTC)[reply]

Lovely, thank you again! Ceirios (talk) 17:27, 19 August 2024 (UTC)[reply]

Hello i am not able to login to translatewiki.net , I get

The supplied credentials could not be authenticated.

Error message when I try to login. And when try to reset password I get

The password reset was not handled. Maybe no provider was configured?

as I was already logged in from mobile device I could post this here.~aanzx ^✉_© 08:22, 19 August 2024 (UTC)[reply]

There is MediaWiki:Tag-cross-wiki-upload/en and I expect the content to appear at https://commons.wikimedia.org/wiki/MediaWiki:Tag-cross-wiki-upload . But it doesn't. MediaWiki:Tag-cross-wiki-upload-description/en seems to have the same problem. (Although for the latter, Commons customizes it.)

It looks like they were removed in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaEvents/+/788259 but I'm not sure why. whym 10:53, 20 August 2024 (UTC)[reply]

@Whym: That's not the right diff to look at, that's just L10n-bot doing its job correctly. You should look at when the message was removed from the English file, which happened in gerrit:787116. Seems they thought it was unused. Jon Harald Søby (talk) 14:47, 20 August 2024 (UTC)[reply]

Thanks a lot for the pointer. I submitted a patch to partially undo it. gerrit:1064150 whym 03:24, 21 August 2024 (UTC)[reply]

Can someone here take a look at the link above? The patch concerns interface messages only, and ready to be reviewed. whym 09:06, 28 August 2024 (UTC) EDIT: This is now merged. whym 00:04, 1 September 2024 (UTC)[reply]

I would like to change my user name to Paloi Sciurala. Thanks in advance. NGC 54 (talk) 13:10, 23 August 2024 (UTC)[reply]

 Done. Amir E. Aharoni (talk) 12:47, 27 August 2024 (UTC)[reply]

The documentation of this message contains {{optional}}, but it isn’t actually marked as such. Could someone add it to the list of optional messages before we get a sea of redundant translations? Thanks in advance! —Tacsipacsi (talk) 13:46, 24 August 2024 (UTC)[reply]

 Done.

Feel free to send a patch like this one next time. Amir E. Aharoni (talk) 22:43, 24 August 2024 (UTC)[reply]

Hi, please help add Jju language (ISO Code: kaj) for translation. I intend to lead a translation process for this language closely related to the Tyap language, beginning from September 2024. Thanks! Kambai Akau (talk) 00:58, 30 August 2024 (UTC)[reply]

Thanks for the request, we'll do it soon. Amir E. Aharoni (talk) 14:36, 30 August 2024 (UTC)[reply]

My pleasure! Thanks, too!! Kambai Akau (talk) 18:49, 30 August 2024 (UTC)[reply]

Phabricator task for tracking: https://phabricator.wikimedia.org/T373928 Amir E. Aharoni (talk) 19:28, 3 September 2024 (UTC)[reply]

 Done

This is now enabled. --Amir E. Aharoni (talk) 13:26, 4 September 2024 (UTC)[reply]

I would like to change my user name to Mohanad. Thx in advance --Mohanad Kh (talk) 12:46, 2 September 2024 (UTC)[reply]

 Done. Amir E. Aharoni (talk) 19:17, 3 September 2024 (UTC)[reply]

The purpose of the request is to have Negeri Sembilan Malay interface in Wikimedia projects especially multilingual projects like Wikidata.

English name: Negeri Sembilan Malay
Native name: Baso Nismilan
ISO 639-3 code: zmi
Directionality: LTR
Script: Latin

~ Thank you - Zahirulnukman (talk) 15:11, 2 September 2024 (UTC)[reply]

Thanks for the request!

Other than Wikipedia, are there perhaps any other places where the name "Baso Nismilan" appears, such as a dictionary or another website? Amir E. Aharoni (talk) 02:45, 3 September 2024 (UTC)[reply]

Unfortunately, I couldn't find it academically. Nismilan is short form for Negeri Sembilan.

But, the Malaysian authority (National Archive of Malaysia) use "Bahaso Nogori" for this language in a formal and academic event, which appeared in this Instagram post. For informal way, many use "Loghat Nogori". So, maybe can use "Bahaso Nogori" instead. - Zahirulnukman (talk) 03:03, 3 September 2024 (UTC)[reply]

 Done This is now enabled. I recommend using the list called "Links for Negeri Sembilan Malay" on your user page to translate. Thank you and good luck! --Amir E. Aharoni (talk) 13:26, 4 September 2024 (UTC)[reply]

There needs to be some changes for [crh-ro] Dobrujan Tatar

• The background language Romanian is better to be removed (confusing and orthography problem)
• And, as requested actually, Cyrillic script needs to added

→ code: crh-cyrl-ro

→ native name: татарша

→ name: Dobrujan Tatar (Cyrillic script)

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

https://commons.wikimedia.org/wiki/Commons:Vicu%C3%B1aUploader points to https://github.com/exander77/vicuna rather than https://github.com/yarl/vicuna and also says `This branch is 21 commits ahead of, 89 commits behind yarl/vicuna:master.`

Oct 31, 2021 is the last commit to the canonical, May 3, 2022 for the fork.

It does seem it still works, but does seem somewhat abandoned on both upstreams... Reedy (talk) 23:48, 9 September 2024 (UTC)[reply]

(Really sorry for abandoning the topic. I may have dismissed the notification and then forgotten about it.)

Replying to @Amire80:

> Why is it necessary for Hindi? I realize that it is hard for some people to type in Devanagari, but is it hard to read?
The answer is yes. In fact, Devanagari being hard to read is probably one of the major factors driving users away from using Hindi as their locale.

Also, since hi-hinglish was disqualified for not having a valid ISO code among others, the next best alternative is hi-Latn which is listed on Unicode CLDR. My understanding is that only the language variant policies would apply to it, in which case it satisfies the first condition. ~Saurmandal 20:59 15:29, 10 September 2024 (UTC)[reply]