From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Encoding again
Date: Tue, 19 Oct 2004 13:15:09 GMT [thread overview]
Message-ID: <jwv8ya2j1pk.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 2oZcd.58831$Vf.2788737@news000.worldonline.dk
> As far as I can see, there is no or little difference between the
> coding systems:
> emacs-mule
> raw-text
> no-conversion
> binary
binary == no-conversion == raw-text-unix.
raw-text is almost the same except it does end-of-line conversion.
emacs-mule is completely different: reading a file with one of the other
3 encoding will only generate chars between 0 and 255, whereas with
emacs-mule you can get literally any char (it's an encoding loosely
comparable to iso-2022 or to utf-8).
emacs-mule should generally be avoided (it's the internal encoding used
inside Emacs buffers and can change between Emacs versions).
Stefan
prev parent reply other threads:[~2004-10-19 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 0:40 Encoding again Soren Kuula
2004-10-19 12:18 ` Thien-Thi Nguyen
2004-10-19 13:15 ` Stefan Monnier [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=jwv8ya2j1pk.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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).