Hi José,
On Wednesday, October 2, 2002 at 7:44:24 PM -0300,
José Romildo Malaquias signed:
> Content-Type: text/plain; charset=utf-8
>
> --
> Prof. Jos� Romildo Malaquias
^
> Departamento de Computa��o - Universidade Federal de Ouro Preto
^^
Strange there are those UTF-8 unknown replacement chars U+FFFD here.
Should have been "José" and "Computação" I guess, and that is writable
in Latin-1.
What is your $charset? Your sigfile is written in the same?
> Content-Type: text/plain; charset=utf-8
> Content-Disposition: attachment; filename="mutt.spec"
>
> Comment[sv]=E-postl�sare
^
> * Tue Oct 01 2002 Jos� Romildo Malaquias <[EMAIL PROTECTED]> 1.4-4
^
> * Mon Jun 19 2000 Trond Eivind Glomsr�d <[EMAIL PROTECTED]>
^
Same problem applies to attached text file. But here there is the
solution to declare the right charset when you attach the file: in
compose menu use <edit-type> (^T by default), replace by the file's real
charset, and refuse the proposed conversion.
I wonder if there is a way to declare a different default charset
for texts to be attached. This could be usefull in situations like, say:
All your text files are Latin-1 (or US-Ascii), but you use Mutt on an
UTF-8 terminal. So $charset=utf-8, you view and edit UTF-8 mails, but
attach Latin-1 (or less) files. Someone knows?
I tried to tweak ~/.mime.types for asc/txt extensions, but didn't
succeed. Something like:
| text/plain; charset=iso-8859-1 asc txt
Bye! Alain.
