From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 36315@debbugs.gnu.org
Subject: bug#36315: 27.0.50; SVG transparency handling is inaccurate
Date: Tue, 02 Jul 2019 05:32:41 +0300 [thread overview]
Message-ID: <83h885dv3q.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBcXmECx9v5Czu9LsE9AiFUuoCz0nBdMJprO7FmU23WQ3w@mail.gmail.com> (message from Pip Cet on Mon, 1 Jul 2019 16:25:49 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Mon, 1 Jul 2019 16:25:49 +0000
> Cc: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>, 36315@debbugs.gnu.org
>
> On Mon, Jul 1, 2019 at 2:12 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > So on balance, I prefer the original fix, which was much simpler.
> > Assuming it fixed the problem, of course (I didn't try).
>
> I prefer the other fix, for what it's worth, probably for the same
> reasons you don't: it makes it easier to add more fancy features
> editors don't need, such as true image transparency and SVG
> animations. librsvg has painful limitations such as not allowing us to
> pass in a foreground color (it simply uses black), but maybe that'll
> be better one day, and then this patch would make it easier for us to
> use the new features.
>
> The fix looks more complicated than it is because it changes
> indentation (for the better) and removes a misleading comment.
Are we talking about the same "other fix"? I was talking about the
one that uses Cairo calls directly. Changes in indentation is not
what makes it more complex than the patch you suggested.
next prev parent reply other threads:[~2019-07-02 2:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 20:26 bug#36315: 27.0.50; SVG transparency handling is inaccurate Pip Cet
2019-06-20 20:46 ` Pip Cet
2019-06-22 20:56 ` Alan Third
2019-06-24 7:56 ` YAMAMOTO Mitsuharu
2019-06-24 8:17 ` YAMAMOTO Mitsuharu
2019-06-24 16:24 ` Pip Cet
2019-06-24 17:41 ` Eli Zaretskii
2019-06-24 23:06 ` YAMAMOTO Mitsuharu
2019-06-25 16:54 ` Eli Zaretskii
2019-06-25 18:44 ` Alan Third
2019-06-25 18:55 ` Eli Zaretskii
2019-06-25 23:48 ` YAMAMOTO Mitsuharu
2019-06-26 0:12 ` Lars Ingebrigtsen
2019-06-26 15:57 ` Eli Zaretskii
2019-06-27 3:33 ` YAMAMOTO Mitsuharu
2019-06-27 14:16 ` Eli Zaretskii
2019-06-30 6:12 ` YAMAMOTO Mitsuharu
2019-06-30 14:26 ` Eli Zaretskii
2019-07-01 3:46 ` YAMAMOTO Mitsuharu
2019-07-01 14:11 ` Eli Zaretskii
2019-07-01 16:25 ` Pip Cet
2019-07-02 2:32 ` Eli Zaretskii [this message]
2019-07-02 9:46 ` YAMAMOTO Mitsuharu
2019-07-02 14:26 ` Eli Zaretskii
2020-08-21 13:04 ` Lars Ingebrigtsen
2020-08-21 15:04 ` Alan Third
2020-08-22 13:29 ` Lars Ingebrigtsen
2020-08-22 16:00 ` Alan Third
2020-12-18 0:49 ` bug#36315: Incorrect SVG color Qiantan Hong
2020-12-18 15:00 ` Alan Third
2020-12-18 15:47 ` Qiantan Hong
2020-12-18 15:51 ` Qiantan Hong
2020-12-18 16:42 ` Qiantan Hong
2020-12-18 18:04 ` Alan Third
2020-12-18 18:16 ` Alan Third
2020-12-19 0:24 ` Lars Ingebrigtsen
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=83h885dv3q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36315@debbugs.gnu.org \
--cc=pipcet@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).