On Mar 17, 10:56 am, TThierry <[email protected]> wrote: > Marcello, I considered sticking to a langage for internal purposes > (say : english). But at the same time, I'd like to display my results > for the user. It seems to me he could understand getting the names in > the local langage of the place, but would find it strange to have them > in english no matter where the place is, if he is not a native english > speaker. That's why I'd like to get the geocoding results in local > langage.
Yes, I understand that. But you said that the reason why you want to get results in the local language is because you want to compare them with a database you have. My suggestion would be that you build your database with multiple languages and then 1. Let the user type in any language 2. Send the query to your own server and see if the result already exists in your database 3. If found, then return it to the client and you're done, else query the geocoder from your server, getting the result in English 4. Now see if the English result exists in your databse, and if it does return it to the client in whatever language you want, and you're done. 5. If it doesn't exist then insert the English result in your own databse and return it in English to the client. 6. Periodically, add translations to other languages of newly inserted records in your database. Knowing that the geocoder will always use English will allow you a safer identification of the relevant record. If you try to do this identification in other languages you also have to deal with character encoding and directionality. -- Marcelo - http://maps.forum.nu -- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
