Last modified: 2014-11-04 22:52:44 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 4777 - Separate messages 'prevn', 'nextn'
Separate messages 'prevn', 'nextn'
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
1.10.x
All All
: Normal normal with 6 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
: 5310 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-28 10:44 UTC by Carlos
Modified: 2014-11-04 22:52 UTC (History)
8 users (show)

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


Attachments

Description Carlos 2006-01-28 10:44:55 UTC
They are used all over the place to navegate through lists, to get the next or
previous n items of it. The problem is, "next" and "previous" are adjectives and
in many languages they must agree in gender, number, etc. with the substantive.

In Spanish, "articles" is masculine and "edits" feminine. If we change prevn to
display '$1 previas' then the category listings will be wrong; if we change it
to say '$1 previos' then the user's contributions listing is wrong (the last one
is used now, more people look at categories than at user's contributions).

Thanks.
Comment 1 lɛʁi לערי ריינהארט 2006-02-10 00:00:49 UTC
Is there a way to use {{grammar:...}} and or {{plural:...}} ?
Comment 2 Niklas Laxström 2006-04-11 14:42:39 UTC
*** Bug 5310 has been marked as a duplicate of this bug. ***
Comment 3 Niklas Laxström 2006-04-11 14:49:39 UTC
I added following messages used in user contributions to HEAD.

'sp-contributions-newest' => 'Newest',
'sp-contributions-oldest' => 'Oldest',
'sp-contributions-newer'  => 'Newer $1',
'sp-contributions-older'  => 'Older $1',

Comment 4 Omegatron 2006-04-11 14:51:26 UTC
As in Bug 5310, the list "next" and "previous" need to be separated from the
chronological "next" and "previous", so that the chronological ones can be
replaced by "later" and "earlier".
Comment 5 Carlos 2006-06-29 10:18:44 UTC
Shouldn't this bug be closed already? Niklas Laxström's patch fulfills the
requested enhancement.
Comment 6 Niklas Laxström 2006-06-29 12:29:33 UTC
As far as I know this is not yet fixed.
grep nextn -l includes/*.php
includes/CategoryPage.php
includes/GlobalFunctions.php
includes/PageHistory.php
includes/SpecialNewimages.php
includes/SpecialWhatlinkshere.php
Comment 7 Carlos 2006-06-29 12:34:45 UTC
Ok. Sorry. I was looking at "contributions" only.
Comment 8 Raimond Spekking 2007-03-22 09:27:01 UTC
(In reply to comment #6)
> includes/SpecialWhatlinkshere.php

For this one fixed in r20616 by two new messages: 'whatlinkshere-prev' and
'whatlinkshere-next'

Comment 9 ais523 2007-10-19 09:33:44 UTC
The history nextn/prevn definitely needs a different message from the category nextn/prevn; there has been more than one complaint on enwiki (including one recent complaint) that 'next' and 'previous' are confusing and should be 'older' and 'newer' on article histories, but this change can't be done in interface messages with the current software because the same messages are used in categories, on which 'older' and 'newer' normally don't make sense. Adding keyword 'easy' because this is likely just a matter of changing the name of the message used and adding a new message to the default language files.
Comment 10 Niklas Laxström 2007-12-07 09:16:06 UTC
Since r28237 there is messages pager-older-n and pager-newer-n, which are used in page histories, block list and in merge history. Still need to fix Special:Newpages.
Comment 11 Huji 2008-01-08 11:45:18 UTC
At the moment, we have: 

grep nextn -l includes/*.php
includes/CategoryPage.php
includes/GlobalFunctions.php
includes/Pager.php
includes/SpecialNewimages.php

I think choronology doesn't make sense for categories. So is it that we just need to fix SpecialNewimages.php ?
Comment 12 Aphaia 2008-02-17 16:49:07 UTC
I recently met a similar problem when I tried to fix grammatically incorrect "pro usor:xxxx" on la localization. It should be "pro usore:XXX.." but there is only one valuable (pro $1[= user[in l10n]:$USERNAME), so I couldn't fix it. Or better to bug in another thread?
Comment 13 Niklas Laxström 2008-03-16 10:04:58 UTC
(In reply to comment #12)
> I recently met a similar problem when I tried to fix grammatically incorrect
> "pro usor:xxxx" on la localization. It should be "pro usore:XXX.." but there is
> only one valuable (pro $1[= user[in l10n]:$USERNAME), so I couldn't fix it. Or
> better to bug in another thread?

Yes please open a new bug for it with more details.
Comment 14 Niklas Laxström 2009-05-21 13:15:55 UTC
grep nextn -l includes/*.php
includes/CategoryPage.php
includes/GlobalFunctions.php
includes/Pager.php

I'm assuming this issue is fixed for now, something might still call the one from GlobalFunctions, but I haven't noticed any.

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


Navigation
Links