On Sunday, August 4, 2002 at 2:06:19 PM +0300, Jussi Ekholm wrote:
> Would it be possibly catastrophous, if I'd modify $send_charset so,
> that it would only send mails with character sets of 'ISO-8859-1'? Any
> insight?
Last time someone tried, some of his mails were labeled with
"unknown-8bit" charset. He lost his job, his wife is gone, car stolen,
and on the road children begun casting stones at him. I'd not recommend
it.
>>> ``�'' showed up as ``A�'' and such forth.
>> You mean 2 chars as "ä"?
> Yes, I mean those two chars that look like A�.
Let's be precise:
- "ä" C3 A4 (latin-1: A tilde, monetary sign) is the UTF-8 for �.
- "A�" 41 FE (latin-1: A, little thorn) is not a valid UTF-8 string.
> I tried to do something like this:
> :s/A�/�/g
:s/ä/�/g perhaps?
> in future I'd like to be able to replace as many occurences as there
> are of "A�" with that simple search-and-replace line.
Best is to have good setup on both sides: automatic UTF-8 decoding,
and/or no more UTF-8 at all.
> thanks for your ideas, I'll pass them to this friend
He could perhaps detail his iconv and $charset setup here? When
something is broken there, you see on your terminal raw chars without
charset conversion. UTF, but also all other charsets. Not so annoying
when all received mails are in the same charset as your terminal, but...
What gives:
| $ iconv -f utf-8 -t iso-8859-1 < /dev/null && echo OK
| OK
...OK, or unsuported as:
| $ iconv -f utf-8 -t silly-charset < /dev/null && echo OK
| iconv: conversion to silly-charset unsupported
And is his Mutt correctly linked with the library iconv functions?
And of course is his $charset="iso-8859-1"?
>> thanks to the CT parameter "x-action=pgp-signed" Mutt knows
>> automatically it must be PGP verified.
> What is CT parameter?
"Content-Type:" header field, with "parameter=value" thing.
>>> My traditionally signed mails show up correctly, right?
>> no, the signature is bad in my 1.4
It's due to my setup. Mutt 1.2.5 and a stock 1.4 verifies well your
signatures. I'm trying to find the culprit patch, compiling test
versions while I write this mail... Result later.
Later: it's a patch I (obviously badly) backported from 1.5 to
detect the "x-action=" parameter in inline PGP signed mails... It works
well, but seems to lead Mutt to first decode UTF-8 before passing the
mail to GPG. Unlike <check-traditional-pgp> (ESC P) which gives raw mail
to GPG. I'll have to look at this... :-(
Bye! Alain.
