Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.lang.php
Subject: Re: Encoding Problems
Date: Sun, 06 Jul 2014 01:36:20 +0200
Lines: 36
Message-ID: <53B88BF4.4070600@arnowelzel.de>
References: <lp19to$r2$1@dont-email.me> <53B7520B.8080506@arnowelzel.de> <53b754c5$0$6705$9b4e6d93@newsspool2.arcor-online.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net I3B7+N1qZaWDHUW5BEwWwQqauP1ueh0Ympks5f9bI6jIoKCVbo
Cancel-Lock: sha1:sNOZ367btABGpRlxPO1jSEym8Bg=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
In-Reply-To: <53b754c5$0$6705$9b4e6d93@newsspool2.arcor-online.net>
X-Enigmail-Version: 1.6
Xref: csiph.com comp.lang.php:14067

Christoph Michael Becker, 2014-07-05 03:28:

> Arno Welzel wrote:
> 
>> So extend that for the encoding:
>>
>> if($msgStructure->subtype=="PLAIN")
>> {
>>   switch($msgStructure->encoding)
>>   {
>>   case 4:
>>     // Body text is quoted-printable encoded
>>     $body = quoted_printable_decode($body);
>>     break;
>>
>>   case 3:
>>     // Body text is base64 encoded
>>     $body = base64_decode($data);
>>     break;
>>   }
>>
>>   $body = renderPlainText($body);
>> }
> 
> What about a default clause, at least triggering a notice/warning that
> the encoding is not understood?

Good Point. But which other encoding except no encoding at all, base64
and or quoted printable may be used?


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de