Page MenuHomePhabricator
Create Task
Maniphest T18909

histlegend message should use live 'cur', 'last' messages instead of duplicating their contents
Closed, ResolvedPublic
Actions

Description

Currently, "cur" and "last" texts are hardcoded in the 'histlegend' page history legend text. This means that any customization to one or the other leads to an out-of-sync message -- for instance when r45311 goes live, English Wikipedia's customized legend will be incorrect (saying "last" instead of the new text, "prev").

The Minor edit letter is also used here... Probably some other legends need to be similarly updated.

Version: unspecified
Severity: enhancement
URL: http://en.wikipedia.org/w/index.php?title=MediaWiki:Histlegend&action=history

Details

Reference
bz16909

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:24 PM
• bzimport added a project: MediaWiki-Internationalization.
• bzimport set Reference to bz16909.
• bzimport added a subscriber: Unknown Object (MLST).
• brooke created this task.Jan 6 2009, 10:05 PM
siebrand added a comment.Jan 7 2009, 8:54 AM

Inconsistencies can always arise. Whenever they occur, developers try to fix them. {{int:key}} could be used in messages to circumvent this. With 300+ localisations, something is out of sync somewhere all the time. Customised messages are out of sync by definition.

It seems to me WONTFIX is closest to CANTFIX here, unless you want to throw away a few hundred translations by renaming this message. We live with it...

siebrand added a comment.Jan 7 2009, 8:56 AM

Some additional information: see http://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki:Histlegend for all available translations of MediaWiki:Histlegend.

• brooke added a comment.Jan 7 2009, 8:18 PM

(In reply to comment #1)

It seems to me WONTFIX is closest to CANTFIX here, unless you want to throw
away a few hundred translations by renaming this message. We live with it...

What on earth are you talking about?

Inconsistencies can always arise. Whenever they occur, developers try to fix
them. {{int:key}} could be used in messages to circumvent this.

That's exactly the aim of this bug entry...

siebrand added a comment.Feb 8 2009, 9:57 AM

Fixed in r47003.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits