From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yurivkhan@gmail.com>
Cc: slippycheeze@google.com, cpitclaudel@gmail.com, emacs-devel@gnu.org
Subject: Re: What is the proper way to scale fringe-bitmaps for high-DPI displays?
Date: Thu, 21 Mar 2019 16:32:21 +0200 [thread overview]
Message-ID: <83a7houwlm.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8VJLwf007pzz1sCH_Vzc2y6YnOueafNCaKf2RLkQSMEKg@mail.gmail.com> (message from Yuri Khan on Thu, 21 Mar 2019 20:33:33 +0700)
> From: Yuri Khan <yurivkhan@gmail.com>
> Date: Thu, 21 Mar 2019 20:33:33 +0700
> Cc: Eli Zaretskii <eliz@gnu.org>, Clément Pit-Claudel <cpitclaudel@gmail.com>,
> emacs-devel <emacs-devel@gnu.org>
>
> * Migrate everything to SVG. Teach developers SVG is good, bitmaps are
> bad. Package developer provides a single vector image. Failure mode:
> developer is on a high DPI screen, makes a high-detail image, low DPI
> users complain “image is blurry”.
The failure mode that bothers me much more is that Emacs without SVG
support will be unable to show the standard fringe indicators.
In general, having the basic Emacs functionality depend on image
libraries is a non-starter, IMO.
> * Keep bitmaps and upscale them for high DPI. Package developer
> provides a single bitmap image. Failure mode 1: Nearest neighbor
> upscaling looks ugly at non-integer factors. Failure mode 2: all other
> upscaling algorithms look ugly pretty much always.
Is this worse than the current situation?
> * Keep bitmaps and downscale them for low DPI. Package developer
> provides a single, fairly large bitmap image. Failure mode: small
> details get lost on low resolutions, image looks blurry.
Is this worse than the current situation?
> * Migrate to multi-resolution bitmaps. Package developer has to
> provide multiple bitmaps. Failure mode 1: Nobody knows what sizes they
> need. Failure mode 2: Some will only include one for the low DPI. This
> can be combined with up/downscaling, trading the corresponding failure
> modes around.
Is this worse than the current situation?
next prev parent reply other threads:[~2019-03-21 14:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 14:55 What is the proper way to scale fringe-bitmaps for high-DPI displays? Clément Pit-Claudel
2019-03-20 17:32 ` Eli Zaretskii
2019-03-20 19:34 ` Clément Pit-Claudel
2019-03-20 19:44 ` Eli Zaretskii
2019-03-20 20:05 ` Clément Pit-Claudel
2019-03-20 20:17 ` Eli Zaretskii
2019-03-20 21:17 ` Clément Pit-Claudel
2019-03-21 3:32 ` Eli Zaretskii
2019-03-21 11:43 ` Daniel Pittman
2019-03-21 13:33 ` Yuri Khan
2019-03-21 14:32 ` Eli Zaretskii [this message]
2019-03-21 17:32 ` Alex
2019-03-21 18:31 ` Eli Zaretskii
2019-03-21 17:38 ` Clément Pit-Claudel
2019-03-21 18:33 ` Eli Zaretskii
2019-03-21 17:40 ` Clément Pit-Claudel
2019-03-20 19:37 ` Clément Pit-Claudel
2019-03-21 15:24 ` Dmitry Gutov
2019-03-21 16:02 ` Eli Zaretskii
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=83a7houwlm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=slippycheeze@google.com \
--cc=yurivkhan@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.