exotic characters handling about twitter HOT 4 OPEN

(I remember that I've sent an email some time ago on the mailing list about a related issue, but this issue was tested with the uptodate github version).

from twitter.

Hi Joel ...

This worked for a while and re-broke w/ the conversion to httr. I got it working "better" w/ httr last weekend, but still working on it.

from twitter.

OK, good to know there's nothing wrong on my side at least ;-)

On Mon, Mar 3, 2014 at 6:09 PM, Jeff Gentry [email protected]:

Hi Joel ...

This worked for a while and re-broke w/ the conversion to httr. I got it
working "better" w/ httr last weekend, but still working on it.

Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-36532554
.

Joël Gombin

Doctorant en science politique / PhD candidate in political science
CURAPP - Université de Picardie Jules Verne

277, rue du Faubourg Saint-Antoine
75011 Paris
Tel : +33 (0)6 61 55 22 41
www.joelgombin.fr

from twitter.

Nope. Even pre-httr there were characters that would slip through, and perhaps the current point is the same as it was before. The forceUtf8Conversion is removed as everything is being forced to UTF-8 in the httr call. FWIW, I'm doing this:

fromJSON(content(response, as="text", encoding="UTF-8"))

Which may or may not be the best thing to do w/ the JSON response in terms of getting the best results from httr.

from twitter.