From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: \201\236 appearing in emacs.desktop Date: Sat, 08 Jul 2017 18:29:46 +0300 Message-ID: <8360f3kkut.fsf@gnu.org> References: <87bmovpb8c.fsf@skimble.plus.com> <20170708111918.GF18691@tuxteam.de> <87h8ynm81x.fsf@skimble.plus.com> <20170708152050.GB29492@tuxteam.de> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1499527830 15494 195.159.176.226 (8 Jul 2017 15:30:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 8 Jul 2017 15:30:30 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jul 08 17:30:25 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dTrgd-0003c8-7X for geh-help-gnu-emacs@m.gmane.org; Sat, 08 Jul 2017 17:30:23 +0200 Original-Received: from localhost ([::1]:33184 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTrgi-0000YC-N1 for geh-help-gnu-emacs@m.gmane.org; Sat, 08 Jul 2017 11:30:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47290) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTrgE-0000Y5-N0 for help-gnu-emacs@gnu.org; Sat, 08 Jul 2017 11:29:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dTrgB-0001x2-KT for help-gnu-emacs@gnu.org; Sat, 08 Jul 2017 11:29:58 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTrgB-0001ww-H9 for help-gnu-emacs@gnu.org; Sat, 08 Jul 2017 11:29:55 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2415 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dTrgA-0003yE-VQ for help-gnu-emacs@gnu.org; Sat, 08 Jul 2017 11:29:55 -0400 In-reply-to: <20170708152050.GB29492@tuxteam.de> (tomas@tuxteam.de) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:113741 Archived-At: > 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.