From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani
> From: ohki@gssm.otsuka.tsukuba.ac.jp
> Cc: ohki@gssm.otsuka.tsukuba.ac.jp, 22815@debbugs.gnu.org
> Date: Sat, 27 Feb 2016 08:21:39 +0900
>
> Eli Zaretskii writes:
> > > From: ohki@gssm.otsuka.tsukuba.ac.jp
> > > Cc: ohki@gssm.otsuka.tsukuba.ac.jp, 22815@debbugs.gnu.org
> > > Date: Fri, 26 Feb 2016 19:09:57 +0900
> > >
> > > > I was asking why couldn't the plug-in do the conver= sion, e.g., by
> > > > using libiconv?=C2=A0 Emacs is not the only piece of so= ftware that knows
> > > > how to convert from one encoding to another.
> > >
> > >=C2=A0 I considered using libiconv once, but Emacs has the co= nversion
> > >=C2=A0 capability, so why not use it.
> >
> > Because it can signal an error, if the encoding you pass is not a=
> > valid coding-system that Emacs recognizes?
>
>=C2=A0 Yes it does!
>=C2=A0 In the course of developing my plugin,
>=C2=A0 I encountered `Invalid coding system' message,=C2=A0 and Ema= cs keep working
>=C2=A0 (no crash, no hangup).
It's all too easy to get that, since Emacs coding-systems have names
that are rarely used elsewhere.=C2=A0 And using libiconv is easy enough.
So I'm uneasy about this.=C2=A0 What do others think?