UserInfoCard: Support GENDER for all nedeed i18n strings
Closed, ResolvedPublic0.5 Estimated Story Points
Actions

Description

Hello! I found some lines that should support GENDER.

        "checkuser-userinfocard-menu-view-contributions": "View {{GENDER:$1|user}} contributions",
	"checkuser-userinfocard-menu-add-to-watchlist": "Add {{GENDER:$1|user page}} to watchlist",
	"checkuser-userinfocard-menu-remove-from-watchlist": "Remove {{GENDER:$1|user page}} from watchlist",
	"checkuser-userinfocard-menu-check-ip": "Check {{GENDER:$1|user}} IP addresses",
	"checkuser-userinfocard-menu-block-user": "Block {{GENDER:$1|user}}",
        "checkuser-userinfocard-loading-label": "Loading {{GENDER:$1|user}} info",
	"checkuser-userinfocard-toggle-button-aria-label": "Open {{GENDER:$1|user}} info card",
	"checkuser-userinfocard-open-menu-aria-label": "Open {{GENDER:$1|user}} info card menu",

Details

Related Changes in Gerrit:

	Subject	Repo	Branch	Lines +/-
	Remove GENDER from messages which cannot support it	mediawiki/extensions/CheckUser	master	+8 -8
	Use gender for several UserInfoCard messages	mediawiki/extensions/CheckUser	master	+104 -61

Customize query in gerrit

Event Timeline

Iniquity created this task.Jul 29 2025, 12:07 PM

Restricted Application added a project: Trust and Safety Product Team. · View Herald TranscriptJul 29 2025, 12:07 PM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

A_smart_kitten added a project: Gender-Support.Jul 29 2025, 12:16 PM

checkuser-userinfocard-error-no-data

We may not be able to properly support GENDER in this message, because we get the gender of the user using the API and the above message is displayed if the API returns nothing. We could just provide unknown as the gender always if that works?

In T400687#11043682, @Dreamy_Jazz wrote:

checkuser-userinfocard-error-no-data

We may not be able to properly support GENDER in this message, because we get the gender of the user using the API and the above message is displayed if the API returns nothing. We could just provide unknown as the gender always if that works?

It seems to me that if we absolutely cannot get information about the user, then remove this message from the list above. But if we have a chance, then we can use {{GENDER:|male text|female text|gender-neutral text for unspecified gender}}.

In T400687#11044159, @Iniquity wrote:

In T400687#11043682, @Dreamy_Jazz wrote:

checkuser-userinfocard-error-no-data

We may not be able to properly support GENDER in this message, because we get the gender of the user using the API and the above message is displayed if the API returns nothing. We could just provide unknown as the gender always if that works?

It seems to me that if we absolutely cannot get information about the user, then remove this message from the list above. But if we have a chance, then we can use {{GENDER:|male text|female text|gender-neutral text for unspecified gender}}.

Yeah, if the message I mentioned is used then we can absolutely not get information about the user (because the request to get it failed).

We can still define GENDER in the message, but the gender in this case would default to unknown to use the gender-neutral text.

I’d probably add a note in the message documentation of checkuser-userinfocard-error-no-data in this case, so that this question doesn’t get asked again and again.

In T400687#11044187, @Dreamy_Jazz wrote:

We can still define GENDER in the message, but the gender in this case would default to unknown to use the gender-neutral text.

In this case, it seems to me that it will only confuse the translator, so gender is not needed :)

Iniquity updated the task description. (Show Details)Jul 29 2025, 6:01 PM

kostajh set the point value for this task to 0.5.Aug 1 2025, 9:27 AM

Dreamy_Jazz moved this task from Inbox to Engineering on the Trust and Safety Product Team board.Aug 6 2025, 8:53 AM

Dreamy_Jazz added a project: Trust and Safety Product Sprint (Sprint Rum baba (July 28 - August 15)).Aug 12 2025, 4:13 PM

OKryva-WMF moved this task from Priority Backlog to Ready on the Trust and Safety Product Sprint (Sprint Rum baba (July 28 - August 15)) board.Aug 12 2025, 4:53 PM

OKryva-WMF triaged this task as High priority.Aug 12 2025, 5:03 PM

Dreamy_Jazz claimed this task.Aug 12 2025, 8:01 PM

Change #1178078 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/extensions/CheckUser@master] Use gender for several UserInfoCard messages

https://gerrit.wikimedia.org/r/1178078

gerritbot added a project: Patch-For-Review.Aug 12 2025, 9:01 PM

Dreamy_Jazz moved this task from Ready to Needs Review on the Trust and Safety Product Sprint (Sprint Rum baba (July 28 - August 15)) board.Aug 12 2025, 9:01 PM

Dreamy_Jazz moved this task from Untriaged to Gender on the I18n board.

Change #1178078 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] Use gender for several UserInfoCard messages

https://gerrit.wikimedia.org/r/1178078

ReleaseTaggerBot added a project: MW-1.45-notes (1.45.0-wmf.15; 2025-08-19).Aug 13 2025, 9:00 AM

This probably doesn't need QA, so moving to done and resolving

Maintenance_bot removed a project: Patch-For-Review.Aug 13 2025, 9:30 AM

But it would have needed more thorough code review… Please address my comments on Gerrit.

A_smart_kitten subscribed.Aug 13 2025, 8:15 PM

Dreamy_Jazz moved this task from Done to In Progress on the Trust and Safety Product Sprint (Sprint Rum baba (July 28 - August 15)) board.Aug 14 2025, 9:53 AM

OKryva-WMF added a project: OKR-Work.Aug 14 2025, 9:54 AM

Change #1178825 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/extensions/CheckUser@master] Remove GENDER from messages which cannot support it

https://gerrit.wikimedia.org/r/1178825

gerritbot added a project: Patch-For-Review.Aug 14 2025, 9:58 AM

Dreamy_Jazz moved this task from In Progress to Needs Review on the Trust and Safety Product Sprint (Sprint Rum baba (July 28 - August 15)) board.Aug 14 2025, 10:05 AM

AFAICS the second patch should have resolved the open comments on the first patch, so marking this as resolved again.

Change #1178825 merged by jenkins-bot: