-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thursday, July 29 at 11:32 AM, quoth Paul E Condon:
I'm still having problems. I'd like to read some documentation that
expands on what these configuration lines do.
Without a better idea of what you're after, I'd say the Mutt manual is
the
On 20100727_155630, Kyle Wheeler wrote:
On Tuesday, July 27 at 12:35 PM, quoth Paul E Condon:
1) The short answer does not work. My copy of Mutt informs me that
LC_TYPE is not a recognized variable name.
LC_TYPE (or, more correctly, LC_CTYPE) is not a mutt variable. It
should not be set
? How? Or (gently, please) why is this a silly
question?
FWIW, the charset.c source file says that mutt's charset names come from
http://www.isi.edu/in-notes/iana/assignments/character-sets
and that only charsets for which a preferred MIME name is given are
listed.
The recommended additions
On Wed, Jul 28, 2010 at 12:41:37AM -0600, Paul E Condon wrote:
Thanks for tip about iconv. I do have both WINDOWS-1252 and CP1252 on my
computer. So the second line should not be needed. While composing this
email I suddenly realized that the charset names are probably case sensitive
and my
I use Mutt in a system that is running Debian Squeeze. I have
installed the system recently and it should have no legacy
cruft from Lenny or whatever. I did this new install because
I was having serious problems with charsets and utf8. Almost
all such are gone from this. But a problem with Mutt
On 2010-07-27, Paul E Condon wrote:
I use Mutt in a system that is running Debian Squeeze. I have
installed the system recently and it should have no legacy
cruft from Lenny or whatever. I did this new install because
I was having serious problems with charsets and utf8. Almost
all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tuesday, July 27 at 12:35 PM, quoth Paul E Condon:
1) The short answer does not work. My copy of Mutt informs me that
LC_TYPE is not a recognized variable name.
LC_TYPE (or, more correctly, LC_CTYPE) is not a mutt variable. It
should not be
Date: Thu, 1 Aug 2002 15:58:46 +1000
From: Erik Christiansen [EMAIL PROTECTED]
To: Mutt users ml [EMAIL PROTECTED]
Subject: Re: problem about subjects in asian charsets
OK, it seems then that the xterm and vim are more tolerant than mutt,
when it comes to ISO8859-1 characters
On Tue, Jul 30, 2002 at 04:54:18PM +0800, Isaac Claymore wrote:
However, whenever I send emails with a subject in Chinese, the receiver
gets something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=, although
all other parts of the mail are fine.
Thanks for hints and
On Tue, Jul 30, 2002 at 10:38:55PM +0200, Alain Bench wrote:
Hello Isaac,
On Tuesday, July 30, 2002 at 4:54:18 PM +0800, Isaac Claymore wrote:
whenever I send emails with a subject in Chinese, the receiver gets
something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=
This gets
Hi Erik,
On Wednesday, July 31, 2002 at 7:26:25 PM +1000, Erik Christiansen wrote:
100 N + Jul 19 Erik Christians ( 4) Forbl?ffende Ul?selig V?s
Subject: Forbl\370ffende Ul\346selig V\345s
Would whatever helped Isaac also fix this one?
No: completely different problem. Your's is even
On Wed, Jul 31, 2002 at 01:12:56PM +0200, Alain Bench wrote:
No: completely different problem. Your's is even not a Mutt problem,
just bad system's locale configuration. Try to set LC_CTYPE to a
suitable locale for your language, country and character set.
Thanks Alain, for the hint
On Wed, Jul 31, 2002 at 01:12:56PM +0200, Alain Bench wrote:
No: completely different problem. Your's is even not a Mutt problem,
just bad system's locale configuration. Try to set LC_CTYPE to a
suitable locale for your language, country and character set.
OK, it seems then that
Hi folks,
I set up .muttrc as:
set charset=zh_cn.gb2312
set send_charset=us-ascii:iso-8859-1:zh_cn.gb2312
And everything is OK, I can read and write mails in Chinese(in gb2312).
However, whenever I send emails with a subject in Chinese, the receiver
gets something like
Hi,
* Isaac Claymore [02-07-30 15:03:51 +0200] wrote:
set charset=zh_cn.gb2312
set send_charset=us-ascii:iso-8859-1:zh_cn.gb2312
And everything is OK, I can read and write mails in Chinese(in gb2312).
However, whenever I send emails with a subject in Chinese, the receiver
Hello Isaac,
On Tuesday, July 30, 2002 at 4:54:18 PM +0800, Isaac Claymore wrote:
whenever I send emails with a subject in Chinese, the receiver gets
something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=
This gets decodable (everywhere?) once the zh_cn. removed. So if
your iconv
Hi!
Until yesterday, I used mutt installed from RedHat's RPM (125) I have
now switched to mutt-1327i-11rhl6 (linked from wwwmuttorg) and
have discovered that my outgoing messages have garbled charsets (and
umlaut letters are displayed as question marks in incoming messages)
I don't even know
* Johan Almqvist [EMAIL PROTECTED] [020305 16:49]:
Until yesterday, I used mutt installed from RedHat's RPM (1.2.5). I have
now switched to mutt-1.3.27i-1.1.rhl6 (linked from www.mutt.org) and
have discovered that my outgoing messages have garbled charsets (and
umlaut letters are displayed
* Johan Almqvist [EMAIL PROTECTED] [05-03-02 10:27 AM EST]:
Until yesterday, I used mutt installed from RedHat's RPM (1.2.5). I have
now switched to mutt-1.3.27i-1.1.rhl6 (linked from www.mutt.org) and
Please check the whole thread starting with
[EMAIL PROTECTED]. The fix is there.
Cheers,
starting with
[EMAIL PROTECTED]. The fix is there.
this is how the thread look like in my mutt's index:
40640 X 020304 Johan Almqvist( 17) Garbled charsets
40641 X 020304 David Collantes ( 79) |-
40642 X 020304 Dominik Mierzejew ( 28) | `-
40643 X 020304 David Collantes ( 95
Hi!
Until yesterday, I used mutt installed from RedHat's RPM (125) I have
now switched to mutt-1327i-11rhl6 (linked from wwwmuttorg) and
have discovered that my outgoing messages have garbled charsets (and
umlaut letters are displayed as question marks in incoming messages)
I don't even know
* Johan Almqvist [EMAIL PROTECTED] [04-03-02 01:26 PM EST]:
[... SNIP ...]
have discovered that my outgoing messages have garbled charsets (and
umlaut letters are displayed as question marks in incoming messages).
[... SNIP ...]
I am seeing something similar, but getting characters like
On Monday, 04 March 2002, David Collantes wrote:
* Johan Almqvist [EMAIL PROTECTED] [04-03-02 01:26 PM EST]:
[... SNIP ...]
have discovered that my outgoing messages have garbled charsets (and
umlaut letters are displayed as question marks in incoming messages).
[... SNIP ...]
I am
* Dominik Mierzejewski [EMAIL PROTECTED] [04-03-02 02:12 PM EST]:
I am seeing something similar, but getting characters like:
\337
\256
\251
\352
?
\377
When using umlauts. I have the latest iconv installed. Anyone has an
Looks like config issue. Show output of `locale`
On Monday, 04 March 2002, David Collantes wrote:
[snip]
Locale is:
[david@david]$ locale
LANG=POSIX
LC_CTYPE=POSIX
LC_NUMERIC=POSIX
LC_TIME=POSIX
LC_COLLATE=POSIX
LC_MONETARY=POSIX
LC_MESSAGES=POSIX
LC_ALL=
I'm no guru, but I don't think POSIX locale knows about umlauts and stuff
Why
* Dominik Mierzejewski [EMAIL PROTECTED] [04-03-02 03:01 PM EST]:
Good. You might want to try us-ascii:iso-8859-1:utf-8, though.
I have mine set to us-ascii:iso-8859-1:iso-8859-2:utf-8.
Excellent! My locale is set to en_US and everything is showing the way it
should. Thanks for the tips and
On Mon, Mar 04, 2002 at 07:04:57PM +0100, Johan Almqvist wrote:
have discovered that my outgoing messages have garbled charsets (and
umlaut letters are displayed as question marks in incoming messages)
I have exactly the same problems here I found that unsetting charset
shows umlauts
hi,
thanks for all replies regarding pop password forgetting. i understand the necessity
of using fetchmail, and i plan to switch to it later. currently i implement
quick-and-dirty solution, which is to set pop_pass to a dummy value and then unsetting
it.
now i've got another problem. i'm
Guys,
I'm not sure if you got this message. If you did, just disregard it. I can't
seem to be able to read messages in other encodings with mutt. Setting
"charset" to anything does not help at all. This is my compile options:
-DOMAIN
-HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL
Marius Gedminas [EMAIL PROTECTED]:
Once again -- could `charset-hook' be renamed to `charset-alias' before
1.2 please? It's not a hook. Definetely. Not a hook at all. Not even
close to that.
This sounds like a sensible suggestion.
Edmund
Denis Chapligin [EMAIL PROTECTED]:
How can i make Mutt automaticly recode e-mails from one character
set to another one?
If it's installed properly, it should handle charsets correctly. Do
you have a specific problem?
I recommend upgrading to 1.0.1, by the way; the only differences
between
Denis Chapligin wrote:
: Hi
:
: How can i make Mutt automaticly recode e-mails from one character set to another one?
I not have any problems with it.
Is your `charset' variable set properly?
What is your local encoding?
What is encoding of recode-failed message (for example)?
--
Andrew W.
Hi
On Wed, Mar 01, 2000 at 02:51:59PM +0200, Andrew W. Nosenko wrote:
:
: How can i make Mutt automaticly recode e-mails from one character set to another
one?
I not have any problems with it.
Is your `charset' variable set properly?
Yes.
What is your local encoding?
KOI8-R
What is
Denis Chapligin [EMAIL PROTECTED]:
There is one of message that i can't read with mutt
It's in "windows-1251". Presumably your mutt doesn't know about that
charset.
I think you can tell whether mutt knows about a charset by going to
the compose menu and doing ":exec change-charset" on any
On Wed, Mar 01, 2000 at 04:52:19PM +, Edmund GRIMLEY EVANS wrote:
It's in "windows-1251". Presumably your mutt doesn't know about that
charset.
I think you can tell whether mutt knows about a charset by going to
the compose menu and doing ":exec change-charset" on any text part. If
the
Hi
On Wed, Mar 01, 2000 at 09:45:14PM +0200, Marius Gedminas wrote:
knows about a charset.
My mutt does know about windows-1251. I'm using it for the body of
this message, I think.
Mine doesn't. Actually, it's not Mutt who doesn't know this charset,
it's my /usr/share/i18n/charmaps/
in this branch implemented
with using external charset files -- this allow add new charsets
without recompilation of Mutt, and charset aliases -- without
charset hooks.
--
Andrew W. Nosenko([EMAIL PROTECTED])
Michael S. Tsirkin [EMAIL PROTECTED]:
Hello!
Have the following problem with mutt-1.0.1:
Each time a message comes with
Content-Type: text/plain; charset=koi8-r
All koi8 letters are replaced with '?' in an internal viewer
I must pipe to 'cat' to see the real contents.
Does anyone
Hello!
Have the following problem with mutt-1.0.1:
Each time a message comes with
Content-Type: text/plain; charset=koi8-r
All koi8 letters are replaced with '?' in an internal viewer
I must pipe to 'cat' to see the real contents.
Does anyone have a clue how can this be helped?
Thanks,
Hello,
I have a problem with mutt's insistent translating between charsets
when I view messages in Russian.
Such messages typically belong to the 'koi8-r' charset, yet there are
three types of messages:
a) With charset=iso-8859-1 incorrectely written in Content-Type: header
b) With charset
Anatoly Vorobey [EMAIL PROTECTED] wrote:
a) With charset=iso-8859-1 incorrectely written in Content-Type: header
b) With charset=koi8-r correctly written in Content-Type: header
Messages of type (a) are broken, and you should inform the sender that
their mail software is incorrectly
Timur Mustakimov:
I have the following problem with mutt. It doesn't show cyrillic chars, although my
terminal, which in mutt is running shows them very nice. Mutt change all of them to
'?'. What do i need to set ? Charset is koi-8r.
Check that you really did install the charsets ("
I have the following problem with mutt. It
doesn't show cyrillic chars, although my terminal, which in mutt is running
shows them very nice. Mutt change all of them to '?'. What do i need to set ?
Charset is koi-8r.
No apologies
needed...I'm probably just not understanding how mutt/linux/charsets all
interact, and would like someone to briefly explain to me where I'm going
wrong. :)
There are two things that might be wrong:
1) Application Character Map shows which characters written out to the
console map to w
Marius Gedminas dijo:
My version of mutt interprets these characters correctly (by converting them
from iso-8859-1 to iso-8859-13 which I use).
iso-8859-13 ... isn't it an extended iso-8859-1 containing the euro
currency sign? does it work like iso-8859-1? where can I get hold of
it?
J Horacio MG dijo:
iso-8859-13 ... isn't it an extended iso-8859-1 containing the euro
currency sign? does it work like iso-8859-1? where can I get hold of
it?
My apologies, iso-8859-15 is the one which is an extended iso-8859-1.
Is anyone using this charset? If so, does it work just as
On 1999-09-04 14:03:30 -0400, Fairlight wrote:
After looking at the kernel source, the unicode docs, and not a
small amount of pestering of Alan Cox, who was kind enough to help
me, I've discovered that for (stock, American) Linux consoles, you
really want your .muttrc to say:
set
On Sat, Sep 04, 1999 at 10:15:21AM +0200, J Horacio MG blurted:
http://www.mutt.org is «the mother of all sites» ... well, as far as
mutt goes. There should be a link (in user's pages? or download?) to
where the .rpm's are located.
Okay, this has been bugging me for a bit. I've been seeing
Fairlight dijo:
On Sat, Sep 04, 1999 at 10:15:21AM +0200, J Horacio MG blurted:
http://www.mutt.org is «the mother of all sites» ... well, as far as
mutt goes. There should be a link (in user's pages? or download?) to
where the .rpm's are located.
So why do the 1/2 symbol and the
Fairlight dijo:
After looking at the kernel source, the unicode docs, and not a small
amount of pestering of Alan Cox, who was kind enough to help me, I've
discovered that for (stock, American) Linux consoles, you really want your
.muttrc to say:
set charset="ibm437"
And all is
Warning
Could not process message with given Content-Type:
multipart/signed; boundary=Izn7cH1Com+I3R9J; micalg=pgp-md5;protocol="application/pgp-signature"
51 matches
Mail list logo
