[prev in list] [next in list] [prev in thread] [next in thread]
List: mhonarc
Subject: Re: Unrecognized character set: windows-1252 [2nd try]
From: Robert Hsiung <dr-bob () uchicago ! edu>
Date: 2000-12-01 16:58:31
[Download RAW message or body]
At 9:36 PM -0800 11/27/00, Earl Hood wrote:
> > ><CharsetConverters>
>> >windows-1252; iso_8859::str2sgml; iso8859.pl
>> ></CharsetConverters>
>> >
> > >http://www.xray.mpe.mpg.de/mailing-lists/mhonarc/2000-06/msg00002.html
>>
>> didn't work, and that's what I would've tried (maybe without the
>> spaces).
>
>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).
>
>All other sets it does its own internal checks. The filter should
>probably be changed to key completely off CharsetConverters.
>I cannot remember the initial reason why I did not do that way
>in the first place.
>
>In the mean time, you can comment out the warning statement from
>mhtxtplain.pl.
Thanks for responding. Do you mean I should (1) take this section:
## Check MIMECharSetConverters if charset should be left alone
if (defined($readmail::MIMECharSetConverters{$charset}) and
$readmail::MIMECharSetConverters{$charset} eq "-decode-") {
$asis{$charset} = 1;
}
and make it:
## Check MIMECharSetConverters if charset should be left alone
if (defined($readmail::MIMECharSetConverters{$charset})) {
$asis{$charset} = 1;
}
and in addition (2) add the above CharsetConverter? I just don't want
to screw everything up. Thanks,
Bob
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic