mhonarc-users

Re: MHonArc warning summary

1999-09-12 22:52:46
On September 11, 1999 at 16:30, archive(_at_)marmot(_dot_)jab(_dot_)org wrote:

      3        Warning: Unrecognized character set:  

Hmm.  A blank charset setting.  Should probably check for this.

      1        Warning: Unrecognized character set: iso-8859-13 
      4        Warning: Unrecognized character set: iso-8859-15 

Does anyone have URLs that show the mappings for iso-8859-13 and
iso-8859-15?  Basically, any iso-8859-11 or greater mapping pointers
will be helpful.

      2        Warning: Unrecognized character set: us-ascii^\multipart/mixed
 
      7        Warning: Unrecognized character set: us-ascii^\text/plain 

These two concern me a bit.  I'm wondering if MHonArc is having
problems parsing the charset correctly, or the messages themselves are
screwed up.

The trick with charsets is knowing what to do with them.  When
an unrecognized one is encountered, MHonArc punts and just escapes
HTML specials.

The general problem with charsets is that a MIME message may not map
well into a single HTML document since a MIME message can have multiple
parts, each with there own charset.  Going to UTF8 can be a solution,
but then there will have to be a full charset mapping library.

     27        Warning: Unrecognized time zone, "+-100" 
      1        Warning: Unrecognized time zone, "+-200" 

I guess the MUA could not make up its mind.

      1        Warning: Unrecognized time zone, "AKDT" 
      7        Warning: Unrecognized time zone, "CEST" 
      1        Warning: Unrecognized time zone, "EASTERN" 
      1        Warning: Unrecognized time zone, "EST5EDT" 
      2        Warning: Unrecognized time zone, "GMT+0" 
      5        Warning: Unrecognized time zone, "GMT+0100" 
     58        Warning: Unrecognized time zone, "GMT0BST" 
      1        Warning: Unrecognized time zone, "METDST" 
      4        Warning: Unrecognized time zone, "MEZ-1" 
      5        Warning: Unrecognized time zone, "Z" 

Some of these could be added to TIMEZONES.  The GMT+ ones could
be handled by puting more intelligence in zone parsing.  The
brute force method of defining them in TIMEZONES can work also.

        --ewh

<Prev in Thread] Current Thread [Next in Thread>