bug#4047: 23.1.1: hexl-mode doesn't like UTF8 files with a byte-order mark

[Kenichi Handa]

In article <83ljldh5pm.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > > > Unless Handa objects, I'd recommend we change encode_coding_string to be
> > > > a nop on unibyte strings (tho, we may want to let it obey EOL
> > > > conversions).
> > > 
> > > I don't object to that change.
> > 
> > For strings only (i.e. in coding.h:encode_coding_string) or on the
> > more basic level, in coding.c:encode_coding_object?

> Ping!

At the moment, all I can say is that changing
coding.h:encode_coding_string is quite safe.  But,
encode_coding_object is used by Lisp functions
encode-coding-region and encode-coding-string, and thus the
change will break some packages that use them on unibyte
string/buffer.

---
Kenichi Handa
handa@m17n.org