Jump to content

Logentry-rights-* and gender

Logentry-rights-* and gender

I believe Logentry-rights-rights ("$1 {{GENDER:$2|changed}} group membership for {{GENDER:$6|$3}} from $4 to $5"), Logentry-rights-rights-legacy ("$1 {{GENDER:$2|changed}} group membership for $3"), and Logentry-rights-autopromote ("$1 was automatically {{GENDER:$2|promoted}} from $4 to $5") should use the {{GENDER:$2|changed}} syntax in the original English message so the translations are not marked as problematic due to unsupported $2, which should be supported in all log entry messages.

Mormegil (talk)14:07, 15 November 2012

Isn't this the infamous bugzilla:24156 whose fix was vetoed by Tim?

Nemo (talk)18:23, 20 November 2012

Yes. I've added keyword "platformeng". Allegedly that should help.

Siebrand20:07, 20 November 2012
 

D’oh! You mean the whole gender support in log entries was reverted? I did not really notice that (except I spotted a few gender removals, but I thought they were special cases). But if that’s the case, {{logentry}} should be updated as well, because using a quick grep, I found at least 112 messages with “logentry” and “gender” currently committed.

Mormegil (talk)10:26, 21 November 2012
Edited by another user.
Last edit: 11:18, 26 September 2020

Not the whole support, just {{GENDER}} calls were removed because they were inefficient (apparently they are not anymore but they haven't been restored yet).

Nike (talk)12:11, 21 November 2012

I see; the GENDER seems to work correctly (on logentry-rights-*, at least), it was just removed because of a performance issue. All right then, I’ll let it be now, and wait for possible future restoration.

Mormegil (talk)16:21, 21 November 2012