From: Stefan Kangas <stefan@marxist.se>
To: Alan Third <alan@idiocy.org>
Cc: ynyaaa@gmail.com, Lars Ingebrigtsen <larsi@gnus.org>,
47040@debbugs.gnu.org
Subject: bug#47040: 27.1; PNG binary transparency is ignored
Date: Sun, 31 Oct 2021 07:49:16 -0700 [thread overview]
Message-ID: <CADwFkm=5yHaFc=LFWR_p1x2mV3GrjfoZKcZSEihneOd2O-Ra3g@mail.gmail.com> (raw)
In-Reply-To: <YElEwZTerbLMFGR9@breton.holly.idiocy.org> (Alan Third's message of "Wed, 10 Mar 2021 22:14:25 +0000")
Alan Third <alan@idiocy.org> writes:
> I see the same on NS, so it must be something wrong with the libpng
> support code. Although I don't know why Lars doesn't see it on Debian.
>
> I wonder if it's related to image.c:6909
>
> # ifdef PNG_tRNS_SUPPORTED
>
> It looks like that is not defined here... I don't really understand
> what the png code is doing with transparency.
That was added in commit 8826beaf0066. I think this if this is
undefined in your case, I think it could be a problem with your libpng
build, as Paul alludes to here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37153#71
As far as I can tell from here,
https://github.com/mitsuba-renderer/libpng/search?q=PNG_tRNS_SUPPORTED
and here,
https://github.com/mitsuba-renderer/libpng/blob/master/scripts/pnglibconf.h.prebuilt
libpng is built with PNG_tRNS_SUPPORTED by default. So why is your
libpng not built with that?
next prev parent reply other threads:[~2021-10-31 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 10:45 bug#47040: 27.1; PNG binary transparency is ignored ynyaaa
2021-03-10 15:05 ` Lars Ingebrigtsen
2021-03-10 15:14 ` Eli Zaretskii
2021-03-10 22:14 ` Alan Third
2021-03-11 16:53 ` Lars Ingebrigtsen
2021-10-31 14:49 ` Stefan Kangas [this message]
2022-06-20 9:46 ` 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='CADwFkm=5yHaFc=LFWR_p1x2mV3GrjfoZKcZSEihneOd2O-Ra3g@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=47040@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=larsi@gnus.org \
--cc=ynyaaa@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).