Last modified: 2005-12-05 21:07:22 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 4180 - rendering of MediaWiki:Listingcontinuesabbrev
rendering of MediaWiki:Listingcontinuesabbrev
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 4170
  Show dependency treegraph
Reported: 2005-12-05 12:16 UTC by Ronald Beelaard
Modified: 2005-12-05 21:07 UTC (History)
1 user (show)

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


Description Ronald Beelaard 2005-12-05 12:16:17 UTC
If the contents of this file contains html opening/closing tags, the < and > 
chars are converted to &lt;, &gt;.
On nl we used to have:
   - <font size=-1><i>vervolg</i></font>
as contents. 
As a temporary work-around this has now been replaced by an ASCII only text
Comment 1 Ronald Beelaard 2005-12-05 12:18:49 UTC
Oeps: although it is in the summary, the file name is 
Comment 2 Jelte (WebBoy) 2005-12-05 12:27:23 UTC
The problem is here:

vibber said: * ( bug 4170 ) Decode HTML character escapes in sort key

But I _think_ the change of wfMsg('listingcontinuesabbrev') to
wfMsgHtml('listingcontinuesabbrev') hasn't anything to do with bug 4170.
Comment 3 Brion Vibber 2005-12-05 21:07:22 UTC
Such messages should not contain HTML; that it wasn't properly escaped for output before was an 
oversight, which I have corrected.

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