all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Evgeny Zajcev <lg.zevlg@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: What is `image-compute-scaling-factor' for?
Date: Fri, 25 Dec 2020 12:12:14 -0500	[thread overview]
Message-ID: <jwvwnx5rez5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAO=W_ZrMj=-qNDAdV2tY1+YKN86vtN4=KAxHOqNS7m0i1F07YA@mail.gmail.com> (Evgeny Zajcev's message of "Fri, 25 Dec 2020 09:36:13 +0300")

> something new.  None of the software I've been using does so.  You can set
> any default font size in Mozilla/Chrome/Opera without affecting image
> sizes, but if you do "zoom-in", then everything zooms in, text and images.

I suspect this is comparing apples and oranges: images in HTML pages are
inserted via elements that provide additional information about the
intended size of the image, whereas the current ELisp API has no
such information so all we have to go on is the pixel size of the image,
which is fundamentally insufficient to do a good job.

IOW we ought to fix the APIs so that inserting an image has to come with
either a scaling factor or some size info expressed in "char-cells" or
"inches" or "percent of screen size" or "percent of window size" or some
such entity.


        Stefan




      reply	other threads:[~2020-12-25 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  9:30 What is `image-compute-scaling-factor' for? Evgeny Zajcev
2020-12-24 10:36 ` Eli Zaretskii
2020-12-24 10:52   ` Evgeny Zajcev
2020-12-24 11:07     ` tomas
2020-12-24 14:46     ` Eli Zaretskii
2020-12-24 17:12       ` Evgeny Zajcev
2020-12-25  5:17         ` Lars Ingebrigtsen
2020-12-25  6:10           ` Evgeny Zajcev
2020-12-25  6:15             ` Lars Ingebrigtsen
2020-12-25  6:36               ` Evgeny Zajcev
2020-12-25 17:12                 ` Stefan Monnier [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvwnx5rez5.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=lg.zevlg@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.