Last modified: 2006-05-01 20:38:29 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 5454 - A link to a title with two quotes is not parsed correctly
A link to a title with two quotes is not parsed correctly
Status: RESOLVED DUPLICATE of bug 4598
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal normal with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-04-04 21:39 UTC by Yuri Astrakhan
Modified: 2006-05-01 20:38 UTC (History)
1 user (show)

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


Description Yuri Astrakhan 2006-04-04 21:39:40 UTC
If a page has two quote symbols in its name, an interwiki link to it will not be
shown properly in the other languages section.

Example: [[nap:Torre d''o Grieco]] is shown as text instead of an interwiki link
to the nap: article.
Workaround: [[nap:Torre d<nowiki>''</nowiki>o Grieco]] solves it, but later all
the bots remove that as improper link.

See the URL link for the specific example.
Comment 1 Phil Boswell 2006-04-04 22:08:10 UTC
Just to point out that the link which fails in the wiki works here, whilst the hacked-up link which works in 
the wiki fails here.

Maybe there's something in whatever renders links here which might be of help :-)
Comment 2 Melancholie 2006-04-05 13:35:57 UTC
Instead of using <nowiki> you could replace one or both apostrophes by: &#x0027;
I do not know whether bots will replace this, too; but I don't think so.
Comment 3 Melancholie 2006-04-05 13:38:09 UTC
@Yuri: Could you test it with your bot at [[Torre del Greco]] again?
Comment 4 Yuri Astrakhan 2006-04-05 21:55:20 UTC
The bot was designed to resolve all &...; numbers to make them readable to the
users. Before utf-8 all links had to be entered that way, and it was a mess.
Now, bot converts any such numbers to readable symbols, which means that
"&#x0027;'" would get converted to "''", unless we introduce some ugly hack. 
Regardless, this is clearly a bug in the mediawiki, so hopefully we can get it
Comment 5 Brion Vibber 2006-04-05 22:20:39 UTC
Most likely we should just ban '' and ''' in title names, as we've banned %[0-9a-f]{2} 
to avoid ambiguous and breaky markup-in-titles.
Comment 6 Yuri Astrakhan 2006-04-06 02:38:25 UTC
I think banning such titles might be a good solution, but, unlike the %XX, its
not breaking the syntax or causes ambiguity - it is just a bug in the parser
that can be fixed. Maybe this bug will help us structure the parser better? :)
Comment 7 lɛʁi לערי ריינהארט 2006-04-07 14:30:26 UTC

I assume this is a duplicate of
Bug 4598: Order of title recognition and bold / italic rendering should be reversed

Search for such titles will fail; see
Bug 4601: Exact search for titles using php meta / escape characters

However I see this as valid titles. When bug 4598 no escaping will be / should
be required.

best regards reinhardt [[user:gangleri]]
Comment 8 Antoine "hashar" Musso (WMF) 2006-05-01 20:38:29 UTC
This is exactly a duplicate. A patch is pending review in #4598

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

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