Last modified: 2013-09-30 00:58:58 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 28920 - Allowing HTML tag to identify e.g. English text embedded in a non-English page
Allowing HTML tag to identify e.g. English text embedded in a non-English page
Status: NEW
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks: 18521
  Show dependency treegraph
 
Reported: 2011-05-10 22:15 UTC by Purodha Blissenbach
Modified: 2013-09-30 00:58 UTC (History)
7 users (show)

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


Attachments

Description Purodha Blissenbach 2011-05-10 22:15:47 UTC
There are several bugs such as Bug 28300 that ask for (limited, specific) inline html elements being allowed in messages of the user interface.

A recurring example are untranslated english technical terms appearing embedded in native sentences. It is good html, good for search engines and other text analysing tools, good for speech generators and screen reading devices, when those terms are properly tagged as English. This requires an inline element such as <span lang="en"> or similar, wrapped around them. It is usually not posing a problem when it is allowed in normal messages rendered as visible html text.

For messages used in contexts where html elements cannot be used, see bug 28919
Comment 1 Quim Gil 2013-04-02 05:09:10 UTC
Narrowing the request to the case explained above and moving to i18n in order to gather the atention of maintainers sensitive with multilingual content.
Comment 2 Brion Vibber 2013-09-29 14:04:31 UTC
So, any page content or UI component that uses wikitext for output can use <span lang="en">blah</span> already.

As I understand the problem is that folks would like to do this in messages that are plaintext...

Possibilities include:

* change those messages from plaintext to wikitext (are there performance issues, or issues with being able to render things for JavaScript client-side usage?)

* add a new message format that does some kind of restricted HTML, use that in place of plaintext/wikitext/raw HTML.

* ???
Comment 3 Niklas Laxström 2013-09-30 00:58:58 UTC
Functions of XML and Html classes don't accept message objects. Currently it is all or nothing escaping there.

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


Navigation
Links