Page MenuHomePhabricator

Change paging link labels on page histories to "newest", "newer", "oldest" and "older"
Closed, ResolvedPublic

Description

Author: itai_y_beerli

Description:
I'd like the navigation links of the history pages to be renamed from "Previous
50", "Next 50" to "Newer 50", "Older 50", respectively.

What's wrong with the current naming convention?

It's unintuitive, even counter-intuitive ("Next" is "Further in the past"!),
hence confusing, and also inconsistent with both the two other history
navigation links named "Latest" and "Earliest" as well as with the navigation
links appearing on top of the revision pages, named "<- Older revision", "Newer
revision ->".


Version: 1.10.x
Severity: enhancement
OS: Windows XP
Platform: PC

Details

Reference
bz9579

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:38 PM
bzimport set Reference to bz9579.
bzimport added a subscriber: Unknown Object (MLST).

itai_y_beerli wrote:

On this occasion, it would be nice if you also renamed the history navigation
links "Latest" and "Earliest" to "Newest" and "Oldest". This is not so
important, but it will make the interface more consistent.

robchur wrote:

This can, of course, be done on a per-wiki basis through the MediaWiki namespace.

axel9891 wrote:

*** Bug 11064 has been marked as a duplicate of this bug. ***

thisnudibranch wrote:

It can't be fixed locally; the prevn and nextn messages are used by categories, which need "previous" and "next". We need two new messages, historyolder and historynewer.

EN.WP.ST47 wrote:

Proposed patch to create new such messages

This patch will:
a) add the function 'getNavigationBar' to the class 'PageHistoryPager' based on the function in 'ReverseChronologicalPager'
b) change the messages in the new 'getNavigationBar from 'prevn' and 'nextn' to 'historyprevn' and 'historynextn'
c) create the above messages in all languages that have a localized 'prevn' and 'nextn'

I could not find any 'master list' of messages, but if there is one, it is not updated :(

Attached:

Resolved in r28237 (Dec 7, 2007) as part of the fix for bug #4777, AFAICT.