Last modified: 2014-11-17 10:35:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 27387 - Gender specific display text for tabs
Gender specific display text for tabs
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
1.18.x
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 27691 28052
  Show dependency treegraph
 
Reported: 2011-02-13 21:34 UTC by Leinad
Modified: 2014-11-17 10:35 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Leinad 2011-02-13 21:34:54 UTC
Now namespaces have gender support (bug17160), but tab of NS_USER needs the same support.

On [[MediaWiki:Nstab-user]] is possible to set {{GENDER:{{BASEPAGENAME}}|male form|female form}}, but I'm not sure is it ok for servers performance.

Maybe better idea is to create [[MediaWiki:Nstab-user-male]] and [[MediaWiki:Nstab-user-female]] and use these messages when $namespaceGenderAliases is enabled.
Comment 1 Siebrand Mazeland 2011-03-03 00:12:16 UTC
(In reply to comment #0)
> Maybe better idea is to create [[MediaWiki:Nstab-user-male]] and
> [[MediaWiki:Nstab-user-female]] and use these messages when
> $namespaceGenderAliases is enabled.

This particular idea is not a good suggestion, because it assumes that
male/female will be the only two forms GENDER will (ever) use. However, there
has been speculation that formal/informal could also be introduced using this
magic word, and there is an open issue requesting a transgender form. Limiting
options isn't a good idea. Using GENDER, and adding support for it where
needed, is what needs to be done, regardless of how many GENDERs we will have
defined now or in the future.
Comment 2 Leinad 2011-03-03 00:29:24 UTC
(In reply to comment #1)
> This particular idea is not a good suggestion, because it assumes that

Hmmm, maybe you are right, but are you sure this is good solution for servers? - in similar situation Domas reverted changes (http://en.wikipedia.org/w/index.php?title=MediaWiki:Nstab-main&diff=217955007&oldid=215091279) :-) and last time there was created dedicated message (Bug14267).

PS. If {{GENDER:{{BASEPAGENAME}}|male form|female form}} is the best solution, could you add variable $1 for [[MediaWiki:Nstab-user-male]] as in standard message with GENDER support: {{GENDER:$1|male form|female form}}.
Comment 3 Chad H. 2011-03-03 01:08:12 UTC
(In reply to comment #2)
> Hmmm, maybe you are right, but are you sure this is good solution for servers?
> - in similar situation Domas reverted changes
> (http://en.wikipedia.org/w/index.php?title=MediaWiki:Nstab-main&diff=217955007&oldid=215091279)
> :-) and last time there was created dedicated message (Bug14267).
> 

The major difference between that and this is the number of readers in NS_MAIN vs NS_USER.
Comment 4 Platonides 2011-03-06 21:55:17 UTC
> > Maybe better idea is to create [[MediaWiki:Nstab-user-male]] and
> > [[MediaWiki:Nstab-user-female]] and use these messages when
> > $namespaceGenderAliases is enabled.
> 
> This particular idea is not a good suggestion, because it assumes that
> male/female will be the only two forms GENDER will (ever) use. 

There's nothing fixed in that naming.

$gender = $user->getGender();
if ($gender === '') {
  $msg = 'nstab-user';
} else {
  $msg = 'nstab-user-' . $gender;

  if $msg doesn't exists, fall back to 'nstab-user'
}

print wfMsg($msg) in the tab
Comment 5 Niklas Laxström 2011-04-02 19:48:11 UTC
Added message documentation in twn. That should be enough.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links