#3040: charset difference between index browser and pager
---+
Reporter: miekg | Owner: mutt-dev
Type: defect | Status: new
Priority: minor | Milestone:
#3040: charset difference between index browser and pager
Changes (by brendan):
* priority: major = minor
--
Ticket URL: http://dev.mutt.org/trac/ticket/3040#comment:30
#3040: charset difference between index browser and pager
Comment (by Derek Martin):
{{{
On Mon, Apr 07, 2008 at 01:47:28AM +0200, Vincent Lefevre wrote:
Mutt should not be redesigned in such a way as
to be inconsistent with the current Unix paradigm for handling
encodings, just
On Mon, Apr 07, 2008 at 01:47:28AM +0200, Vincent Lefevre wrote:
Mutt should not be redesigned in such a way as
to be inconsistent with the current Unix paradigm for handling
encodings, just because you don't like your options...
No, that's not the current Unix paradigm.
The fact that
On 2008-04-05 22:31:43 -0400, Derek Martin wrote:
On Sat, Apr 05, 2008 at 05:13:27PM +0200, Vincent Lefevre wrote:
There are also many bugs related to UTF-8, e.g. Debian bug 391452
(that's the most important one),
It seems likely that this is not a bug at all, but an improper
expectation
#3040: charset difference between index browser and pager
Comment (by Vincent Lefevre):
{{{
On 2008-04-05 22:31:43 -0400, Derek Martin wrote:
On Sat, Apr 05, 2008 at 05:13:27PM +0200, Vincent Lefevre wrote:
There are also many bugs related to UTF-8, e.g. Debian bug 391452
(that's the
On 2008-03-28 09:48:02 -0400, Derek Martin wrote:
switch your environment to UTF-8. So who's the idiot?
You're not living in the real world. How can one switch the Zaurus
to UTF-8? How can one switch the environment to UTF-8 when UTF-8
locales have not been installed and the user isn't root and
#3040: charset difference between index browser and pager
Comment (by Vincent Lefevre):
{{{
On 2008-03-28 09:48:02 -0400, Derek Martin wrote:
switch your environment to UTF-8. So who's the idiot?
You're not living in the real world. How can one switch the Zaurus
to UTF-8? How can one
On Sat, Apr 05, 2008 at 05:13:27PM +0200, Vincent Lefevre wrote:
On 2008-03-28 09:48:02 -0400, Derek Martin wrote:
switch your environment to UTF-8. So who's the idiot?
You're not living in the real world.
I beg to differ, see below.
There are also many bugs related to UTF-8, e.g.
#3040: charset difference between index browser and pager
Comment (by Derek Martin):
{{{
On Sat, Apr 05, 2008 at 05:13:27PM +0200, Vincent Lefevre wrote:
On 2008-03-28 09:48:02 -0400, Derek Martin wrote:
switch your environment to UTF-8. So who's the idiot?
You're not living in the
#3040: charset difference between index browser and pager
Comment (by Miek Gieben):
{{{
[27 Mar, @15:48 CET, Mutt wrote in Re: [Mutt] #3040: charset diff ...]
#3040: charset difference between index browser and pager
reverse_alias=yes is set. So this is why it displays the name wrong.
On 2008-03-27 11:21:15 -0400, Derek Martin wrote:
On Thu, Mar 27, 2008 at 01:00:29AM +0100, Vincent Lefevre wrote:
On 2008-03-22 16:28:43 +0100, Thomas Roessler wrote:
The user isn't assumed to run under UTF-8. The user is assumed to
run in a consistent environment in which the terminal,
#3040: charset difference between index browser and pager
Comment (by Derek Martin):
{{{
On Fri, Mar 28, 2008 at 10:14:30AM +0100, Vincent Lefevre wrote:
On 2008-03-27 11:21:15 -0400, Derek Martin wrote:
On Thu, Mar 27, 2008 at 01:00:29AM +0100, Vincent Lefevre wrote:
On 2008-03-22
On Fri, Mar 28, 2008 at 10:14:30AM +0100, Vincent Lefevre wrote:
On 2008-03-27 11:21:15 -0400, Derek Martin wrote:
On Thu, Mar 27, 2008 at 01:00:29AM +0100, Vincent Lefevre wrote:
On 2008-03-22 16:28:43 +0100, Thomas Roessler wrote:
The user isn't assumed to run under UTF-8. The user is
#3040: charset difference between index browser and pager
Comment (by Alain Bench):
{{{
On Wednesday, March 26, 2008 at 18:13:19 -, Miek Gieben wrote:
reverse_alias=yes is set. So this is why it displays the name wrong.
The entry in the alias file looks okay though...
The
On Thu, Mar 27, 2008 at 01:00:29AM +0100, Vincent Lefevre wrote:
On 2008-03-22 16:28:43 +0100, Thomas Roessler wrote:
The user isn't assumed to run under UTF-8. The user is assumed to
run in a consistent environment in which the terminal, the file
system, and local files share a single
#3040: charset difference between index browser and pager
Comment (by Derek Martin):
{{{
On Thu, Mar 27, 2008 at 01:00:29AM +0100, Vincent Lefevre wrote:
On 2008-03-22 16:28:43 +0100, Thomas Roessler wrote:
The user isn't assumed to run under UTF-8. The user is assumed to
run in a
#3040: charset difference between index browser and pager
Comment (by Miek Gieben):
{{{
[25 Mar, @02:21 CET, Mutt wrote in Re: [Mutt] #3040: charset diff ...]
Thanks Miek, Google groups gave me the original raw header:
| From: =?iso-8859-1?Q?=D3lafur?=
#3040: charset difference between index browser and pager
Comment (by Miek Gieben):
{{{
[26 Mar, @08:22 CET, Mutt wrote in Re: [Mutt] #3040: charset diff ...]
#3040: charset difference between index browser and pager
% export | grep -i lang
LANG=en_US.UTF-8
LANGUAGE=en_US:en_GB:en
On 2008-03-22 16:28:43 +0100, Thomas Roessler wrote:
The user isn't assumed to run under UTF-8. The user is assumed to
run in a consistent environment in which the terminal, the file
system, and local files share a single character set which is
inferred from the user's locale settings.
This
#3040: charset difference between index browser and pager
Comment (by Alain Bench):
{{{
On Friday, March 21, 2008 at 6:56:26 -, Miek Gieben wrote:
the from address in de index is displayed as ?lafur Gu?mansson, and in
the body of the mail it is rendered okay (as it looks in the
On 2008-03-21 16:46:51 +0100, Vincent Lefevre wrote:
I frankly wouldn't bother adding code to mutt to work properly
in another inconsistent specification edge case, where the user
actually runs several locales in parallel.
The problem occurs even when using only *one* locale. If the user
is
#3040: charset difference between index browser and pager
Comment (by Thomas Roessler):
{{{
On 2008-03-21 16:46:51 +0100, Vincent Lefevre wrote:
I frankly wouldn't bother adding code to mutt to work properly
in another inconsistent specification edge case, where the user
actually runs
Hello Kyle,
On Thursday, March 20, 2008 at 11:51:33 -0500, Kyle Wheeler wrote:
On Thursday, March 20 at 03:47 PM, quoth Vincent Lefevre:
set charset=`codeset 2 /dev/null || locale charmap`//TRANSLIT
it isn't particularly portable...
While neither universally portable, there is a pair of
On 2008-03-21 11:42:00 +0100, Alain Bench wrote:
The other is using locale_charset() from libcharset, libiconv,
gettext, or whatever, and should be portable to a whole lot of systems.
Christian tested it OK on MacOS-X.
My codeset program does the following:
#include stdio.h
#include
#3040: charset difference between index browser and pager
Comment (by Vincent Lefevre):
{{{
On 2008-03-21 11:42:00 +0100, Alain Bench wrote:
The other is using locale_charset() from libcharset, libiconv,
gettext, or whatever, and should be portable to a whole lot of systems.
On 2008-03-21 15:12:41 +0100, Vincent Lefevre wrote:
BTW, it seems that Mutt mixes the locale charset and the editor
charset. This is also something bad. For instance, I use
ISO-8859-1 locales (in an ISO-8859-1 terminal) and want to reply
to a message written in UTF-8, with characters that
#3040: charset difference between index browser and pager
Comment (by Thomas Roessler):
{{{
On 2008-03-21 15:12:41 +0100, Vincent Lefevre wrote:
BTW, it seems that Mutt mixes the locale charset and the editor
charset. This is also something bad. For instance, I use
ISO-8859-1 locales
On 2008-03-21 15:20:25 +0100, Thomas Roessler wrote:
So, why don't you use utf-8 in terminals?
Because not all software supports multibyte characters (in particular
not too old versions of zsh). Also, almost all my files are in
ISO-8859-1, so that using ISO-8859-1 is more practical (mainly for
#3040: charset difference between index browser and pager
Comment (by Alain Bench):
{{{
Hello Miek, and thank you for the problem report.
On Tuesday, March 18, 2008 at 20:42:11 -, Miek Gieben wrote:
| set assumed_charset=UTF-8
You .nl very probably don't want that: try cp1252
#3040: charset difference between index browser and pager
Comment (by Vincent Lefevre):
{{{
On 2008-03-18 16:05:37 -0500, Kyle Wheeler wrote:
On Tuesday, March 18 at 08:42 PM, quoth Mutt:
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
Do not set $charset. There are very few
On Thursday, March 20 at 03:47 PM, quoth Vincent Lefevre:
Do not set $charset. There are very few good reasons for it.
A good reason is to use transliteration!
I didn't say there were *NO* good reasons. Transliteration is the only
one I'm aware of, and even that has problems, as Alain
#3040: charset difference between index browser and pager
Comment (by Kyle Wheeler):
{{{
On Thursday, March 20 at 03:47 PM, quoth Vincent Lefevre:
Do not set $charset. There are very few good reasons for it.
A good reason is to use transliteration!
I didn't say there were *NO* good
On 2008-03-20 11:51:33 -0500, Kyle Wheeler wrote:
On Thursday, March 20 at 03:47 PM, quoth Vincent Lefevre:
set charset=`codeset 2 /dev/null || locale charmap`//TRANSLIT
Part of the problem there is that it isn't particularly portable...
A .muttrc file doesn't have to be portable. It just
#3040: charset difference between index browser and pager
Comment (by brendan):
Are you using gmail IMAP by any chance? The gmail IMAP server has a bug
which produces these symptoms in mutt. See #2997 for more info.
--
Ticket URL: http://dev.mutt.org/trac/ticket/3040#comment:5
#3040: charset difference between index browser and pager
Comment (by Miek Gieben):
{{{
[19 Mar, @16:53 CET, Mutt wrote in Re: [Mutt] #3040: charset diff ...]
#3040: charset difference between index browser and pager
Comment (by brendan):
Are you using gmail IMAP by any chance? The
#3040: charset difference between index browser and pager
I'm using the following setting in muttrc:
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
My index_format is:
index_format=%4C %Z %(%b %d (%H:%M)) %-18.18n [%10.10B] (%3.3c) %?H? [%H]
? %.60s
Suppose my name (Miek Gieben)
On Tuesday, March 18 at 08:42 PM, quoth Mutt:
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
Do not set $charset. There are very few good reasons for it.
There is *never* a good reason to use UTF-8 and //TRANSLIT at the same
time.
Suppose my name (Miek Gieben) would contain some
#3040: charset difference between index browser and pager
Comment (by Kyle Wheeler):
{{{
On Tuesday, March 18 at 08:42 PM, quoth Mutt:
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
Do not set $charset. There are very few good reasons for it.
There is *never* a good reason to
#3040: charset difference between index browser and pager
Comment (by Miek Gieben):
{{{
[18 Mar, @22:05 CET, Mutt wrote in Re: [Mutt] #3040: charset diff ...]
#3040: charset difference between index browser and pager
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
Do not
On Tuesday, March 18 at 09:21 PM, quoth Mutt:
It's possible that your name is being mis-encoded in email, and so
it is taking various paths through mutt on the way to being
displayed based on whether mutt notices the problem or not.
The content type of the email showing this problem is set to
41 matches
Mail list logo
