From: Jason Rumney <jasonrumney@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
kzhr@d1.dion.ne.jp, 6918@debbugs.gnu.org
Subject: bug#6918: Colors of xbm image are swapped on Windows
Date: Fri, 27 Sep 2019 05:38:54 +0800 [thread overview]
Message-ID: <CAFa88WnUJw--zQe98XCNow20TSeUhiM+2gWiYxjdaFwB3xRdfg@mail.gmail.com> (raw)
In-Reply-To: <838sqalwy3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
I wouldn't call myself an expert on images on Windows. I basically got it
working through trial and error, and from the looks of that history there
may have been bugs fixed later that invalidated some early decisions. Most
of the monchrome Emacs icons were PBM IIRC, so XBM may not have had a lot
of testing on Windows over the past 12 years.
On Fri, 27 Sep 2019, 4:44 AM Eli Zaretskii, <eliz@gnu.org> wrote:
> > From: Lars Ingebrigtsen <larsi@gnus.org>
> > Cc: jasonr@gnu.org, jasonrumney@gmail.com, kzhr@d1.dion.ne.jp,
> > 6918@debbugs.gnu.org
> > Date: Thu, 26 Sep 2019 20:34:15 +0200
> >
> > >> /* Windows convention for mono bitmaps is black = background,
> > >> white = foreground. */
> > >> SetTextColor (new_img_dc, background);
> > >> SetBkColor (new_img_dc, foreground);
> > >>
> > >> Can anybody who works on Windows say whether this is the case?
> > >
> > > Say whether WHAT is the case?
> >
> > That the convention in Windows is as described in the comment above.
>
> No clue, sorry.
>
[-- Attachment #2: Type: text/html, Size: 1823 bytes --]
next prev parent reply other threads:[~2019-09-26 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 8:42 bug#6918: Colors of xbm image are swapped on Windows Kazuhiro Ito
2019-09-26 17:59 ` Lars Ingebrigtsen
2019-09-26 18:31 ` Eli Zaretskii
2019-09-26 18:34 ` Lars Ingebrigtsen
2019-09-26 18:44 ` Eli Zaretskii
2019-09-26 21:38 ` Jason Rumney [this message]
2019-09-27 5:30 ` Eli Zaretskii
2019-10-10 6:59 ` Jason Rumney
2019-10-10 8:17 ` Eli Zaretskii
2021-11-05 13:26 ` Stefan Kangas
2021-11-06 11:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFa88WnUJw--zQe98XCNow20TSeUhiM+2gWiYxjdaFwB3xRdfg@mail.gmail.com \
--to=jasonrumney@gmail.com \
--cc=6918@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kzhr@d1.dion.ne.jp \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.