all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: "H.-J. Heitländer" <Heiner.Heitlaender@posteo.de>
Cc: Stephen Berman <stephen.berman@gmx.net>,
	gnu emacs <help-gnu-emacs@gnu.org>
Subject: Re: emacs 30.5.0 editing epub
Date: Thu, 16 Mar 2023 22:23:42 +0700	[thread overview]
Message-ID: <CAP_d_8W8XeuUmEurTPw3mMSc6ku90xDv9y_czx2MJyGKJ8MVTA@mail.gmail.com> (raw)
In-Reply-To: <74d91d8b-ac3c-9463-4334-9c1db8df7c13@posteo.de>

On Thu, 16 Mar 2023 at 20:17, H.-J. Heitländer
<Heiner.Heitlaender@posteo.de> wrote:

> kill buffer up to the top epub
>
> reopen epub
>
> open epub subfile (...html)
>
> C-x RET r ... utf-8
>
> in minibufer: Revert buffer from file xxx.html? (y or n)
>
> Answer: y
>
> Minibuffer: Cannot revert noexistent file xxx.html

You keep mentioning “editing epub”. Are you even sure it’s supposed to work?

An EPUB file is a zip archive, typically containing XHTML pages and
some metadata. Emacs covers some basic scenarios where you can browse
the archive, visit files inside, even edit and save them (and they get
re-compressed and updated in the archive).

Reverting, on the other hand, does not work, probably because of the
way archive-mode is implemented. So when it picks the wrong encoding,
you cannot fix it by reverting.

You could probably achieve better results if you first extract the
contents of the EPUB archive into a real directory on your file
system, then edit files there. If necessary, re-pack the modified
files.

I see ‘archive--extract-file’ initially sets the coding system to
‘no-conversion’, possibly because it needs that for decompression. It
is supposed to re-decide on a coding system later in
‘archive-set-buffer-as-visiting-file’, but for some reason it keeps
‘no-conversion’ in your case.



  reply	other threads:[~2023-03-16 15:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 18:35 emacs 30.5.0 editing epub H.-J. Heitländer
2023-03-16  5:05 ` Michael Heerdegen
2023-03-16  6:57   ` H.-J. Heitländer
2023-03-17  0:44     ` Michael Heerdegen
2023-03-17  1:13     ` Michael Heerdegen
2023-03-19 21:23       ` editing a PDF [Re: emacs 30.5.0 editing epub] gebser
2023-03-19 23:59         ` Michael Heerdegen
2023-03-20  7:15           ` gebser
2023-03-21  0:31             ` Michael Heerdegen
2023-03-21  6:28             ` Yuri Khan
2023-03-21  6:38               ` Emanuel Berg
2023-03-22 16:32                 ` Yuri Khan
2023-03-22 18:48                   ` Bob Newell
2023-03-23  9:36                     ` Jean Louis
2023-03-23 23:00                       ` Bob Newell
2023-03-23  9:13                   ` Jean Louis
2023-03-23 10:37                   ` Michael Heerdegen
2023-03-23 20:13                     ` Emanuel Berg
2023-03-23 20:07                   ` Emanuel Berg
2023-03-21 11:51               ` Ulrich Deiters
2023-03-21 21:57                 ` gebser
2023-03-21 22:55                   ` Ulrich Deiters
2023-03-22  1:56                     ` Michael Heerdegen
2023-03-22  8:26                     ` FOSS replacement for PDF [Re: editing a PDF] gebser
2023-03-22  9:18                       ` Yuri Khan
2023-03-23  9:21                         ` Jean Louis
2023-03-23  9:49                           ` Yuri Khan
2023-03-23 10:53                             ` Gregory Heytings
2023-03-28 11:28                     ` editing a PDF [Re: emacs 30.5.0 editing epub] Michael Heerdegen
2023-03-22  7:03                   ` Jean Louis
2023-03-22 15:20                     ` gebser
2023-03-16  9:22 ` emacs 30.5.0 editing epub Stephen Berman
2023-03-16 13:16   ` H.-J. Heitländer
2023-03-16 15:23     ` Yuri Khan [this message]
2023-03-16 16:54       ` H.-J. Heitländer
2023-03-16 18:58         ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-20 21:50           ` emacs 30.5.0 editing epub - finishing remark H.-J. Heitländer

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=CAP_d_8W8XeuUmEurTPw3mMSc6ku90xDv9y_czx2MJyGKJ8MVTA@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=Heiner.Heitlaender@posteo.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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.