unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Help-gnu-emacs@gnu.org
Subject: Re: Emacs text bug
Date: Thu, 31 Jan 2013 22:04:54 +0200	[thread overview]
Message-ID: <83halxce55.fsf@gnu.org> (raw)
In-Reply-To: <1359660527067-276942.post@n5.nabble.com>

> Date: Thu, 31 Jan 2013 11:28:47 -0800 (PST)
> From: drain <aeuster@gmail.com>
> 
> Now I see. This problem must have started when I copied an early 19th
> century letter into the buffer, and the characters did not transliterate
> properly into modern English. Whatever those characters were, they turned
> into circumflexed /a/ (â), the pound sign (£), and a (special) right double
> quotation mark (”). utf-8 apparently cannot handle these.

UTF-8 certainly _can_ handle them.  I suspect that these characters
got copied as raw bytes instead.

> But why would this prevent utf-8 from encoding the rest of the buffer? Why
> not just leave those three characters mangled, and display the rest
> properly? It reverted fine; it just would not stay in utf-8 unless I (1)
> put the instruction at the top of the buffer or (2) deleted those special
> characters. So the functionality appears to be there: Emacs just would not
> accept it as a saved state (absent instruction at the top).

Emacs auto-detects the encoding each time you visit a file, unless
either the file (by the 'coding:' cookie) or you (by using "C-x RET c")
tell it exactly how to decode the file.




  reply	other threads:[~2013-01-31 20:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 20:23 Emacs text bug drain
2013-01-26 22:26 ` Peter Dyballa
2013-01-26 22:43   ` drain
2013-01-26 22:59     ` Peter Dyballa
2013-01-26 23:23       ` drain
2013-01-26 23:29         ` Peter Dyballa
2013-01-31 17:55           ` drain
2013-01-31 18:36             ` Doug Lewan
2013-01-31 18:45               ` drain
2013-01-31 19:08                 ` Eli Zaretskii
2013-01-31 18:52             ` Eli Zaretskii
2013-01-31 19:28               ` drain
2013-01-31 20:04                 ` Eli Zaretskii [this message]
2013-01-26 22:48   ` Drew Adams
2013-01-26 23:26     ` Peter Dyballa

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=83halxce55.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).