[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eli Zaretskii
Subject: bug#31807: 27.0; `info-apropos' bad name or bad matching
Date: Sun, 17 Jun 2018 10:44:10 +0300

> Date: Thu, 14 Jun 2018 07:16:12 -0700 (PDT)
> From: Drew Adams <address@hidden>
> Cc: address@hidden
> > > 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.

Done on the master branch.

> 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.

Option (2) is already available: just type C-g.  And the other 2 is
what this dialog is about.  With this change, UTF-8 is offered as the
default, if it can encode the text, and all the other encodings are
shown in a list from which the user can select another one.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]