in reply to Re^2: Decoding UTF-8 charset in an .EML file (RTFBP)
in thread Decoding UTF-8 charset in an .EML file

So you're not even going to try ? I mean, I got it on the first guess.

MIME::Base64 is most of the solution, it appears. But that really was just a guess (but it produces 'Cancellation <Cancellation@norvergence.com>' from your example).

Update: Note that the CC list is even more "revealing", especially considering all of the "RE.MO.VI.NG" you did. (:

(note the (unmodified) sig) I thought you're "lack of effort" deserved some ribbing, as did (even more so) the all-too-common response to "lack of effort" around here. Enjoy.

- tye        

Replies are listed 'Best First'.
Re^4: Decoding UTF-8 charset in an .EML file (RTFBP)
by japhy (Canon) on Nov 15, 2006 at 18:06 UTC
    If I had recognized the encoding as Base-64, I would have investigated it as such. As it stands, I had no idea what the encoding was (I thought it was some UTF-specific shenanigans). merlyn had mentioned on #perl that any MIME reader should be able to grok it, but I have no experience with the MIME::* modules. It wasn't until I looked at MIME::Parser that I followed the trail that led me to my goal.
    Jeff japhy Pinyan, P.L., P.M., P.O.D, X.S.: Perl, regex, and perl hacker
    How can we ever be the sold short or the cheated, we who for every service have long ago been overpaid? ~~ Meister Eckhart
[reply]

      I didn't recognize the encoding as base-64. I actually looked at the encoding and spent a few seconds thinking about it. At that point I noticed that it used letters of both case and digits and so I tried to think of encodings that used such. base-64 and uuencode both do that and a quick test showed that base64 worked.

      I didn't let some initial guess ("UTF-specific shenanigans") prevent me from trying to solve the problem. (: Just FYI.

      - tye        

[reply]

In Section Seekers of Perl Wisdom