* [EMAIL PROTECTED] on Saturday, September 01, 2007 at 14:24:47 -0400
I was able to get mutt and bash to agree on en_US.ISO8859-1,
but there is no option for that in Terminal.app's preferences.
I only see Western (ISO Latin 1) and Western (ISO Latin 9)
[In fact, I even opened up Terminal.app's
On Saturday, September 1, 2007 at 14:24:47 -0400, [EMAIL PROTECTED] wrote:
I made all three agree on en_US.UTF-8, and the result was terrible.
Most accented chars still were garbled.
Strange: I've seen reports about this very setting working OK on
MacOS-X. The shell command locale charmap
Hello,
On Wednesday, August 29, 2007 at 15:49:35 -0400, [EMAIL PROTECTED] wrote:
the correctly-shown from is the very first time, ever, in my history
with mutt that an accented character has been displayed. Normally,
I get either a single question-mark or a double one.
This means that
Thus spake Alain Bench [09/01/07 @ 11.14.46 +0200]:
the correctly-shown from is the very first time, ever, in my history
with mutt that an accented character has been displayed. Normally,
I get either a single question-mark or a double one.
This means that your terminal does UTF-8,
Thus spake [EMAIL PROTECTED] [09/01/07 @ 14.24.47 -0400]:
I made all three agree on en_US.UTF-8, and the result was terrible. Most
accented chars still were garbled. Plus, I sent a test mail to myself with
some accented chars, and although they looked fine when I sent it, they were
Hi folks,
I know, I'm a little off-topic, but I have a question about a charset issue:
On Tue, Aug 28, 2007 at 02:39:54PM -0400, Cristóbal M. Palmer wrote:
^^
Cristóbal Palmer
^
I have a clean mutt 1.5.16 running on a linux with locale
On Wed, Aug 29, 2007 at 10:36:07AM +0200, Alexander Dahl wrote:
Did I miss some in my configuration (I can't imagine), is this a bug in
mutt I should report or is it a wrong coded mail?
Fair chance it's me. I've seen the same miscoding in my boss's
inbox. He uses alpine:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, August 29 at 10:36 AM, quoth Alexander Dahl:
On Tue, Aug 28, 2007 at 02:39:54PM -0400, Cristóbal M. Palmer wrote:
^^
Cristóbal Palmer
^
Headers are only allowed to be sent in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, August 29 at 05:44 AM, quoth Cristóbal M. Palmer:
It'd be awesome if somebody on this list could point out where I'm
erring.
Hmm... Presumably, that's set in your muttrc via 'set realname=...',
right? My first guess would be that
On 29.08.2007 (07:08), Kyle Wheeler wrote:
Hmm... Presumably, that's set in your muttrc via 'set realname=...',
right? My first guess would be that you need to tell mutt what charset
you've encoded the muttrc file in (it assumes ascii unless you set
config_charset to something). You'll need
this seems to work. At least a test mail I sent to myself did. Let's
see how this one fares...
Looks fine on my side. :-)
--
* http://www.lespocky.de ***
GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0
pgpRB3XEkILEY.pgp
Description:
Hi Kyle,
The subject? You mean your *From* header, right?
Sure the From header, sorry about that. O:-)
Greets
Alex
--
* http://www.lespocky.de ***
GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0
pgpmtNu4dXqLI.pgp
Description: PGP
On Wednesday, August 29 at 03:35 PM, quoth Eyolf Østrem:
On 29.08.2007 (07:08), Kyle Wheeler wrote:
Hmm... Presumably, that's set in your muttrc via 'set
realname=...', right? My first guess would be that you need to
tell mutt what charset you've encoded the muttrc file in (it
assumes ascii
Thus spake Alexander Dahl [08/29/07 @ 10.36.07 +0200]:
Hi folks,
I know, I'm a little off-topic, but I have a question about a charset issue:
On Tue, Aug 28, 2007 at 02:39:54PM -0400, Crist??bal M. Palmer wrote:
^^
Crist?bal Palmer
14 matches
Mail list logo
