Mark Crispin wrote:
Are you back to maintain c-client?
I maintain c-client for my own purposes, but I am no longer in the business of
developing or maintaining it for others.
But, after digging around the code, I found out a previous developer never
finished the code to
decode rfc2047. I hav
> Are you back to maintain c-client?
I maintain c-client for my own purposes, but I am no longer in the business of
developing or maintaining it for others.
> But, after digging around the code, I found out a previous developer never
> finished the code to
> decode rfc2047. I have just complete
Are you back to maintain c-client?
But, after digging around the code, I found out a previous developer never finished the code to
decode rfc2047. I have just completed the coding and now the filename is decoded correctly.
Regards,
Shawn
Mark Crispin wrote:
utf8_mime2text() decodes RFC 2047
utf8_mime2text() decodes RFC 2047 encoded words.
It does not, and was never intended to, decode RFC 2231 extended parameters.
The application is responsible for assembling RFC 2231 extended parameters,
and then calling utf8_mime2text() on the assembly if desired.
-- Mark --
http://panda.com/mr
I have a message from the latest thunderbird client that is setting the
filename as:
Content-Disposition: inline;
filename*0*=ISO-8859-1''%65%78%65%6D%70%6C%65%2D%64%E9%64%E9%6D%2D%31%2E;
filename*1*=%35%2E%70%64%66
The issue is that utf8_mime2text isn't decoding the filename. Is there an up
