I've noticed a difference in the localization of results on the HTTP geocoder which I'm not sure is intentional. The V2 reverse geocoder defaulted the language of the locality names to the local language, while the V3 returns them all in english.
For example: V3: http://maps.google.com/maps/api/geocode/xml?latlng=34.3937,132.464&sensor=false V2: http://maps.google.com/maps/geo?q=34.3937,132.464&output=xml&sensor=false The V3 locality/country/etc names are all in English, while the V2 results tend to be in the local language of the geocoded location. I've tried this with points in several countries and the behavior is consistent. While I could set the output language manually, if I want the local name of a place this would require twice the number of geocoder requests to accomplish. The docs however do not mention a difference in behaviors with respect to the language/hl parameters V2: http://code.google.com/apis/maps/documentation/geocoding/v2/index.html#GeocodingRequests V3: http://code.google.com/apis/maps/documentation/geocoding/#GeocodingRequests Is this the new default behavior or am I missing something? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
