unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28824@debbugs.gnu.org
Subject: bug#28824: 26.0.90; display of pbm images broken?
Date: Sat, 14 Oct 2017 16:52:22 -0500	[thread overview]
Message-ID: <34582.83757.771697.23010@gargle.gargle.HOWL> (raw)
In-Reply-To: <83376mjjq7.fsf@gnu.org>

[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 1176 bytes --]

On Sat Oct 14 2017 Eli Zaretskii wrote:
> Works for me in Emacs 26.0.90 on MS-Windows.  I used PBM images from
> etc/images/ in the Emacs tree: does this fail to work for you with
> those images as well?

I need to apologize: the bug is not with pbm images, but with ppm
images.  (The tool I use to create them calls them pbm, but it gives
ppm, pgm or pbm files depending on the content of the image.)

Then I realized there seem to be different versions of ppm files.
If I use the imagemagick tool `convert' to convert
etc/images/home.pbm to a ppm file it gives me the attached file
home-1bit.ppm.  This one still displays fine.  But if I export this
file with gimp, it gives me the attached file home-8bit.ppm.  This
file illustrates the bug I am talking about.

The file names refer to the output from the imagemagick tool
`identify':

$ identify home*
home-1bit.ppm PPM 24x24 24x24+0+0 1-bit sRGB 1.84KB 0.000u 0:00.000
home-8bit.ppm PPM 24x24 24x24+0+0 8-bit sRGB 1.78KB 0.000u 0:00.000

PS: Visiting these files display them fine (according to the
modeline, this uses imagemagick).  The problem occurs with
insert-image which appears to process these files differently


[-- Attachment #2: home-1bit.ppm --]
[-- Type: application/octet-stream, Size: 1845 bytes --]

[-- Attachment #3: home-8bit.ppm --]
[-- Type: application/octet-stream, Size: 1780 bytes --]

  parent reply	other threads:[~2017-10-14 21:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14  2:10 bug#28824: 26.0.90; display of pbm images broken? Roland Winkler
2017-10-14  7:01 ` Eli Zaretskii
2017-10-14 15:01   ` Andy Moreton
2017-10-14 15:31     ` Eli Zaretskii
2017-10-14 18:16       ` Andy Moreton
2017-10-14 19:03         ` Andy Moreton
2017-10-14 19:16           ` Eli Zaretskii
2017-10-14 19:50             ` Andy Moreton
2017-10-14 20:15               ` Andy Moreton
2017-10-14 19:14         ` Eli Zaretskii
2017-10-14 21:52   ` Roland Winkler [this message]
2017-10-15 17:42     ` Andy Moreton
2017-10-15 18:49       ` Eli Zaretskii
2017-10-16  8:30         ` Paul Eggert
2017-10-16 15:11           ` Eli Zaretskii
2017-10-16 15:22             ` Roland Winkler

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=34582.83757.771697.23010@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=28824@debbugs.gnu.org \
    --cc=eliz@gnu.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 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).