Last modified: 2006-09-10 12:11:53 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 7279 - Image import maintenance script uses buggy PHP5 basename() breaking multibyte chinese hebrew greek internationalisation
Image import maintenance script uses buggy PHP5 basename() breaking multibyte...
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
All Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-09-09 22:43 UTC by Carl Austin Bennett
Modified: 2006-09-10 12:11 UTC (History)
0 users

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


Description Carl Austin Bennett 2006-09-09 22:43:11 UTC
In most of the MediaWiki PHP code, PHP's basename() function has been replaced
with wfBaseName() from includes/GlobalFunctions because the PHP default version
is seriously buggy in handling multibyte characters.

Even after SVN update to get updated to revision 16459, the
maintenance/importImages.php script still seems to call the default PHP
basename() function. This breaks import of all images in which the basename
begins with a UTF-8 two-byte character. In languages such as el: he: zh: which
aren't based on the western-euro character set, normally nothing will be
correctly importable as stripping leading two-byte characters leaves basically
nothing but the .jpg or .png extension. Other languages with a few non-ASCII
characters will be affected, but to a lesser extent.
Comment 1 Brion Vibber 2006-09-10 12:11:53 UTC
Fixed in r16465

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