Please upgrade to a recent development version. These are stable,
and have this problem fixed.
On 2001-07-12 07:29:01 +0300, Alper Ersoy wrote:
>Date: Thu, 12 Jul 2001 07:29:01 +0300
>From: Alper Ersoy <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Strange behavior against uppercase Content-Type header
>Mail-Followup-To: [EMAIL PROTECTED]
>User-Agent: Mutt/1.2.5i
>
>Hello,
>
>Whenever I try to read a mail that has the Content-Type header in
>uppercases, mutt complains about unsupported mime-type and forces me to
>press v and select the part from the list.
>
>I investigated further and found that this only happens when the mime-type
>has "I" in it. My locale (specifically, LC_CTYPE is "tr_TR.iso-8859-9") is
>set to turkish. And in turkish (iso-8859-9 or latin5), the lowercase
>equivalent of I is ? (dotless i with my font). Therefore, when "PLAIN" is
>encountered, it is translated to "pla?n", which is meaningless to mutt.
>Mutt reads mails with strange types, ie. "TeXt/PLAiN", without problems as
>long as those chars' lowercase equivalents are the same in iso-8859-1 and
>iso-8859-9.
>
>Setting LC_ALL to "C", I was able to read those mails without this problem.
>However, I lose the language specific chars with this approach.
>
>I think the best solution would be using a fixed table (iso-8859-1) to
>translate mime-types to lowercase, as all mime-types are in iso-8859-1
>character set.
>
>--
>Alper Ersoy
>
--
Thomas Roessler http://log.does-not-exist.org/
