From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: pquessev@gmail.com, larsi@gnus.org, 56182@debbugs.gnu.org
Subject: bug#56182: 28.1; Display of SVG file with transparent background is incorrect
Date: Wed, 29 Jun 2022 05:26:48 +0300 [thread overview]
Message-ID: <83czes6w7r.fsf@gnu.org> (raw)
In-Reply-To: <YrtaTSHFhHK0NASC@idiocy.org> (message from Alan Third on Tue, 28 Jun 2022 20:45:17 +0100)
> Date: Tue, 28 Jun 2022 20:45:17 +0100
> From: Alan Third <alan@idiocy.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
> 56182@debbugs.gnu.org
>
> > 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. For what it's worth I managed
> > to work around the problem in lisp. With version 27.1 I had
> > implemented an advice to improve the taking into account of the
> > background color in the style of SVG file. So I extended that advice
> > to solve my problem.
>
> *scratches head*
>
> Eli, do we need to decode the "unsigned long" colours in a special way
> on Windows? It could be I've missed a vital step and am using them
> incorrectly. So if the colour is defined in BGR byte order, and I then
> use the unsigned long directly in a printf("#%06X", colour) style,
> that's likely to be wrong, yes?
I don't think I understand what colors you had in mind here. Can you
walk me through the relevant code? I'm not sure I will have an
answer, but I could at least try things.
Thanks.
next prev parent reply other threads:[~2022-06-29 2:26 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 [this message]
2023-09-09 12:09 ` Alan Third
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=83czes6w7r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56182@debbugs.gnu.org \
--cc=alan@idiocy.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).