Last modified: 2011-08-19 20:20:43 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 T21748, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19748 - recentchangestext should be translated just like any other string
recentchangestext should be translated just like any other string
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Recent changes (Other open bugs)
1.16.x
All All
: Lowest minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://transgender-taiwan.org/index.p...
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-15 17:35 UTC by Dan Jacobson
Modified: 2011-08-19 20:20 UTC (History)
2 users (show)

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


Attachments

Description Dan Jacobson 2009-07-15 17:35:24 UTC
Why this line?
>$out->addWikiText( wfMsgForContentNoTrans( 'recentchangestext' ) );
Why do you insist I have that one line of untranslated Chinese at top of the above URL when it should clearly be English?

There was some mention deep in here in Bugzilla, but there's no justification for not translating it here in my simple case.

I often want to show English speakers some problem, and I rely on uselang=en to work, and work right.
Comment 1 Dan Jacobson 2009-07-15 17:43:52 UTC
Grepping thru the code finds a couple other instances of wfMsgForContentNoTrans(), apparently some kind of speed up around caching or something. Please see if they still make all the sense they perhaps once did, and are still justified.
Else why would one not want the translation?
Comment 2 Chad H. 2009-07-15 18:39:23 UTC
NoTrans does not mean don't translate, it means don't transform (parse) it. Since it's being added as wikitext to the page (which gets parsed), there's no major issue.
Comment 3 Dan Jacobson 2009-07-16 00:14:26 UTC
There is too an issue.
Why in the world must that string on that page appear in Chinese, despite a perfectly good English string available, and everything else that could be affected by uselang=en affected. Why, why, why?
Comment 4 Chad H. 2009-07-17 20:47:36 UTC
Because a good number of wikis customize this message heavily, and that would require them to copy it to all the language variants.
Comment 5 Dan Jacobson 2009-07-17 21:01:49 UTC
Well then Aha, Checkmate, there should be
IF they haven't customized it
   THEN just like any other message, obey uselang= etc.
   ELSE then do as you do now, but what if they indeed want to provide
   three different translations, etc...

Anyway, the current way is not the right way to make a special case.
I fully support the goal, but the way it is currently accomplished
messes it up for the default case.

And of course this is all rather complicated so I'll just submit my
"high level analysis" above, and leave it as that...

Do get around to it LATER.
Comment 6 Max Semenik 2011-08-19 20:20:43 UTC
CLosing as WONTFIX - most wikis only localise it in one language. Others can always override this behaviour with $wgForceUIMsgAsContentMsg or {{int:...}} hacks.

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


Navigation
Links