all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: awrhygty@outlook.com
Cc: 67926@debbugs.gnu.org
Subject: bug#67926: 29.1; fail to extract ZIP subfile named with [...]
Date: Thu, 28 Dec 2023 16:06:14 +0200	[thread overview]
Message-ID: <83sf3m776x.fsf@gnu.org> (raw)
In-Reply-To: <TYZPR01MB3920ABDD666D070CB37CE7ECC39EA@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (awrhygty@outlook.com)

> From: awrhygty@outlook.com
> Cc: 67926@debbugs.gnu.org
> Date: Thu, 28 Dec 2023 22:09:23 +0900
> 
> > Btw, your suggested changes required gzip and bunzip2 as external
> > programs to support the 2 most popular compression methods.  Why
> > should we assume these are available more widely than unzip,
> > especially on Windows?
> 
> When I installed UnxUtils years ago, it had bzip2 and gzip, but not
> unzip nor zip. Now I download it again, it has unzip and zip.

Windows systems don't come with UnxUtils installed anyway.

> My interest is how to avoid naming problems.
> There are more difficulties in Japanese.
> Japanese characters in file names are normally encoded in cp932.
> Encoded characters may have '[', '\' or ']' as a second byte.
>   (encode-coding-string "ゼソゾ" 'cp932)
>   => "\203[\203\\\203]"
> Subfiles of such names can not be extracted normally.

I don't think we can solve this in Emacs: non-ASCII file names in zip
archives are a mess, even before you consider the fact that zip
archives are frequently moved between systems.  For starters, how can
one know in advance what is the encoding of file names in an arbitrary
zip archive?  This will bite you even if we do everything in Emacs,
and even if someone does submit patches to implement all the
compression methods.





  reply	other threads:[~2023-12-28 14:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 11:23 bug#67926: 29.1; fail to extract ZIP subfile named with [...] awrhygty
2023-12-23 10:16 ` Eli Zaretskii
2023-12-23 11:47   ` Andreas Schwab
2023-12-23 11:58     ` Eli Zaretskii
2023-12-26 14:51   ` awrhygty
2023-12-26 17:25     ` Eli Zaretskii
2023-12-27 14:36       ` awrhygty
2023-12-27 16:48         ` Eli Zaretskii
2023-12-28  0:38           ` awrhygty
2023-12-28  6:31             ` Eli Zaretskii
2023-12-28 13:09               ` awrhygty
2023-12-28 14:06                 ` Eli Zaretskii [this message]
2024-01-03 19:53                   ` awrhygty
2024-01-03 20:00                     ` Eli Zaretskii
2024-01-03 20:02                     ` Eli Zaretskii
2023-12-28 14:56       ` Eli Zaretskii
2024-01-04 10:46         ` 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=83sf3m776x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67926@debbugs.gnu.org \
    --cc=awrhygty@outlook.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 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.