Project:Village Pump

Currently, the page translation target language configuration on mediawiki.org 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 mediawiki.org 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://www.wikifunctions.org/wiki/Special:Translate?group=page-Template%3AMain+page&action=page&language=zh-hans&filter=
• https://www.wikifunctions.org/wiki/Special:Translate?group=page-Template%3AMain+page&action=page&language=zh-hant&filter=
• https://www.wikifunctions.org/wiki/Special:Translate?group=page-Template%3AMain+page&action=page&language=zh-hk&filter=
• 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://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&action=page&language=zh-hk&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=
• https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&action=page&language=zh-hk&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).

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

-- Winston Sung (talk) 08:02, 30 July 2025 (UTC) Reply

Pinging @Aaron Liu @Anterdc99 @AromaTake @Cookai1205 @Diskdance @Lakejason0 @LowensteinYang @MilkyDefer @SolidBlock @Stang @Xiplus @魔琴 -- Winston Sung (talk) 15:02, 2 August 2025 (UTC) Reply

I've added my comments on the associated Phabricator task you linked, which is basically about doing the same thing on every multilingual wiki. TL;DR: I'm opposed because as it currently stands, this proposal would quadruple the work of translators. Aaron Liu (talk) 16:18, 2 August 2025 (UTC) Reply

I'd say rather than doing this, we sort of finding a way to actually implement the NoteTA (manual conversion RULES, so not quadrupling the work but actively using the LC model) for content page. -- Lakejason0 (talk) 17:03, 2 August 2025 (UTC)(edited at 17:05, 2 August 2025 (UTC))Reply

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()

-- Winston Sung (talk) 04:44, 5 August 2025 (UTC) Reply

This is a problem, but more one for something like T196501 or something else that allows for fetching the current page variant under Lua. Aaron Liu (talk) 22:33, 6 August 2025 (UTC) Reply

Even if T196501 is solved, you still have no way to either get the requested language tag or pass the lang_tag parameter because we are currently using 1ドル instead of {{{lang|}}}, which make the message bundle messages to be something different like {{{lang|1ドル}}}. -- Winston Sung (talk) 08:41, 8 August 2025 (UTC) Reply

I don't think I understand. As long as lang is set to the needed value somewhere, it should work if we can get all the parent frames, even if it is input by the parser. Aaron Liu (talk) 21:42, 9 August 2025 (UTC) Reply

There might be some misunderstandings.

You can only get "template arguments" like {{{1|}}} after T196501 being solved so we no longer need to write {{LC zh|lang = {{{lang|}}}|

However, "system message arguments"/"interface message arguments" like 1ドル are never something can be get from frame:getParent().args without either creating new methods to the frame object or still writing {{LC zh|lang = 1ドル| in Wikitext.

:t(message_key):params(lang_tag) use the "system message argument API" instead of "template argument API".

-- Winston Sung (talk) 13:06, 11 August 2025 (UTC) Reply

Future timestamp to prevent automatic archive to unresolved discusstion topic. -- Winston Sung (talk) 00:00, 1 January 2026 (UTC) Reply

Currently, the floated image is taking the page title's place, causing it to be shifted to the right (Legacy Vector). Please add {{clear}}. Thanks. NguoiDungKhongDinhDanh 13:34, 30 October 2025 (UTC) Reply

I tried {{clear}} and adding

clear:both;

to the div, but it seems not to have any effect. —Mainframe98 _talk 18:35, 30 October 2025 (UTC) Reply

@Mainframe98: {{clear}} needs to be placed right before ‎</div>. NguoiDungKhongDinhDanh 20:50, 30 October 2025 (UTC) Reply

There's a more elegant solution: Add overflow: hidden; to the style element of the div. It makes the div grow to contain all floating elements. Ciencia Al Poder (talk) 21:02, 30 October 2025 (UTC) Reply

Closing as nothing to do atm. Hide on Rosé (talk) 10:59, 7 November 2025 (UTC) Reply

Each year, typically from October through December, several of the movement’s committees seek new volunteers.

Read more about the committees on their Meta-wiki pages:

• Affiliations Committee (AffCom)
• Ombuds commission (OC)
• Case Review Committee (CRC)

Applications for the committees open on October 30, 2025. Applications for the Affiliations Committee, Ombuds commission and the Case Review Committee close on December 11, 2025. Learn how to apply by visiting the appointment page on Meta-wiki. Post to the talk page or email cst(_AT_)wikimedia.org with any questions you may have.

For the Committee Support team,

- MKaur (WMF) 14:12, 30 October 2025 (UTC) Reply

• MediaWiki.org website

• Languages pages