I agree this is the way to go. We can add a mechanism to change the default encoding, but leave things as they are by default.
Mike On 10/19/06, Roland Weber <[EMAIL PROTECTED]> wrote:
Hi Odi, > Look at RFC 2047 which updates RFC 1521. This method is quite popular in > E-Mail traffic. Maybe real-world HTTP servers and clients support it? Maybe, but MIME encoding is not really our line of work. If somebody is willing to come up with a patch, I would suggest to implement something similar to the non-ASCII HTTP headers we already have, to be used at the application developer's risk. http://jakarta.apache.org/commons/httpclient/apidocs/org/apache/commons/httpclient/params/HttpMethodParams.html#HTTP_ELEMENT_CHARSET cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
