#1317: wish $edit_charset
------------------------------------------------+---------------------------
Reporter: Tony Leneis <t...@cvr.ds.adp.com> | Owner: mutt-dev
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: charset | Version: 1.4i
Resolution: | Keywords:
------------------------------------------------+---------------------------
Comment(by Vincent Lefevre):
{{{
On 2009-07-02 14:19:29 -0500, Derek Martin wrote:
That's why one may need to switch between different locales (e.g. for
grep), because not all files use the same charset. Some files are
remote files, shared by several users, and one doesn't necessarily
has the choice.
If some users don't know how to configure their system, complain to
them, not here.
I don't know what you mean here, but by default, Mutt does bad things
with charsets. The $thorough_search variable is broken by design and
should be removed.
This remark is ridiculous. First because Mutt is one of the
applications that break under a UTF-8 locale (see above). Then because
one doesn't necessarily have the choice; even when there are other
similar applications that have no problems with UTF-8, they may have
more important bugs so that they can't be used.
Anyway since Mutt allows the user to run it under non-UTF-8 locales,
using such locales should be assumed to be OK.
Wrong. For instance, editors must respect the encoding of XML files
(which is provided with the file in some way), and doing something
else would be against the XML spec.
Now more generally, emacs (and probably others) can be configured to
use an encoding declared by user to *match* the encoding of the file.
Saying that it is broken would be stupid. Note: again, Mutt is
concerned by this point (e.g. the "edit" command).
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/1317#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
