Meta:Babel

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

Hello, this message is to notify that Chealer has been nominated for a global ban at m:Requests for comment/Global ban for Chealer. You are receiving this notification as required per the global ban policy as they have made at least 1 edit on this wiki. Thanks, --shb (t • c) 11:22, 28 July 2025 (UTC)Reply

 This section is resolved and can be archived. If you disagree, replace this template with your comment. The linked discussion closed. — xaosflux ^Talk 12:35, 17 August 2025 (UTC)Reply

Currently, the page translation target language configuration on Wikimedia Meta-Wiki were inherited from the "language converter page translation model".

However, this actually created several problems including the broken page transclutions with malfunctioned language converter tags exposed and using the workaround of Template:Conversion-zh, Template:LC zh. More breakages could be found on phab:T328838.

I would like to propose to use the "translatewiki.net page translation model"/"Miraheze Meta page translation model" instead on Meta-Wiki after the related proposal had been discussed, supported and approved and changes had been done on Wikifunctions.

Below are examples of the proposed translation model.

• https://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&action=page&language=zh-hans&filter=
• https://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&action=page&language=zh-hant&filter=
• https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&action=page&language=zh-hans&filter=
• https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&action=page&language=zh-hant&filter=

More briefly for the zh part: The old configuration can only translate into zh while the new configuration can translate into zh-hans (for zh-Hans-CN, zh-Hans-MY, zh-Hans-SG), zh-hant (for zh-Hant-TW) and zh-hk (for zh-Hant-HK, zh-Hant-MO).

Without using /zh-hans, /zh-hant, /zh-hk, we have to pass the language tag every time using message bundle messages.

-- Wrapping all of them under /zh using {{LC zh|, without using /zh-hans, /zh-hant, /zh-hk
tmb.new( mb_page_title, lang_tag ):t( message_key ):params( lang_tag ):plain()

-- Using separated /zh-hans, /zh-hant, /zh-hk, we no longer need to pass the language tag :params( lang_tag ) every time
tmb.new( mb_page_title, lang_tag ):t( message_key ):plain()

With this change, every Lua module using translation bundles can be simplified:

- :t( message_key ):params( lang_tag ):plain()
+ :t( message_key ):plain()

Without this change, every Lua module using translation bundles need to:

- :t( message_key ):plain()
+ :t( message_key ):params( lang_tag ):plain()

Note: "translatewiki.net page translation model"/"Miraheze Meta page translation model" refer to the same translation model.

-- Winston Sung (talk) 07:57, 30 July 2025 (UTC)Reply

Pinging @​94rain @​乌拉跨氪 @​梦夕琳 ​@Allenwang6212a、 @ASid @Cookai1205 @​Cwek @​Ericliu1912 @​Hamish @​Heihaheihaha @​Joycewikiwiki @​Kaganer @​KOKUYO @​Kuailong @Lakejason0 @​LowensteinYang @​Minorax @​Reke @SCP-2000 @​Shangkuanlc @​Shizhao @SolidBlock @​Stang @​SunAfterRain @​Supaplex @​Taiwania Justo @​Tigerzeng @​Venuslui @​WhitePhosphorus @​Wong128hk @​Xiplus @​YFdyh000 @人间百态 @魔琴 @​だ＊ぜ -- Winston Sung (talk) 04:24, 5 August 2025 (UTC)Reply

As I didn't look into two models, is there any major difference? If yes, would you briefly describe the difference please? Hamish 16:02, 5 August 2025 (UTC)Reply

More briefly for the zh part: The old configuration can only translate into zh while the new configuration can translate into zh-hans (for zh-Hans-CN, zh-Hans-MY, zh-Hans-SG), zh-hant (for zh-Hant-TW) and zh-hk (for zh-Hant-HK, zh-Hant-MO). -- Winston Sung (talk) 08:27, 8 August 2025 (UTC)Reply

July 2025 education newsletter released for translation. Please help our readers to read education newsletter in their native language. The latest education newsletter is ready for translation: here Newsletter headlines link for translation: here, to read individual articles check out: Category:Education/Newsletter/July 2025. Regards, ZI Jony ^(Talk) 02:56, 1 August 2025 (UTC)Reply

@ZI Jony, please also include link to Template:Education Navigation into your invitations. Kaganer (talk) 09:57, 6 August 2025 (UTC)Reply

Noted. Regards, ZI Jony ^(Talk) 16:34, 7 August 2025 (UTC)Reply

☁ Ray Butcher (talk) 09:22, 12 August 2025 (UTC)Reply

hridoy.khan57327@ 103.242.8.180 09:49, 12 August 2025 (UTC)Reply

Hi!

I need the help from a bot to apply the following algorithm:

const listOfPages = mw.getListOfPagesStartingWith( "Wiki Loves Living Heritage/" );

const replaceRegex = new RegExp(`<!--BEGINREPLACE.+<!--ENDREPLACE-->`, "s");
const backupRegex = new RegExp(`{{Wikidata list.+{{Wikidata list end}}`, "s");

for( page in listOfPages ) {
	let matchingContent = page.wikitext.match( replaceRegex );
	if( ! matchingContent ) matchingContent = page.wikitext.match( backupRegex );
	if( ! matchingContent ) continue;

	let contentToMove = matchingContent[0];
	let newSubPageName = page.pageName + '/list';
	page.wikitext.replace( contentToMove, '{{:' + newSubPageName + '}}' ); //must be absolute path (for translation pages)
	page.save();

	mw.createPage(
		pageName: newSubPageName,
		pageWikitext: contentToMove
	);
}

Aim: moving Wikidata List to their own subpage, then transcluding the subpage, so what you see do not change.

Point: many of those pages are translatable. Each time the bot update the Wikidata list, a translation admin must mark the page for translation, which is uselessly time-consuming.

Unfortunately, I have never set a bot up, and I have not enough time to learn. Can someone help?

Pinging Susannaanas for information.

-- Pols12 (talk) 14:49, 12 August 2025 (UTC)Reply

@Pols12: What wanna you? As human, simple? What is problem? You write (in Aim) how wanna you implement, but i dont know what is the problem (example, if i would be a user, a none-technical user). Dušan Kreheľ (talk) 10:46, 13 August 2025 (UTC)Reply

I explained it in the “point” item: each time a translatable page is updated, a translation admin has to “mark the page for translation” to validate the changes so they are applied to translation pages. Since those are Wikidata lists, the bot update the pages every day. This is really time-consuming for translation admins to review all of those bot changes!

Benefits:

• As a translation admin, this change would reduce my workload.
• As a final user, I see the page up-to-date in my language as soon as ListeriaBot updates the page, I don’t need to wait for translation admin work.

-- Pols12 (talk) 12:14, 13 August 2025 (UTC)Reply

@Pols12:

Solution No. 1.:

How about getting pagetranslation rights for a bot?

Solution No. 2.:

I see that the page is a bunch of mini-pages. So I would put the translation into Lua modules (the module would load the translation according to the wikis and have some constant UI for the languages).

The page would be for example: {{Page widget box|en|dog;cat;rabbit}}

The modules would be:

• Page widget box
• Page widget box – item (description pulls according to wikidata and language)
• Page widget box – UI translate

Dušan Kreheľ (talk) 13:15, 15 August 2025 (UTC)Reply

Your solution 1 is not conceivable. That action needs a special right because it needs a human review given the risks of making something wrong and for performance reasons. Besides, my solution only needs 1 bot passage ever for each page; whereas your solution 1 would need a daily passage (each time ListeriaBot edits the page) which would be uselessly resource-consuming.

I don’t understand your solution 2. I agree several unit would benefit to be included through a template since they are common to many pages. They are already some templates for that purpose, including Template:Wiki Loves Living Heritage/Placeholders. In any case, we want the page to be localizable, and the best way is to use Translate extension features, mainly for Meta-Wiki consistency. In most cases, only the page title will be manually translatable (no unit on the page), but that would enable Languages bar to change the page language.

Also, I don’t understand why you seem to want to avoid the solution I proposed.

Unfortunately, I will probably not find any more time to work more on this in the coming weeks, sorry if I can’t follow your next answers here.

--Pols12 (talk) 23:47, 16 August 2025 (UTC)Reply

When I successfully mark pages for translation, the check icon on the left side of the notice squeezed. Probably not the only instance. I don't know where to post it, so I'll leave it here. —— Eric Liu_（Talk） 15:47, 14 August 2025 (UTC)Reply

@Ericliu1912 does it appear similar to phab:T398529#11048062? Johannnes89 (talk) 13:52, 15 August 2025 (UTC)Reply

Yes! Glad to see there was already a Phab task filed. —— Eric Liu_（Talk） 14:22, 15 August 2025 (UTC)Reply

Missing message in ⧼⧼communitywishlist-support⧽⧽. Go to Community Wishlist/Focus areas/Media formats, editing, and display for example, scroll to blue button and push "Support focus area", the popup's main blue button that appears has this {{int:}} in it. Waddie96 (talk) 06:49, 17 August 2025 (UTC)Reply

• Ping to @MusikAnimal (WMF): who I think is the staffer coordinating that. MA, looks like there are 2 problems:

1. Missing label at MediaWiki:communitywishlist-support as reported above.
2. This button loads a custom pop-out editor, which is missing licensing agreement verbiage (which should be, or be functionally similar to MediaWiki:wikimedia-copyrightwarning)

• Would you look in to both of these? Thank you, — xaosflux ^Talk 12:34, 17 August 2025 (UTC)Reply