From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: alan@idiocy.org, lg.zevlg@gmail.com, stefankangas@gmail.com,
emacs-devel@gnu.org
Subject: Re: Image transformation filter for upscaled images
Date: Tue, 09 Mar 2021 18:04:59 +0100 [thread overview]
Message-ID: <87h7lkl0lg.fsf@gnus.org> (raw)
In-Reply-To: <83y2ewp9k6.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Mar 2021 18:37:45 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> There's no single value that will give good results in all cases.
>> Adding a variable to control the default is all well and good, but it's
>> not sufficient.
>
> Neither a variable nor an image attribute? (I suggested both.) Then
> what would you suggest to do to resolve this?
Sorry; missed that you also mentioned an image attribute, which would
be fine.
Thinking a bit more about this, I wonder whether a general solution is
kinda-sorta possible anyway. That is, having a function that returns
what algorithm to use. We normally want shrinking the image to always
use `best', and enlarging an image slightly to use `good' or `best'
(that's the issue with doc-view, I think? we're rendering at one size
and then enlarging it on HiDPI screens? I haven't actually debugged
it), and enlarging more than (say) 3x in size to use nearest
neighbour...
Having a variable (that can be a function that returns the algo to
use, or be one of the symbols) would allow us to experiment with this
more easily and see whether we can come up with something that works for
most people out of the box.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-09 17:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 19:12 Image transformation filter for upscaled images Evgeny Zajcev
2021-03-07 20:45 ` Alan Third
2021-03-07 22:35 ` Evgeny Zajcev
2021-03-07 23:27 ` Stefan Kangas
2021-03-08 0:42 ` Evgeny Zajcev
2021-03-08 2:31 ` Stefan Kangas
2021-03-08 13:34 ` Eli Zaretskii
2021-03-08 13:31 ` Eli Zaretskii
2021-03-08 18:58 ` Alan Third
2021-03-08 19:18 ` Lars Ingebrigtsen
2021-03-08 21:27 ` Alan Third
2021-03-08 21:31 ` Lars Ingebrigtsen
2021-03-08 21:59 ` Alan Third
2021-03-09 8:34 ` Evgeny Zajcev
2021-03-09 9:28 ` Alan Third
2021-03-09 9:46 ` Evgeny Zajcev
2021-03-09 14:16 ` Stefan Monnier
2021-03-09 13:09 ` Eli Zaretskii
2021-03-09 13:48 ` Evgeny Zajcev
2021-03-09 13:59 ` Lars Ingebrigtsen
2021-03-09 16:37 ` Eli Zaretskii
2021-03-09 17:04 ` Lars Ingebrigtsen [this message]
2021-03-09 18:01 ` Eli Zaretskii
2021-03-10 4:23 ` Yuri Khan
2021-03-10 14:44 ` Lars Ingebrigtsen
2021-03-09 13:16 ` Lars Ingebrigtsen
2021-03-09 13:50 ` Dov Grobgeld
2021-03-09 18:16 ` Alan Third
2021-03-09 18:12 ` Alan Third
2021-03-09 22:31 ` Basil L. Contovounesios
2021-03-09 23:59 ` Stefan Monnier
2021-03-10 13:37 ` Alan Third
2021-03-10 14:49 ` Lars Ingebrigtsen
2021-03-10 21:45 ` Alan Third
2021-03-11 16:53 ` Lars Ingebrigtsen
2021-03-12 1:38 ` Lars Ingebrigtsen
2021-03-12 2:01 ` Evgeny Zajcev
2021-03-12 18:32 ` Alan Third
2021-03-08 20:05 ` Evgeny Zajcev
2021-03-08 21:29 ` Alan Third
2021-03-08 13:27 ` Eli Zaretskii
2021-03-07 23:12 ` Stefan Monnier
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=87h7lkl0lg.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lg.zevlg@gmail.com \
--cc=stefankangas@gmail.com \
/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).