Re: Bug #30 in Mail_mime

On 4/5/06, bertrand Gugger <bertrand@toggg.com> wrote: > > Is it actual with php5 handling of unicode ? obsolutely not, the bug was submitted before the release of PHP5 No idea how a patch can be licensed , "from scratch" does not exist as > license. :o) Now that my patch is publicily available and without any licensing term, it is in the public domain. Everybody can relicence it as needed. So, that's the way I think it is ... The point I was talking about is that, if the patch of "mdv at inyourpocket dot com" is considered as a derived thing of kmail, then it is under GPL, and Mail_mime must become GPL... witch is impossible... In reply to Sean : for unitest, I don't have the time sorry, but for i18n, I've many ideas. The first one is that email headers are agnostic about i18n. They bother only for 7bits chars. Personnaly, i send emails in utf-8, and that works well. I've also read some code from http://phpmailer.sourceforge.net/ and squirrelmail . The only i18n thing that may be managed is to choose the best encoding between quoted-printable and base64. The choice is made with one unique criteria : the length of the resulting encoded string. Nicolas