Path: news.ruhr-uni-bochum.de!news.rhrz.uni-bonn.de!news.rwth-aachen.de!uni-paderborn.de!fu-berlin.de!news.mathworks.com!op.net!netaxs.com!nntp.teleport.com!usenet
From: Eryq <[email protected]>
Newsgroups: comp.lang.perl.announce,comp.lang.perl.misc
Subject: MIME-parser 1.13 uploaded to CPAN
Followup-To: comp.lang.perl.misc
Date: 25 Jul 1996 04:41:16 GMT
Organization: Little or none...
Lines: 57
Approved: [email protected] (comp.lang.perl.announce)
Message-ID: <[email protected]>
NNTP-Posting-Host: julie.teleport.com
X-Disclaimer: The "Approved" header verifies header information for article transmission and does not imply approval of content.
Xref: news.ruhr-uni-bochum.de comp.lang.perl.announce:381 comp.lang.perl.misc:38762

The latest release of the "MIME-parser" package has been uploaded to the
CPAN under my author id (ERYQ) and name (Eryq).

Current version:        1.13

Major changes:          Now tolerates header fields where the ":" is
                       followed by zero or more characters of linear
                       whitespace (not tolerating them was a bug).

------------------------------------------------------------

NAME

   MIME-parser - family of MIME:: modules for parsing MIME messages

DESCRIPTION

   MIME-parser is a collection of Perl5 MIME:: modules for parsing
   and decoding single- or multipart (even nested multipart!) MIME
   messages.

SYNOPSIS

   You start by creating an instance of MIME::Parser, and setting up
   certain parsing parameters: what directory to save extracted files
   to, how to name the files, etc.

   You then give that instance a readable filehandle on which waits a
   MIME message.  If all goes well, you will get back a MIME::Entity
   object, consisting of a MIME::Head (which holds the MIME header
   data) and the name of the file in which the (decoded) body has been
   stored.

   If the original message was a multipart document, the MIME::Entity
   object will have a non-empty list of "parts", each of which is in
   turn a MIME::Entity (which might also be a multipart entity, etc,
   etc...).

   Internally, MIME::Parser asks for instances of MIME::Decoder
   whenever it needs to decode an encoded file.  MIME::Decoder has
   a mapping from supported encodings (e.g., 'base64') to classes
   whose instances can decode them.  You can add to this mapping
   to try out new/experimental encodings.  You can also use
   MIME::Decoder by itself.

AUTHOR

   Eryq, [email protected]
   28 April 1996

--
  ____           __
 / __/__________/_/  Eryq ([email protected])
/ __/ _/ / / , /     Hughes STX, NASA/Goddard Space Flight Cntr.
/___/_/ \  /\  /___
       /_/ /_____/   http://www.mcs.net/~eryq

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.