Jump to content

Project:Village Pump

Add topic
From mediawiki.org
This page is only for discussing issues related to MediaWiki.org site.
To get help with MediaWiki software, ask on Project:Support desk.

Change to translatewiki.net/Miraheze-Meta page translation target languages

[edit]

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.

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

Main page styles

[edit]

Following the MediaWiki update to the parsed heading structure, the main page CSS should be updated accordingly - MediaWiki:Common.css#L-37. Thanks.
Replace:

[lang="en"] .page-MediaWiki .mw-parser-output h2 {
	display: none; 
}

With:

[lang="en"] .page-MediaWiki .mw-parser-output .mw-heading2 {
	display: none; 
}

Serhio Magpie (talk) 12:30, 20 November 2025 (UTC)Reply

I can't figure out what this styling is supposed to do. Could you please explain why this should be done, and provide a test case that is currently broken and would be fixed were this change made? @Serhio Magpie: * Pppery * it has begun 03:25, 28 November 2025 (UTC)Reply
These styles hide the first heading in the content that duplicates the page title on the main page. My proposed fix: instead of hiding the h2 element itself (which worked previously), it targets the h2's container element.
Example without styles (see identical headers):
Example with proposed fix:
Serhio Magpie (talk) 03:56, 28 November 2025 (UTC)Reply
I can't reproduce that at all. For me viewing MediaWiki only shows the header once. * Pppery * it has begun 04:00, 28 November 2025 (UTC)Reply
There's an extra separator left over after hiding the heading. Sorry for not being more clear.
Before:
After:
Serhio Magpie (talk) 04:05, 28 November 2025 (UTC)Reply
FWIW, I can't see the duplicate heading either but I do see the extra separator that shouldn't be there, using Firefox if that's of any relevance. Tactica (talk) 04:42, 28 November 2025 (UTC)Reply
Ok, done. * Pppery * it has begun 00:14, 29 November 2025 (UTC)Reply

Reminder: Help us decide the name of the new Abstract Wikipedia project

[edit]

Hello. Reminder: Please help to choose name for the new Abstract Wikipedia wiki project. The finalist vote starts today. The finalists for the name are: Abstract Wikipedia, Multilingual Wikipedia, Wikiabstracts, Wikigenerator, Proto-Wiki. If you would like to participate, then please learn more and vote now at meta-wiki. Thank you!


-- User:Sannita (WMF) (talk) 14:21, 20 November 2025 (UTC)Reply

Blocked IP during development

[edit]

During development of Wikispeech, I was testing directly to our page: Extension:Wikispeech/Pronunciation errors/sv and unfortunately, my IP-address became blocked due to "vandalism". I am fairly new in this eco system, but I was wondering if it perhaps could be possible to cancel the blocking of my IP-adress? Ofcourse I understand now, that I should have used the /sandbox for testing against wikis, but now I know better, but it would be great if the blocking could be cancelled.

Blocking: Special:BlockList IP-address

The page that I was blocked from: Pronunciation errors/sv: Revision history

Kind regards, Viktoria Hillerud (WMSE) (talk) 08:05, 25 November 2025 (UTC)Reply

Pinging @Clump as the blocking admin. NguoiDungKhongDinhDanh 09:21, 25 November 2025 (UTC)Reply
It is best to ask @Clump, as he added the block. However. if you are making anonymous edits without edit summaries (like "I'm testing this new vandalism"), then it is likely you will get blocked indeed, so try to improve on that. You can also use test.wikipedia.org —TheDJ (Not WMF) (talkcontribs) 09:21, 25 November 2025 (UTC)Reply
Thanks! That is great tips, thankyou! Viktoria Hillerud (WMSE) (talk) 11:07, 25 November 2025 (UTC)Reply
Unblocked; sorry about that---testing and nonsense edits tend to look similar, :) and yes, edit comments would help and be appreciated. --Clump (talk) 12:07, 25 November 2025 (UTC)Reply
Thankyou! In the future I will sure use edit comments :) Viktoria Hillerud (WMSE) (talk) 12:09, 25 November 2025 (UTC)Reply