[bug-notifications] [mutt 0002973]: mutt compiled with libidn does not work with the defaul locale
Mantis Bug Tracker
noreply at opencsw.org
Tue Sep 22 20:36:54 CEST 2009
The following issue requires your FEEDBACK.
======================================================================
http://www.opencsw.org/mantis/view.php?id=2973
======================================================================
Reported By: bfr-murphy
Assigned To: skayser
======================================================================
Project: mutt
Issue ID: 2973
Category: regular use
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2008-12-17 21:13 CET
Last Modified: 2009-09-22 20:36 CEST
======================================================================
Summary: mutt compiled with libidn does not work with the
defaul locale
Description:
When compiled with libidn mutt does not work with the "C" or "POSIX"
locales. The error 'Bad IDN "{hostname of IMAP server}".' is printed in
the message line at the bottom of the terminal window and no connection is
made to the IMAP server.
This is a problem because the Sun default locale is "C".
Unsetting the mutt variable use_idn or changing the value of the mutt
variables charset, assumed_charset, attach_charset, config_charset, and
send_charset does not fix the problem.
Possible solutions:
1) Do not compile mutt with libidn.
2) Provide a wrapper script that checks the LANG shell environment
variable and changes the LC_ALL shell environment variable to another value
if LANG is "C" or "POSIX". There would need to be a way for the user to
specify a locale other than "C" or "POSIX" for the wrapper to use.
======================================================================
----------------------------------------------------------------------
(0006742) skayser (administrator) - 2009-09-22 20:36
http://www.opencsw.org/mantis/view.php?id=2973#c6742
----------------------------------------------------------------------
This has been lingering for a while and should be fixed with the updated
libiconv 1.13.1,REV=2009.07.31 which has been released today.
bfr-murphy, could you please verify that it solves the problem for you.
More information about the bug-notifications
mailing list