Last modified: 2006-01-16 17:03:10 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 1275 - image links section emtpy for image with non ascii char in name
image links section emtpy for image with non ascii char in name
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-06 23:07 UTC by peter green
Modified: 2006-01-16 17:03 UTC (History)
1 user (show)

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


Attachments

Description peter green 2005-01-06 23:07:14 UTC
look at the last two images on http://commons.wikimedia.org/wiki/Aucuba_japonica
they say nothing links to them!

based on a previous bug i tried editing the page and it made no difference

the char in question has a code point between u+0080 and u+00FF for those who
don't already known commons is a utf-8 wiki.

my beleif is this is a charset related issue but i don't really know much about
the internal details of mediawiki
Comment 1 JeLuF 2005-01-12 00:25:31 UTC
I've seen the issue as described by Peter when he submitted the bug.
Trying to verify it, I had to notice that now everything looks fine.

Please reopen the bug if you find another example for this behaviour.
Comment 2 peter green 2005-01-12 00:57:05 UTC
which means either it was a database delay issue (1.4 has real trouble with
those) or its been fixed.


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


Navigation
Links