I'm not sure what are considered "special" characters either, but from
what I can tell this particular case seems to be a combination of
factors. For some reason, by using the +OR+ it seems to be matching
anything that has a period character in it. However, if you do the
queries separately, they seem to work (albeit the second one doesn't
return any data).


I don't know if doing separate queries will work for you, but maybe
that's another option.

On Dec 14, 2:52 pm, Howard <h0w4...@gmail.com> wrote:
> Hi Everyone,
> The following query, which includes a period, returns nonsensical
> results:http://search.twitter.com/search.atom?q=%22Battle+for+Bean+Street%22+...
> Removing the period fixes it. I've looked 
> athttp://apiwiki.twitter.com/w/page/22554756/Twitter-Search-API-Method:...
> and can't find anything about how special characters are treated.
> Which characters are considered special and what're the rules
> regarding them?
> Thanks all!

Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to