Subject: bug#8308: 23.3; Use utf-8 for writing abbrev file

From: Leo <[email-masked]>
Date: Tue, 22 Mar 2011 18:41:39 +0800

On 2011-03-22 13:24 +0800, Stefan Monnier wrote:
> (unibyte-string 129) returns a string containing an unencodable char.
> So you can test with it.

I still cannot get any byte into the abbrevs. For example,
(unibyte-string 129) returns byte \201 but when it is written to abbrev
file by write-abbrev-file, it is changed to \ 2 0 1, so utf-8 appear
sufficient even for bytes.

Leo