Last modified: 2006-06-16 23:37:19 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 6337 - MediaWiki to handle caps/no-caps image extension natively ?
MediaWiki to handle caps/no-caps image extension natively ?
Status: RESOLVED DUPLICATE of bug 4421
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-06-16 23:32 UTC by jd
Modified: 2006-06-16 23:37 UTC (History)
0 users

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


Description jd 2006-06-16 23:32:59 UTC
When one has uploaded an image (ie. a picture or a sound or an animation or
whatever is filed within the Image: namespace), MediaWiki is not able to handle
by itself caps/non-caps extension. Eg. if one has uploaded My_Pic.JPG but write
[[Image:My_Pic.jpg|args...]], no image will be displayed.

It would be cool if MediaWiki were to handle this natively, since two images
should be distinguished by their names, not their extensions (ie. My_Pic.jpg,
My_Pic.jpeg and My_Pic.JPG are likely to be the same image, but MyPic.jpg could
be a different one). It would make the user in the street life easier not to
think about extension typo.
Comment 1 Brion Vibber 2006-06-16 23:37:19 UTC
I'm going to dupe this to bug 4421; see also bug 5763, bug 709.

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

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