From: Stephen Berman <stephen.berman@gmx.net>
To: "H.-J. Heitländer" <Heiner.Heitlaender@posteo.de>
Cc: gnu emacs <help-gnu-emacs@gnu.org>
Subject: Re: emacs 30.5.0 editing epub
Date: Thu, 16 Mar 2023 10:22:13 +0100 [thread overview]
Message-ID: <87pm99830a.fsf@gmx.net> (raw)
In-Reply-To: <df344350-16d8-b803-d90d-28abf9a3063c@posteo.de> ("H.-J. Heitländer"'s message of "Wed, 15 Mar 2023 18:35:55 +0000")
On Wed, 15 Mar 2023 18:35:55 +0000 H.-J. Heitländer <Heiner.Heitlaender@posteo.de> wrote:
> Hi there,
>
> trying to get my feet wet with emacs and lisp. ... well it seems I am
> drowning...
>
> The problem:
>
> I am editing epub archives and any saves that I am doing result in
>
> <snip>
>
> ***backtrace***
[...]
> For the moment I can live with that as in reality the epub is being saved.
>
> My problem is that from that moment on the display of the epub subfile
> (<name>.html) loses the utf-8 display. (oh, and every other file is being
> displayed in the same - wrong - way.)
>
> The content is shown as (example)
>
> <snip>
>
> \342\200\234Nicely done. Now let\342\200\231s get that equipment on
> board.\342\200\234 </p>
>
> </snip>
>
> It should have been shown as
>
> <snip>
>
> "Nicely done. Now let's get that equipment on board." </p>
>
> </snip>
>
> I searched the internet without any result. Don't know which part of
> documentation to read.
>
> Question: How do I switch the display back to show the contents in the
> expected way???
It looks like the buffer is being displayed in the raw-text coding
system (is the first character in the mode line "t"?). \342\200\234 is
the raw-byte sequence of the unicode character LEFT DOUBLE QUOTATION
MARK (#x201c) and \342\200\231 of RIGHT SINGLE QUOTATION MARK (#x2019).
Does typing `C-x RET r' and at the prompt entering `utf-8' and at the
next prompt `yes' fix the display?
Steve Berman
next prev parent reply other threads:[~2023-03-16 9:22 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 ` Stephen Berman [this message]
2023-03-16 13:16 ` emacs 30.5.0 editing epub H.-J. Heitländer
2023-03-16 15:23 ` Yuri Khan
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
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=87pm99830a.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=Heiner.Heitlaender@posteo.de \
--cc=help-gnu-emacs@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.
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).