From: Mathias Dahl <brakjoller@gmail.com>
To: gnu-emacs-bug@moderators.individual.net
Subject: Re: image-dired does not rotate the original image
Date: Tue, 24 Jul 2007 08:52:59 +0200 [thread overview]
Message-ID: <ubqe270ok.fsf@gmail.com> (raw)
In-Reply-To: mailman.3767.1185123740.32220.bug-gnu-emacs@gnu.org
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> As I mentioned earlier, jpegtran does lossless rotation, something
> `convert' cannot do (or could not the last time I checked).
>
> does this limitation also exist w/ mogrify(1) (or alternatively gm(1)
> subcommand mogrify)?
I don't know. What I do know is that `convert' makes a lossy rotation
of JPEGs. I found this out myself while creating Tumme; while in the
thumbnail buffer, rotate a thumbnail over and over again. Because of
the small size you soon begin to see changes.
> cp foo.jpg foo.orig.jpg
> gm mogrify -rotate -90 foo.jpg
> gm mogrify -rotate 90 foo.jpg
> cmp foo.jpg foo.orig.jpg
>
> however, doing the above (even w/ "-quality 100" for the mogrify commands)
> always results in cmp(1) noting a difference, even though visually i could
> not tell.
If you do that in a loop, say ten or more times, maybe you will start
to see a difference (save the original and compare it visually).
> i'm not a graphics format expert; could you suggest a better
> way to check for loss?
How about rotating the image in Gimp, for comparison?
Maybe there should be an option in `image-dired' to allow lossy
rotation, so that people who accept that do not need to have
`jpegtran'?
/Mathias
next prev parent reply other threads:[~2007-07-24 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 12:02 image-dired does not rotate the original image Dieter Wilhelm
2007-07-22 12:50 ` Mathias Dahl
2007-07-22 13:34 ` Dieter Wilhelm
2007-07-22 13:52 ` Mathias Dahl
2007-07-22 17:01 ` Thien-Thi Nguyen
[not found] ` <mailman.3767.1185123740.32220.bug-gnu-emacs@gnu.org>
2007-07-24 6:52 ` Mathias Dahl [this message]
2007-07-24 22:50 ` Dieter Wilhelm
2007-07-25 7:25 ` Mathias Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ubqe270ok.fsf@gmail.com \
--to=brakjoller@gmail.com \
--cc=gnu-emacs-bug@moderators.individual.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).