From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: character encoding question
Date: Thu, 21 Feb 2013 10:42:24 +0800 [thread overview]
Message-ID: <8738wqxu9b.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 83obfeom7j.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Date: Wed, 20 Feb 2013 09:42:49 -0500
>>
>> > Given a series of mystery bytes, can I test them against different
>> > charsets, and see what gibberish Emacs comes up with?
>>
>> (decode-coding-string "\344\270\255" 'utf-8) ==> "中"
>
> I'd actually suggest decode-coding-region, because it doesn't require
> copying the "mystery bytes" into a string, something that might change
> the bytes.
Perfect, just what I was looking for. I was getting tired of repeated
revert-buffer-with-etc calls! The explanation about the octal notation
cleared things up nicely, as well.
Many thanks,
Eric
prev parent reply other threads:[~2013-02-21 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 6:34 character encoding question Eric Abrahamsen
2013-02-20 10:44 ` Peter Dyballa
2013-02-20 14:42 ` Stefan Monnier
2013-02-20 18:48 ` Eli Zaretskii
2013-02-21 2:42 ` Eric Abrahamsen [this message]
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=8738wqxu9b.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).