From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: \201\236 appearing in emacs.desktop
Date: Sat, 08 Jul 2017 18:29:46 +0300 [thread overview]
Message-ID: <8360f3kkut.fsf@gnu.org> (raw)
In-Reply-To: <20170708152050.GB29492@tuxteam.de> (tomas@tuxteam.de)
> Date: Sat, 8 Jul 2017 17:20:50 +0200
> From: tomas@tuxteam.de
> Cc: help-gnu-emacs@gnu.org
>
> > --8<---------------cut here---------------start------------->8---
> > Coding system for saving this buffer:
> > U -- utf-8-unix (alias: mule-utf-8-unix)
> [...]
> > --8<---------------cut here---------------end--------------->8---
>
> Pretty unsurprising. Sorry I can't say where those \201\236 are
> coming from. Emacs is able to transparently represent "byte values"
> which would be an encoding error within an otherwise UTF-8 encoded
> buffer (actually it uses an extension of UTF-8 for that). To display
> that, it resorts to those octal escapes, \nnn.
\201 will not happen in UTF-8 encodings. It most probably comes from
some encoding like Shift-JIS or whatever.
Perhaps the OP should show more of the corrupted file (use
find-file-literally to avoid corruption by decoding), it could give
more hints.
next prev parent reply other threads:[~2017-07-08 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 8:46 \201\236 appearing in emacs.desktop Sharon Kimble
2017-07-08 11:19 ` tomas
2017-07-08 12:23 ` Sharon Kimble
2017-07-08 15:20 ` tomas
2017-07-08 15:29 ` Eli Zaretskii [this message]
2017-07-08 17:02 ` Sharon Kimble
2017-07-09 9:56 ` tomas
2017-07-09 16:49 ` Sharon Kimble
2017-07-09 19:48 ` tomas
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=8360f3kkut.fsf@gnu.org \
--to=eliz@gnu.org \
--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).