bug#31807: 27.0; `info-apropos' bad name or bad matching

[Drew Adams]

> > This is the scary text I saw, FWIW:...
>
> What's so scary about it?  It clearly identifies the problematic
> characters, offers clickable buttons to go to each of them, and
> explains the problem.  It should probably suggest UTF-8 as the first
> alternative, but other than that I see no problem in this dialog.

Yes, at the very least, it should suggest utf-8 and provide
that as the default value.  Only in a separate paragraph
should it say that you can instead use any of the following
instead...

Make it simple to understand that utf-8 solves the problem,
and make it simple to choose utf-8.  You might even want
to make it a 3-way decision: (1) Yes, convert to utf-8,
(2) No, don't save, (3) Convert to an alternative encoding.