Last modified: 2010-05-15 15:33:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T3326, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1326 - "1movedto2" message inserted in wrong language
"1movedto2" message inserted in wrong language
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
1.4.x
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://meta.wikimedia.org/w/index.php...
: patch
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-14 01:59 UTC by Rowan Collins [IMSoP]
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Attachments
use the wiki's content language when inserting this comment (1.31 KB, patch)
2005-01-14 02:02 UTC, Rowan Collins [IMSoP]
Details

Description Rowan Collins [IMSoP] 2005-01-14 01:59:33 UTC
When a user moves a page, the message inserted into the edit history is in their
chosen interface language. Anybody who doesn't speak that language will simply
be baffled by what they see in watchlists, history pages, etc.

The ideal situation would be if the message could be magically translated
depending on who was *viewing* the history entry (i.e. it would behave as part
of the interface, not just an immutable comment in the history). But this may be
a bit far-fetched, so the simpler solution is just to use the content language
selected for the entire wiki, which will presumably have been chosen as
appropriate for the majority of users.
Comment 1 Rowan Collins [IMSoP] 2005-01-14 02:02:25 UTC
Created attachment 204 [details]
use the wiki's content language when inserting this comment

Here's a simple patch for the easy way out: use wfMsgForContent() rather than
wfMsg().
Comment 2 zhengzhu 2005-01-14 03:23:11 UTC
patch applied

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


Navigation
Links