From: Alan Third <alan@idiocy.org>
To: Pascal Quesseveur <pquessev@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
56182@debbugs.gnu.org
Subject: bug#56182: 28.1; Display of SVG file with transparent background is incorrect
Date: Sat, 9 Sep 2023 13:09:44 +0100 [thread overview]
Message-ID: <ZPxgiAZ/cwH615Jh@idiocy.org> (raw)
In-Reply-To: <82pmis3a7g.fsf@gmail.com>
On Tue, Jun 28, 2022 at 08:38:11PM +0200, Pascal Quesseveur wrote:
> From what I understand the way to deal with background transparency of
> SVG images has changed in version 28.1 in function svg_load_image
> (comments about opacity are still there but I think they are
> irrelevant). Now the SVG image is encapsulated in another SVG image in
> which a rect element is defined with the background color of the
> image.
>
> I don't know why it doesn't work on the W10 computers I work on. I
> don't know if the problem comes from this modificatino either. It
> seems to me that the displayed color is BGR instead of RGB and the
> screen gamma correction is not applied.
Apologies for leaving this so long.
Is this an issue for *all* Windows machines? The documentation for
COLORREF[1] suggests that Windows uses a byte format for *all* colours
of 0x00BBGGRR, which would explain this, but I thought it worked fine
on some machines?
Alternatively, I'm looking at the wrong documentation, however it
appears the code in w32term.c uses this COLORREF for colours as
defined in a face, so I think it's the right thing.
If this is right and Windows always uses this format, all we need to
do is format the SVG colour differently on Windows.
[1] https://learn.microsoft.com/en-gb/windows/win32/gdi/colorref?redirectedfrom=MSDN
--
Alan Third
next prev parent reply other threads:[~2023-09-09 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 6:30 bug#56182: 28.1; Display of SVG file with transparent background is incorrect Pascal Quesseveur
2022-06-24 9:23 ` Lars Ingebrigtsen
2022-06-24 12:18 ` Pascal Quesseveur
2022-06-25 9:25 ` Eli Zaretskii
2022-06-25 16:32 ` Alan Third
2022-06-27 6:49 ` Pascal Quesseveur
2022-06-27 8:12 ` Pascal Quesseveur
2022-06-28 18:38 ` Pascal Quesseveur
2022-06-28 19:45 ` Alan Third
2022-06-29 2:26 ` Eli Zaretskii
2023-09-09 12:09 ` Alan Third [this message]
2023-09-11 19:10 ` Alan Third
2023-09-12 13:55 ` Corwin Brust
2023-09-12 14:22 ` Eli Zaretskii
2023-09-12 17:01 ` Corwin Brust
2023-09-12 14:19 ` Eli Zaretskii
2023-09-13 19:21 ` Alan Third
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=ZPxgiAZ/cwH615Jh@idiocy.org \
--to=alan@idiocy.org \
--cc=56182@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=pquessev@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).