Bug#923070: eom: can't handle wrong file extensions
Package: eom
Version: 1.20.2-1+b1
Severity: wishlist
Hi!
Unlike most other programs, eom insists that a file ending in ".jpeg" is
indeed a JPEG, one ending in ".png" is indeed a PNG, etc. That's the
"proper" way, right. Alas, with eom's "competition" being more forgiving,
most people don't know the difference and thus mislabelling is rampant.
I see JPEG<->PNG confusion pretty often, and every single time I saw a
webp image (not yet supported by eom), it had a .jpg or .jpeg extension.
Thus, could you please either:
* give the proper image type in error message (rather than just "file is
corrupted")
* just display the image, without any remark
* mention the error but display the image
Meow!
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: arm64 (aarch64)
Kernel: Linux 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages eom depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii eom-common 1.20.2-1
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-7
ii libcairo-gobject2 1.16.0-3
ii libcairo2 1.16.0-3
ii libdbus-1-3 1.12.12-1
ii libdbus-glib-1-2 0.110-4
ii libexempi8 2.5.0-2
ii libexif12 0.6.21-5.1
ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7
ii libgirepository-1.0-1 1.58.3-2
ii libgl1 1.1.0-1
ii libglib2.0-0 2.58.3-1
ii libgtk-3-0 3.24.5-1
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-3
ii libmate-desktop-2-17 1.20.4-2
ii libpango-1.0-0 1.42.4-6
ii libpangocairo-1.0-0 1.42.4-6
ii libpeas-1.0-0 1.22.0-4
ii librsvg2-2 2.44.10-1
ii librsvg2-common 2.44.10-1
ii libstartup-notification0 0.12-6
ii libx11-6 2:1.6.7-1
ii libxml2 2.9.4+dfsg1-7+b3
ii mate-desktop-common 1.20.4-2
ii shared-mime-info 1.10-1
ii zlib1g 1:1.2.11.dfsg-1
eom recommends no packages.
eom suggests no packages.
-- no debconf information
Reply to: