However, this actually created several problems including the broken page transclutions with malfunctioned language converter tags exposed and using the workaround ofTemplate:Conversion-zh,Template:LC zh. More breakages could be found onphab:T328838.
More briefly for thezh part: The old configuration can only translate intozh while the new configuration can translate intozh-hans (forzh-Hans-CN,zh-Hans-MY,zh-Hans-SG),zh-hant (forzh-Hant-TW) andzh-hk (forzh-Hant-HK,zh-Hant-MO).
Note: "translatewiki.net page translation model"/"Miraheze Meta page translation model" refer to the same translation model.
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-hktmb.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 timetmb.new(mb_page_title,lang_tag):t(message_key):plain()
With this change, every Lua module using translation bundles can be simplified:
Even ifT196501 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|}}} afterT196501 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 fromframe:getParent().args without either creating new methods to theframe 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".
The current problem is there are no way to pass template parameter (and only can pass system messsage parameter) when calling system messages. We currently have the way to get the current user interface language but there is no way to properly pass it without extra work on every template calls. --Winston Sung (talk)16:08, 15 December 2025 (UTC)Reply
Latest comment:11 days ago2 comments2 people in discussion
The two pages I link in this section's heading have been repeatedly vandalized by anons. We block one, only for it to return under a new temporary account. The likelihood of constructive edits to those pages by anons is vanishingly small IMO, so I suggest we protect them against anon editing.Mr. Starfleet Command (talk)14:35, 4 December 2025 (UTC)Reply
Latest comment:23 hours ago4 comments2 people in discussion
Howdy. Today I boldly created the articleManual:JavaScript hooks. I think it should have equal weight to the current articleManual:Hooks, which is about the PHP hooks. They're both pretty developed hook systems.
Actually it requires a sysadmin since the page consists of more than 500 translations. But I think this is premature -Manual:Hooks, as a page dating back to 2006 with hundreds of subpages and lots of template infrastructure linking to those subpages, is clearly not on an equal footing with a singular page you created today.* Pppery *it has begun04:39, 15 December 2025 (UTC)Reply
