Last modified: 2005-03-06 07:27:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1637 - Transclusion should follow user's interface language
Transclusion should follow user's interface language
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-03-06 07:02 UTC by Muke Tever
Modified: 2005-03-06 07:27 UTC (History)
0 users

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


Description Muke Tever 2005-03-06 07:02:11 UTC
Currently a user can select an interface language for their skin to display. 
However it is not possible to refer to messages in the user's language in-page.  

For example if one wishes to make a reference to name of a site's "Recent 
changes", one can insert {{MediaWiki:Recentchanges}} into the document and it will 
display the "Recent changes" message even if the text is changed to something else. 
 However this only works in the wiki's base language: even if the user changes 
their interface language away from English, {{MediaWiki:Recentchanges}} will still 
display the English text, not the chosen language, when preferably it should show 
the latter.

[The URL given is to la.wiktionary's sandbox, which has a sample inclusion of 
Comment 1 Tim Starling 2005-03-06 07:27:35 UTC
Use {{int:recentchanges}}

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