aboutsummaryrefslogtreecommitdiffstats
path: root/Gemfile.lock
diff options
context:
space:
mode:
authorHarald Eilertsen <haraldei@anduin.net>2020-05-08 10:20:53 +0200
committerHarald Eilertsen <haraldei@anduin.net>2020-05-08 10:20:53 +0200
commitb493cfafd77e2bdb6e8949fc3bc6e73e4fbed21d (patch)
tree0cf42a7f4b7c450ce56671ec9311c51fc8042a8c /Gemfile.lock
parentfeafaebdf7ad783b2b562356a08b410ffeddce14 (diff)
downloadhmnoweb-b493cfafd77e2bdb6e8949fc3bc6e73e4fbed21d.tar.gz
hmnoweb-b493cfafd77e2bdb6e8949fc3bc6e73e4fbed21d.tar.bz2
hmnoweb-b493cfafd77e2bdb6e8949fc3bc6e73e4fbed21d.zip
Banners: Don't try to resize gifs.deploy-20200508
ImageMagick does not handle resizing of animated gifs wery well. Optimized gifs will usually have individual sizes for each frame, only containing the actually changed image data. Each frame also have an offset from the origin. When ImageMagick tries to resize such an image, the offsets gets messed up and the result looks rather terrible. There's ways to handle this in ImageMagick, by first making all frames the same size (`convert -coalesce ...`) then resize (`convert -resize ...`) and finally optimize the gif again (`convert -layers Optimize ...`). However, this is a bit too much to handle when trying to download the animation, so it should be done on or before upload. For now, I think doing it offline before upload should be good enough. This _requires_ though, that the animation has the correct dimensions before upload!
Diffstat (limited to 'Gemfile.lock')
0 files changed, 0 insertions, 0 deletions