Thanks Scott! I think you answered all my questions. To fill you in a tiny bit 
more, these e-mails are incoming press releases that I'm trying to get into the 
database (which is NOT a problem), but with the formatting retained (since most 
are HTML and I want to keep them that way...not to be interpreted, just to be 
displayed). It looks like translating quoted-printable is no biggie, so I'll 
start on that, but I have no idea what other sort of translation or 
transformation issues I'll run into (and of course didn't see this one coming). 
The devil indeed resides within the details!

Z

> -----Original Message-----
> From: Scott Klement [mailto:klemscot@xxxxxxxxxxxx]
> Sent: Tuesday, March 23, 2004 8:08 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Decode e-mail?
> 
> 
> 
> Hi Zak,
> 
> > Before I dive into this, with your experience and knowledge in this
> > area, would you say I'm heading into a tough battle here 
> and should find
> > existing code to somehow "retrieve" the mail item all 
> sorted out, or is
> > this a reasonable search-and-replace exercise?
> 
> I'm not completely sure what you're doing with the e-mail, so 
> it's hard to
> say whether it's going to be a "tough battle."
> 
> IMHO, decoding quoted-printable isn't that big of a deal...  just read
> lines at a time from the file into a big buffer until one of the lines
> does not end with =, or until the buffer is full.  Then, scan 
> character by
> character through the buffer looking for =, and when it's 
> found, replace
> with the appropriate value.  I'd do all of this in ASCII, and then
> translate the whole buffer to EBCDIC in one go at the end w/iconv(). 
  
NOTICE: This E-mail may contain confidential information. If you are not 
the addressee or the intended recipient please do not read this E-mail 
and please immediately delete this e-mail message and any attachments 
from your workstation or network mail system. If you are the addressee 
or the intended recipient and you save or print a copy of this E-mail, 
please place it in an appropriate file, depending on whether 
confidential information is contained in the message. 
 
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.