From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65299@debbugs.gnu.org, awrhygty@outlook.com
Subject: bug#65299: 29.1; ZIP archived WEBP images can not be displayed correctly
Date: Fri, 1 Sep 2023 22:24:40 +0200 [thread overview]
Message-ID: <CADwFkm=JZXduWPy3FXobcCizRs6WxkaS8bDicd49fOg85S9yWg@mail.gmail.com> (raw)
In-Reply-To: <83fs4k9yx0.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > From: awrhygty@outlook.com
> > Cc: 65299@debbugs.gnu.org
> > Date: Tue, 15 Aug 2023 22:05:36 +0900
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > You need to say
> > >
> > > C-x RET c no-conversion RET RET
> > >
> > > to open such files from a zip archive.
> > >
> > > Determining the right coding system when opening files from ZIP
> > > archives is a tricky issue, and frequently needs forcing a certain
> > > encoding manually. I don't know how to do better in general, what
> > > with all the possible sources of the files and their encodings. A Zip
> > > archive can include files from Unix systems or from Windows, and we
> > > unzip by running the 'unzip' program. So the usual defaults for
> > > guessing the encoding don't really work.
> >
> > At least modifying 'auto-coding-alist takes effect.
>
> OK, but that cannot be done by default, since the right encoding is
> not known in advance.
So is this a wontfix, then?
next prev parent reply other threads:[~2023-09-01 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 4:02 bug#65299: 29.1; ZIP archived WEBP images can not be displayed correctly awrhygty
2023-08-15 11:05 ` Eli Zaretskii
2023-08-15 13:05 ` awrhygty
2023-08-15 14:13 ` Eli Zaretskii
2023-09-01 20:24 ` Stefan Kangas [this message]
2023-09-02 6:20 ` Eli Zaretskii
2023-09-02 16:34 ` Stefan Kangas
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='CADwFkm=JZXduWPy3FXobcCizRs6WxkaS8bDicd49fOg85S9yWg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=65299@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
--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 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.