From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: reading binary, non-unix file
Date: Mon, 25 Oct 2004 17:55:32 -0600 [thread overview]
Message-ID: <2u5i3nF276g67U1@uni-berlin.de> (raw)
In-Reply-To: <cljrs9$gk5$1@quimby.gnus.org>
[Please don't top-post.]
Mickey Ferguson wrote:
> We're almost there. I don't have a single UTF-16 coding choice. When I
> tried what you provided, I saw:
>
> Possible completions are:
> utf-16-be utf-16-be-dos
> utf-16-be-mac utf-16-be-unix
> utf-16-le utf-16-le-dos
> utf-16-le-mac utf-16-le-unix
>
> I chose utf-16-le and it seemed to do it properly. I just don't know if
> that was the right choice - I don't fully understand what each of these
> provides.
LE = Little Endian and BE = Big Endian. Emacs should provide an
encoding in which the endianness is determined from the BOM, but since
it doesn't, utf-16-le is right for x86 processors. See
http://en.wikipedia.org/wiki/UTF-16
> Second, after I determine which one of the above to use, can anyone
help me
> to write a function so that I can then map a key combination (similar
to C-X
> C-F uses Find-File), that will load in the proper coding and then
find the
> file? I'm lisp-impaired, so any help would be appreciated. I'm
capable of
> taking an interactive function that's been defined and mapping it to a
> keystroke, but that's about it.
What's wrong with `C-x RET c utf-16-le RET C-x C-f' :-)
If all the files are UTF-16 on your system, perhaps you can just put
this in your .emacs file:
(setq-default buffer-file-coding-system 'utf-16-le)
--
Kevin Rodgers
next prev parent reply other threads:[~2004-10-25 23:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 18:47 reading binary, non-unix file Mickey Ferguson
2004-10-22 19:27 ` J. David Boyd
[not found] ` <mailman.4677.1098473798.2017.help-gnu-emacs@gnu.org>
2004-10-22 19:57 ` Mickey Ferguson
2004-10-25 6:40 ` Mathias Dahl
2004-10-25 17:48 ` Mickey Ferguson
2004-10-26 1:08 ` Daniel Pittman
2004-10-26 9:05 ` Mathias Dahl
2004-10-26 17:00 ` Mickey Ferguson
2004-10-27 7:46 ` Mathias Dahl
2004-10-27 16:20 ` Mickey Ferguson
2004-10-27 16:39 ` Reiner Steib
2004-10-27 16:41 ` Drew Adams
2004-10-25 21:43 ` Mickey Ferguson
2004-10-25 23:55 ` Kevin Rodgers [this message]
2004-10-23 3:44 ` Daniel Pittman
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=2u5i3nF276g67U1@uni-berlin.de \
--to=ihs_4664@yahoo.com \
/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).