Last modified: 2013-09-29 00:51:20 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 52043 - Use VipsScaler to scale large GIFs
Use VipsScaler to scale large GIFs
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
VipsScaler (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-25 18:48 UTC by Greg Grossmeier
Modified: 2013-09-29 00:51 UTC (History)
7 users (show)

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


Attachments

Comment 1 Bawolff (Brian Wolff) 2013-09-29 00:51:20 UTC
The vips I have locally doesn't support gif images. I think you can compile it with libMagick to use image magick's image loading routine, but then things probably aren't any memory efficient (Just a guess, haven't actually looked). On top of that, it seems doubtful it would support animation in gifs if it doesn't support the format natively. In any case this would all require much more investigation. On top of that gifs usually aren't a problem format for failing to render (Failing to render more than one frame is a common problem). I feel like to make this actually work as we want, we'd probably have to add things to vips to support gif.

We have much more pressing formats to start using VIPS with anyhow, so changing priority -> low

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


Navigation
Links