From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Yuri Khan <yurivkhan@gmail.com>
Cc: slippycheeze@google.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 13:38:45 -0400 [thread overview]
Message-ID: <0e483a02-ca3d-256c-f136-15a5225c06ad@gmail.com> (raw)
In-Reply-To: <83a7houwlm.fsf@gnu.org>
On 2019-03-21 10:32, Eli Zaretskii wrote:
>> 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.
I was expecting something like the toolbars images, where the package author would provide both an SVG and a bitmap, and Emacs would use the latter when SVG support isn't available.
next prev parent reply other threads:[~2019-03-21 17:38 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
2019-03-21 17:32 ` Alex
2019-03-21 18:31 ` Eli Zaretskii
2019-03-21 17:38 ` Clément Pit-Claudel [this message]
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
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=0e483a02-ca3d-256c-f136-15a5225c06ad@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=eliz@gnu.org \
--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 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).