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".
There's not much point in reporting accounts with zero edits to the local admins here absent some reason to think they will specifically target MediaWiki.org. Just report to the stewards and move on.* Pppery *it has begun15:57, 14 October 2025 (UTC)Reply
I've deleted the translation units they created. There are some modifications in existing units that, looking more closely, seem to be better (but mind you I don't know Galician language, only because it's close to Spanish). You may want to take a look at those.Ciencia Al Poder (talk)18:03, 19 October 2025 (UTC)Reply
Report concerning User:((Uw-uhblock)) --Username violation, hard block--
Latest comment:7 days ago1 comment1 person in discussion
Hello. Please help pick a name for the new Abstract Wikipedia wiki project. This project will be a wiki that will enable users to combine functions fromWikifunctions and data from Wikidata in order to generate natural language sentences in any supported languages. These sentences can then be used by any Wikipedia (or elsewhere).
There will be two rounds of voting, each followed by legal review of candidates, with votes beginning on 20 October and 17 November 2025. Our goal is to have a final project name selected on mid-December 2025. If you would like to participate, thenplease learn more and vote now at meta-wiki.Thank you!
Latest comment:7 days ago1 comment1 person in discussion
What I can say here is that I'm seeingSpecial:LintErrors/duplicate-ids having so many lists. Mostly from other languages that useTranslate extension. I'm not sure if somebody has already filed out this track on Phabricator.
Theid attributes in other language pages are just making them same while English one doesn't (it starts with "sectionname_number"). I hope this issue gets fixed. —Baris6161TURK (talk)21:29, 20 October 2025 (UTC)Reply
