Last modified: 2008-05-29 07:40:00 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 5146 - Separator in recent changes list is hardcoded
Separator in recent changes list is hardcoded
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-03-02 22:02 UTC by Kovács Endre János
Modified: 2008-05-29 07:40 UTC (History)
2 users (show)

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


Description Kovács Endre János 2006-03-02 22:02:43 UTC
File: includes/Linker.php
Function: formatComment()

The separator between the section link and the edit summary in recent change lists is 
currently hardcoded: 


It may be a good idea to turn the hardcoded string into a variable (preferably using 
Comment 1 Rob Church 2006-05-21 00:44:03 UTC
For what purpose?
Comment 2 Kovács Endre János 2006-05-21 10:00:38 UTC
(In reply to comment #1)
> For what purpose?

So as to make it possible to change the separator per project. Some may prefer to 
use an en dash, others would perhaps use an em dash, a bullet or a colon (or even 
stick with the hyphen). Typographic conventions vary from language to language.
Comment 3 Raimond Spekking 2008-05-29 07:40:00 UTC
This was fixed/changed some time ago. I cannot find a hardcoded '-' in includes/Linker.php anymore :)

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