Same thing's happening to me. Check out:
http://search.twitter.com/search.json?q=%23jimromeisburningcallback=doghttp://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
Should look like this:
dog(
{
- -
results: [
- -
{
- from_user_id_str:
Do you have more details about the specific illegal character(s) you're
receiving? How frequently are you polling the API? Have you tried
reproducing your scenario outside of a browser-based environment?
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Mon, Jun
Taylor();
I took a pic of firebug here:
https://docs.google.com/leaf?id=0B1lcI5OlKM2xNDczZDdmYTMtMjFjZi00Y2E2LWE4MTMtM2YyM2I5ZTM4Njhlsort=namelayout=listnum=50
It is similar to this case (I believe the same chars)
Oh answers to #2 and #3
2) I am polling the jsonp api every second in this test but it will be
changed for production to like 6 seconds and cached after all 30 feeds are
loaded
3) No, I haven't tried outside the browser since this is strictly a jsonp
feed and I chose jsonp over server-side xml
It would be very helpful if you could provide a specific Tweet ID that
is exhibiting this behavior -- the test case you're presenting is a bit
artificial. Do you know if the environment you're doing this consumption is
fully capable of understanding the UTF-8 character set? Tweets can contain
just
Taylor,
Firefox 4.01 on Windows Server 2003 and IE8 on Windows Server 2003
(I believe they are both fully utf-8 compatible)
(using jQuery 1.3.2 js library, I would upgrade but I am stuck at it w/
other dependencies )
Can you not reproduce the error on the jsFiddlehttp://jsfiddle.net/NBCGf/34/?
