On Sun, Oct 06, 2002 at 03:35:17PM +0200, Alain Bench wrote: > 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.
This happened due to the recent installation of Red Hat Linux 8.0, which defaults to using UTF-8 charset, while my previous system (Red Hat Linux 7.3) used ISO-8859-1. My signature file as well as the attachment sent in the previous email were created using the ISO-8859-1 charset and I did not completely understand the consequences of just installing the new version of Linux and its change to unicode. I have just changed my LANG definition from us_US.UTF-8 to us_US in my /etc/sysconfig/i18n configuration file and things seem to be working as expected now. Can you confirm this? Thanks for pointing the problem out. Romildo -- Prof. José Romildo Malaquias Departamento de Computação - Universidade Federal de Ouro Preto http://www.decom.ufop.br/prof/romildo/ [EMAIL PROTECTED] http://uber.com.br/romildo/ [EMAIL PROTECTED]
