lexer, tokens, and content-types

[David Relson]

Scott,

It sounds like it has everything we need for decoding.  It even uses (can 
use?) iconv which has been mentioned as a charset solution.  Sounds too 
good to be true.  Wonder what's missing?

David

At 04:10 PM 12/9/02, Scott Lenser wrote:

>I've been using libgmime and here's my opinions on it.  The interface is
>slightly complicated but very flexible.  The interface is actually very well
>designed and pretty intuitive.  The main problem with the interface is that
>while all the methods are well documented as to what types that take, 
>sometimes
>the documentation is missing info on the intended way of doing things.  Some
>examples are included though mostly in the form of unit tests.  I have a 
>version
>derived from bogofilter 0.7 using libgmime 1.90.6 which grabs everything 
>except the
>content-encoding fields.  I haven't bothered to try to track down the getting
>access to the content-encoding field since it properly decodes it in all 
>cases.
>The library seems to be under pretty active development and has good support
>for pretty much everything I could think you could want.  It supports a wide
>variety of RFCs and seems very interested in following the standards.  It
>has a _lot_ of features and is GPL'd.
>
>The following data sources are supported:
>
>memory buffer
>FILE *
>FILE * with offsets to begin/end of range to use
>file descriptor
>file descriptor with offset to begin/end of range to use
>memory mapped file
>memory mapped file with offset to begin/end of range to use
>
>The following types of encoding are handled:
>
>7bit
>8bit
>binary
>base64
>quoted printable
>uuencode

... [snip ] ...

>Additional features:
>
>error output redirection (uses glib for this, I don't know how it works
>   exactly)
>parses from, to, etc lines into list of email addresses.  Parses the email
>   addresses into name sections and email address sections
>iconv integration.  Supports using iconv to convert character sets.  I
>   haven't looked at this much