Last modified: 2006-10-04 17:29:27 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 7489 - Expansion of the "pipe trick" functionality
Expansion of the "pipe trick" functionality
Status: RESOLVED DUPLICATE of bug 6826
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal minor with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: parser
Depends on:
  Show dependency treegraph
Reported: 2006-10-04 14:23 UTC by freakofnurture
Modified: 2006-10-04 17:29 UTC (History)
1 user (show)

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


Description freakofnurture 2006-10-04 14:23:52 UTC
It's fairly common knowledge that a wikilink such as [[Cricket (insect)|]] will produce a 
link that points to [[Cricket (insect)]] but displays as "Cricket". Such notational 
shorthand is of even greater usefulness when dealing with titles that are longer and/or 
more difficult to type/spell. I suggest the following improvements:

1. Keep this functionality, but refrain from actually expanding the second half of the 
link. This will reduce the resulting byte count when dealing with particularly long 
titles, and make the affected paragraphs easier to edit (or even comprehend when reading 
them from the editing box). For example, [[Six Degrees of Separation (film)|]] should 
link and display in the rendered page output the same way it does now, but retain the 
same brevity in the saved wikitext, rather than expanding to [[Six Degrees of Separation 
(film)|Six Degrees of Separation]].

2. Expand the functionality of the pipe trick to accommodate comma-separated ordered 
pairs. For example, I'd like to be able to type [[Providence, Rhode Island|]] or [[Diana, 
Princess of Wales|]], and produce links with the displayed text "Providence" or "Diana" 
just as it would if the actual target pages were "Providence (Rhode Island)" and "Diana 
(Princess of Wales)" rather than the generally accepted comma conventions for nobility 
and postal locations.

3. Finally, I'd like to be able to use the pipe trick in edit summaries (and for block/
deletion/protection/pagemove reasons of course). Attempting to do so currently produces 
non-clickable text. Again, this should occur in a non-bloating manner, so that it does 
not count against the maximum byte count of edit comments.

I don't foresee any adverse effects with regard to backward compatability.

Comment 1 freakofnurture 2006-10-04 14:47:32 UTC
correction regarding item 3, in edit summaries, links are displayed as though the 
pipe is not present in the link at all. Still could use fixing IMO.
Comment 2 Filip Maljkovic [Dungodung] 2006-10-04 15:01:21 UTC
1) I think that this is not going to change. This pipe trick exists only before
the save, and I think that the developers aren't going to change that

2) There is a bug opened for this exact thing, AFAIK

3) AFAIK, this is due to the fact that edit summaries, logs etc. don't get
parsed for the "pipe trick". IANAD, but this shouldn't be too hard to implement

4) It is advisable to use separate bug reports for separate issues.

Cheers ;)
Comment 3 Brion Vibber 2006-10-04 16:36:48 UTC
Closing INVALID.

*** This bug has been marked as a duplicate of 6862 ***
Comment 4 freakofnurture 2006-10-04 17:22:57 UTC
Perhaps a case of wrong number -- I do not see how 6862 is related to this.
Comment 5 Brion Vibber 2006-10-04 17:29:27 UTC

*** This bug has been marked as a duplicate of 6826 ***

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