>A potential solution would be to put the different message parts into
>different files in the archive, and use the remainder of the message as
>a container for URLs to those files, mimicking the MIME message
>structure in HTML. I haven't looked to see how/if one can do that in
>MHonarc, but thi
In <[EMAIL PROTECTED]>,
Jeff Breidenbach <[EMAIL PROTECTED]> wrote:
>
>>This is the problem, HTML does not support mixed character sets.
>>Also, the charset affects the entire HTML document. Therefore, your
>>resource settings would have to conform with the charset, and this
>>can be a big proble
>This is the problem, HTML does not support mixed character sets.
>Also, the charset affects the entire HTML document. Therefore, your
>resource settings would have to conform with the charset, and this
>can be a big problem if messages existing in the archive have different
>specified charsets.
On April 20, 2000 at 12:05, Jeff Breidenbach wrote:
>
>
> But as far as I can tell, MHonArc won't produce that meta tag. Thus
> the character set information is lost, which can result in a difficult
> to render web page.
>
> I suspect there is a reason for this, but I'm not sure what it
> is
In mhonarc.rc (in our installation in mhonarc/lib/perl5/site_perl/ )
you can override the and similar with
entries like
--
:
--
Of course you will want to convert incoming mail the that
character set beforehand. Also, this does not cover the
Subject: lines, attachment etc. Worst: to me i
Recently, I've been on an internationalization/localization kick.
I just read the relevant portion of the HTML specification
and found it refreshingly clear.
Let's assume I want to process an email with some weird character set,
like ISO646-SE. It appears the right thing for MHonArc to do is
pro
