Last modified: 2014-11-04 22:52:44 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.
Is there a way to use {{grammar:...}} and or {{plural:...}} ?
*** Bug 5310 has been marked as a duplicate of this bug. ***
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',
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".
Shouldn't this bug be closed already? Niklas Laxström's patch fulfills the requested enhancement.
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
Ok. Sorry. I was looking at "contributions" only.
(In reply to comment #6) > includes/SpecialWhatlinkshere.php For this one fixed in r20616 by two new messages: 'whatlinkshere-prev' and 'whatlinkshere-next'
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.
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.
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 ?
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?
(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.
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.
