Page MenuHomePhabricator

MediaWiki:tooltip-t-contributions: please add a parameter to allow gender use
Closed, ResolvedPublic

Description

The message tooltip-t-contributions is used as tooltip on the 'User contributions' link in the toolbox on a user page.

In French it is 'Voir la liste des contributions de cet utilisateur', which should be 'Voir la liste des contributions de cet utilisatrice' if the user whose page is being read is female.

Afaik this message support {{GENDER:}} but it have no parameter that says to which user it is related, so we cannot get it correct for female users.

Details

Reference
bz54843

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:31 AM
bzimport set Reference to bz54843.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to Ltrlg from comment #0)

Afaik this message support {{GENDER:}} but it have no parameter that says to
which user it is related, so we cannot get it correct for female users.

That syntax doesn't help here and shouldn't be used, because it uses the gender of the /current/ user. http://translatewiki.net/wiki/Gender

Yes, of course. What I really want is the missing parameter, I just wrote that to say that adding the parameter is the only needed action, as the message is already parsed.

Is this still relevant? I looked through the system and couldn't find where tooltip-t-contributions message is actually used. Is it being used broken up in some code?

I did find that "tooltip-pt-mycontris" (which is the tooltip for the "My contributions" top menu has no GENDER support. Is this what this ticket is about, or is it a different issue?

After a bit of research, this is actually not easy at all. A few findings that may help in the future for anyone who can take this on:

  1. The message in ungreppable because it's broken apart in the code (tsk tsk) -- it seems to actually be constructed and used here in includes/skins/BaseTemplate.php#84 (inside function getToolbox())
  2. Adding "{{GENDER}}" is going to be challenging here because we need to find where the message is actually built and then send it the relevant user (not the current user!) as a parameter.

I initially thought of giving this as a Google Code In task, but this is way too complex for that.