| Issue 503: | Twitter excluding accented words from unaccented search | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
If you ask twitter search for San Jose, it does not return tweets containing San José. If maybe not by default, this should at least be an option in the API, since many people do not accent their words from cell phones, and querying every single accentable vowel is just a burden on the search engine and slows down responses. |
||||||||||||
,
Apr 22, 2009
(No comment was entered for this change.)
Labels: Component-Search
|
|||||||||||||
,
Apr 22, 2009
(No comment was entered for this change.)
Status: Accepted
Owner: m...@twitter.com Labels: -Priority-Medium Priority-Low |
|||||||||||||
,
Jun 15, 2009
I believe I have found the root cause of this issue at last. Some sub-set of accented words are not affected (wäre/ware) but the majority are. I'm working on a fix. |
|||||||||||||
,
Jun 15, 2009
Excellent - this is a very very much awaited improvement. Thanks! |
|||||||||||||
,
Jun 16, 2009
When the change goes out the current behavior will change and old data will become inaccessible. All new data going forward will be ok so as old data becomes inaccessible the issue will become 100% fixed. Working on when that will be now. Should be in the next few days. |
|||||||||||||
,
Jun 23, 2009
The fix for this is blocked behind another search change. I'll update when it is deployed. |
|||||||||||||
,
Jun 29, 2009
Launched at last. Queries for "Jose" and "José" will now be equal. This corrects data from now one but previous data will not be corrected. As search moves forward the bad data will become inaccessible.
Status: Fixed
|
|||||||||||||
,
Jun 29, 2009
And it is working perfectly! The very first query I made returned an accented result - great!!! http://search.twitter.com/search?geocode=9.748917,- 83.753428,500mi&max_id=2396275119&page=1&q=+san+jose+near:"costa+rica"+within:500mi |
|||||||||||||
 Sign in to add a comment
|
|||||||||||||
