[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unrecognized character sets: windows-1252 -- and us-asciixxx
>At 9:36 PM -0800 11/27/00, Earl Hood wrote:
>
>>Looking at mhtxtplain.pl, it appears the text/plain filter only
>>keys off the CharsetConverters for "-decode-" charsets (note:
>>CharsetConverters are used for non-ASCII encoded data in message
>>headers).
>>
>>... The filter should
>>probably be changed to key completely off CharsetConverters.
>>
>>In the mean time, you can comment out the warning statement from
>>mhtxtplain.pl.
OK, I think I misunderstood what you meant before. The "-decode-"
business is complicated, so I'll just leave that to you. But instead
of commenting out the warning statement, I think I'll try to have it
emailed to me. That way, I'll still get them.
BTW, I received a different warning the other day:
Warning: Unrecognized character set:
us-ascii<002101c05b35$8e6aeba0$c581e0d8@fred>
Which seemed to have been generated by an email with this in the header:
Content-Type: text/plain; charset=us-ascii
<002101c05b35$8e6aeba0$c581e0d8@fred>
Weird! I guess that person's email program didn't generate the header
correctly?
Bob
[Index of Archives]
[Bugtraq]
[Yosemite News]
[Mhonarc Home]