Last modified: 2014-04-25 10:06:03 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 T41663, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 39663 - Extensions should have possibility to issue messages in the user interface language without touching content
Extensions should have possibility to issue messages in the user interface la...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
: 39094 (view as bug list)
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-08-26 10:51 UTC by Marcin Cieślak
Modified: 2014-04-25 10:06 UTC (History)
10 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Marcin Cieślak 2012-08-26 10:51:48 UTC 
Some extensions like Cite or SyntaxHighlight_GeSHi (see Gerrit change #20219) issue error messages (like "syntaxhighlight-specify") that are inserted into the page HTML and therefore are currently rendered in the content language instead of the user language.

This bug is about discussing whether (1) they should use user (chrome) language
instead and (2) how to do it without cache thrashing .
Comment 1 Nemo 2012-11-20 08:51:52 UTC 
*** Bug 39094 has been marked as a duplicate of this bug. ***
Comment 2 Pavel Selitskas [wizardist] 2013-05-03 15:25:48 UTC 
I think that Cite and every other extension modifying the content should work in a page content language. It will make sense when we learn (read "implement") how to change the language on a per-page basis (see the notorious ContentHandler::getPageLanguage()).
Comment 3 Pavel Selitskas [wizardist] 2013-05-03 15:30:18 UTC 
Of course, we can leave senseless placeholders when we generate the content, and then replace them with appropriate localized messages via JavaScript. It's simple, but makes us transmit extra messages through the network. Choose what is cheaper and more effective.
Comment 4 Kunal Mehta (Legoktm) 2014-04-25 07:27:00 UTC 
This doesn't block bug 32551...
Comment 5 TeleComNasSprVen 2014-04-25 09:55:14 UTC 
(In reply to Kunal Mehta (Legoktm) from comment #4)
> This doesn't block bug 32551...

My bad, I think I put it in there by accident after reading the dupe...
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links