Placename disambiguation is something we've wrestled with a lot lately. The way we do it now is: (a) find the most likely origin you meant based on proximity & size; (b) if we have historical data, choose the most likely destination given previous popularity, and (c) whatever the case, give prompts on each one to let you tell us you meant a different one.
Also, we don't currently support multi-city trips, so that would've confused the search parser.
But just running these searches now, they seem to give results:
Placename disambiguation is something we've wrestled with a lot lately. The way we do it now is: (a) find the most likely origin you meant based on proximity & size; (b) if we have historical data, choose the most likely destination given previous popularity, and (c) whatever the case, give prompts on each one to let you tell us you meant a different one.
Also, we don't currently support multi-city trips, so that would've confused the search parser.
But just running these searches now, they seem to give results:
http://adioso.com/us/boston-massachusetts-to-tunis-tn
http://adioso.com/tn/tunis-tn-to-barcelona-es
But yeah I know what you mean; the results can be baffling when they're not what you expect.
Thanks for sharing your experience.