From: Angelo Graziosi <angelo.g0@libero.it>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Zipped image file
Date: Sat, 7 Sep 2019 00:59:13 +0200 (CEST) [thread overview]
Message-ID: <756926190.471306.1567810753197@mail1.libero.it> (raw)
In-Reply-To: <ee7359e5-adcb-319a-3feb-660f004b25c8@cs.ucla.edu>
> Il 6 settembre 2019 alle 23.24 Paul Eggert ha scritto:
>
>
> On 9/6/19 2:04 PM, Angelo Graziosi wrote:
> > Suppose one uses bzip2 to compress a PNG file, foo.png ---> foo.png.bzip2. Visiting this file, Emacs says that cannot display the image because cannot determine the image type.
>
> I see similar symptoms, but the display works as expected if the file is
> named foo.png.bz2. Is the extension '.bzip2' popular? I generally see
> just '.bz2'.
There was a mistake: read 'foo.png.bzip2' == 'foo.png.bz2' in the above text.
Here both foo.png.bz2 and foo.png.bzip2 produce almost the same result: only 'garbage' is displayed, not the PNG image.
Anyway, the .bz2 version is decompressed but not the .bzip2. I have checked this also with a text file: foo.txt.bz2 is displayed correctly a fully readable; foo.txt.bzip2 is displayed as 'garbage' (should have seen .bzip2 files somewhere...).
BTW, I tested this both on Windows build and GNU/Linux (cairo build).
If this is to be expected, it is useless to file a bug report.
next prev parent reply other threads:[~2019-09-06 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 21:04 Zipped image file Angelo Graziosi
2019-09-06 21:24 ` Paul Eggert
2019-09-06 22:59 ` Angelo Graziosi [this message]
2019-09-07 10:21 ` Eli Zaretskii
2019-09-07 10:39 ` Paul Eggert
2019-09-07 11:05 ` Eli Zaretskii
2019-09-07 12:03 ` Paul Eggert
2019-09-07 12:14 ` Eli Zaretskii
2019-09-07 12:34 ` Eli Zaretskii
2019-09-07 11:49 ` Angelo Graziosi
2019-09-07 14:36 ` Stefan Monnier
2019-09-07 17:15 ` Paul Eggert
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=756926190.471306.1567810753197@mail1.libero.it \
--to=angelo.g0@libero.it \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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 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.