Project:Village Pump

About this board

This page is only for discussing issues related to site.
To get help with MediaWiki software, ask on Project:Support desk.
Shirayuki (talkcontribs)

The following message is not displayed on the Template:Temporary Accounts/Header/sandbox page:

This is the template sandbox page for Template:Temporary Accounts/Header (diff).
See also the companion subpage for test cases.
Pppery (talkcontribs)
Reply to "Processing of page names in Module:Documentation"
Salima Rabiu (talkcontribs)

I tried to fix a broken link on this page Professional development and consulting at an external link that goes to Yaron Koren's Working with Mediawiki book but it returned an error, please how do i fix it ?

Salima Rabiu (talkcontribs)

This has been fixed, thanks

Salima Rabiu (talkcontribs)
Wladek92 (talkcontribs)

I think after having created your account 4 days ago better is to start by learning the first steps of how to contribute.

Reply to "Broken link fix"
Bluehill (talkcontribs)

I can't translate "Developers wanting to install MediaWiki locally to have an environment for development of MediaWiki core or extensions should also read How to become a MediaWiki hacker for further instructions." from the Download page. What should I do?

Ciencia Al Poder (talkcontribs)

I've made that text translatable

(Technical) Weird behavior with PAGELANGUAGE and ifeq

Aaron Liu (talkcontribs)

Hi there, I've been trying to implement namespace-removal for {{Ll }}'s translated link names. You can see a problem at User:Aaron Liu/sandbox. The first line produces a blank, while the second line, which is just the first line's both cases substituted, produces its stuff correctly. What's wrong here?

Aidan9382 (talkcontribs)

There seems to have been an issue with the pipes in your #ifeq:, which I've fixed.

NoteTA is deprecated?

Summary last edited by Aaron Liu 11:41, 10 April 2024 11 days ago

Yes, due to improper conversion when the UI language differs from the language to convert to in certain cases such as Special:Permalink/5860177. Other reasons include the desire for translation units to be independent of each other.

Aaron Liu (talkcontribs)
Dinoguy1000 (talkcontribs)

The tracking category was added to Module:NoteTA, with only the comment "Add tracking category", by (talk · contribs) on February 25, and the same IP then created the category a few minutes later, without comment.

@ can you explain the reasoning for this unilateral and undiscussed (as far as I can see) deprecation?

Aaron Liu (talkcontribs)

Since this was unilateral, could I revert it? The IP seems knowledgeable, though.

Tacsipacsi (talkcontribs)

Please note that IPs cannot be pinged, so it’s unlikely that will notice this topic.

Aaron Liu (talkcontribs)

I've put a talkback template on their talk page.

This post was hidden by Aaron Liu (history)
Aaron Liu (talkcontribs)

The IP seems to also have mass-edited translations to port them to LC zh. Should we nuke these?

Pppery (talkcontribs)

I think very few people other than you and the IP know about this well enough to have an informed opinion so. (talkcontribs)

@Aaron Liu: It is because NoteTA would mess up translation memories, so to ensure the translation memory can provide correct results with proper language conversion, always specify the translation for different variants.

Aaron Liu (talkcontribs)

But isn't NoteTA the translation memory? I can see nowhere else with a translation memory.

Winston Sung (talkcontribs)

No. Translation memory is separated from the NoteTA template/module.

Translation memories is where the translation suggestions came from.

(the right part in the page translation UI)

Aaron Liu (talkcontribs)

Oh wait, the translation memory means the one on the right, doesn't it? Would it still be messed up if every page used NoteTA?

Edit: Thanks Winston for confirming the former. But does being messed up mean it displays improperly or wouldn't convert like the original page? In the latter case, would using NoteTA on these pages too solve that?

Winston Sung (talkcontribs)

Would it still be messed up if every page used NoteTA?

The problem would still exist:

  • NoteTA being place on one of the translation unit on a page, causing page-dependent NoteTA template transclusions showing up in different translation units' translation suggestions.
  • NoteTA cannot always placed in the first translation unit of a page due to different types of translation units (e.g., syntaxhighlight, template parameters like the Localized_link template).
  • Translators ignore the one-to-multi conversion and use the translation suggestion with broken language conversion result.
  • NoteTA template being used in templates causing duplicated page status indicator
Winston Sung (talkcontribs)

Also, every translation unit should be able to give correct language conversion result regardless of what the previous translation units were.

Winston Sung (talkcontribs)

Another reason is the broken syntax in cross-page-language transclusion.

Aaron Liu (talkcontribs)

I'm not sure why we would need to transclude a Chinese page onto a page of another language as long as the title of the page uses LC zh.

Winston Sung (talkcontribs)

See Main Page as an example.

Aaron Liu (talkcontribs)

Shouldn't the main page always be viewed in the user's language?

Winston Sung (talkcontribs)

The Main Page template /zh translation page has the page language code in 'zh'.

Aaron Liu (talkcontribs)

Sorry for dragging this out a bit, but could you clarify what the problem with the main page is?

Winston Sung (talkcontribs)

The Main Page has been migrated to LC zh, but here's a brief explaination:

Conversion-zh use UI-language-only detection and output respective variant contents.

If users view the template (usually by clicking the "other language" link) while there are inconsistency between the output language (UI language, the 'en' when not logged in would output 'zh-hans') and the variant language ('zh-Hant-TW' / 'zh-tw'), it will give out incorrect conversion results (e.g., '信息' vs. '資訊').

At this case, you can neither add NoteTA (as it will become many directly-exposed '-{H' tags) nor using native syntax (same reason).

Winston Sung (talkcontribs)
Winston Sung (talkcontribs)

Also, using the LC_zh template in the page display title translation units is meant to solve the Localized_link template problem.

Aaron Liu (talkcontribs)

Wasn't the problem with removing namespaces?

Winston Sung (talkcontribs)

Both the Main Page cross-language-page transclusion problem and the hide namespace problem.

This post was hidden by Aaron Liu (history) (talkcontribs)

As you can see, most of them were to ensure all translation units having consistency, always giving correct conversion results independently (instead of relying on other translation units with NoteTA).

RealMe is available on Miraheze

Tomodachi94 (talkcontribs)

Could Module:Used by/data.json be adjusted to include the RealMe extension in the Miraheze portion? I have tried to do it myself, but I am filtered by "Operator873's Filter". This was confirmed by a Miraheze engineer in their Discord. Unfortunately, I am unable to link to that discussion without being filtered. ~~~~

Pppery (talkcontribs)


Wikimedia Foundation Board of Trustees 2024 Selection

MediaWiki message delivery (talkcontribs)

You can find this message translated into additional languages on Meta-wiki.

Dear all,

This year, the term of 4 (four) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.

The Elections Committee will oversee this process with support from Foundation staff [2]. The Board Governance Committee created a Board Selection Working Group from Trustees who cannot be candidates in the 2024 community- and affiliate-selected trustee selection process composed of Dariusz Jemielniak, Nataliia Tymkiv, Esra'a Al Shafei, Kathy Collins, and Shani Evenstein Sigalov [3]. The group is tasked with providing Board oversight for the 2024 trustee selection process, and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].

Here are the key planned dates:

  • May 2024: Call for candidates and call for questions
  • June 2024: Affiliates vote to shortlist 12 candidates (no shortlisting if 15 or less candidates apply) [5]
  • June-August 2024: Campaign period
  • End of August / beginning of September 2024: Two-week community voting period
  • October–November 2024: Background check of selected candidates
  • Board's Meeting in December 2024: New trustees seated

Learn more about the 2024 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page, and make your plan.

Election Volunteers

Another way to be involved with the 2024 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page.

Best regards,

Dariusz Jemielniak (Governance Committee Chair, Board Selection Working Group)





[5] Even though the ideal number is 12 candidates for 4 open seats, the shortlisting process will be triggered if there are more than 15 candidates because the 1-3 candidates that are removed might feel ostracized and it would be a lot of work for affiliates to carry out the shortlisting process to only eliminate 1-3 candidates from the candidate list.

MPossoupe_(WMF)19:56, 12 March 2024 (UTC)

Reply to "Wikimedia Foundation Board of Trustees 2024 Selection"
M7 (talkcontribs)
M7 (talkcontribs)
M7 (talkcontribs)

Disable "Work in Progress" gadget

Summary by Jdforrester (WMF)

Gadget has been de-listed from the definitions configuration page, and emptied to disable its functionality for people cross-loading it, but not deleted.

Pppery (talkcontribs)

What it does is CamelCase the page title. It seems to be some admin having some fun in 2014, and is ancient cruft in 2023. I suggest it be disabled. Any objection?

P858snake (talkcontribs)
Krinkle (talkcontribs)

Do you mean "delete" instead of "disable"? The gadget was created as a demo during a MediaWiki workshop, I believe. It is disabled by default. I don't think it was ever enabled.

Strangely, it is enabled by 1000+ users per Special:GadgetUsage, though fewer than 10 of which are active users. In any event, I've deleted it now, since it was indeed not meant as a useful tool by itself.

Pppery (talkcontribs)

Global ban proposal for Slowking4

Seawolf35 (talkcontribs)
Reply to "Global ban proposal for Slowking4"