It'd be nice if it wouldn't. :) If it knows how to autocomplete the name, why doesn't it save the actual name?
Got this answer from the Geo Technologies folks at Yahoo:
Think of it this way : London is the UK and US version of "London", Londra, the Italian and Londres and French. In this case the spelling is different and we would be incorrect to return London if Italian or French language support is specified.
We call these sorts of issues "exonyms" ... it's the way significant place names are spelt outside of their country and language of origin. Not all places rate an exonym and the fact that the spelling of the English exonym of this Finnish town is identical to the Finnish original but less the accents is sort of clouding the issue.
Here is what we get back from YQL:
<place xml:lang="en-US" yahoo:uri="http://where.yahooapis.com/v1/place/566473"> <woeid>566473</woeid> <placeTypeName code="7">Town</placeTypeName> <name>Jyvaskyla</name> <country code="FI" type="Country">Finland</country> <admin1 code="FI-LS" type="Province">Western Finland</admin1> <admin2 code="" type="Region">Central Finland</admin2> <admin3/> <locality1 type="Town">Jyvaskyla</locality1> <locality2/> <postal/> <centroid> <latitude>62.240490</latitude> <longitude>25.751289</longitude> </centroid> <boundingBox> <southWest> <latitude>62.175419</latitude> <longitude>25.604650</longitude> </southWest> <northEast> <latitude>62.298199</latitude> <longitude>25.882360</longitude> </northEast> </boundingBox> </place>
We may work on a way to override the name as a future enhancement.
IIRC they're using a 3rd party location library. So it might be some bug there. (See my other post with an issue in it)