Kees Jongenburger <[EMAIL PROTECTED]> wrote:
On Wednesday 07 April 2004 12:20 pm, Simon Groenewolt wrote:
I think the Jakarta HttpClient Kees suggested might be the most robust solution, but that will make the email application dependent on another library, I don't know if that's a good thing. I'll try to make a really simple content-type parser first.
Yes it does but its freely downloadable And that's not true for activation and javamail.
I think that even so, depending on another application just for parsing the
Content-Type is rather over kill.
I agree. And besides that I didn't find a magic method automatically using the right encoding there either.
It can be implemented in 2 or 3 lines, which would be even less than the documetnation you would need to explain why we use httpclient in the first place.
I do not agree on the 2 or 3 lines... for only getting the 'charset=' part that is correct, but there also are the default encodings for txt/html vs. txt/xml and such. Probably there's more, and you also have some defaults to take into account.
I'll make something I can use for myself now, and give the code to the email maintainer (Daniel?) later when I've looked a bit more into the details of the Content-Type header.
Simon
