|
|
|
date: Mon, 1 Oct 2007 07:56:00 -0700,
group: microsoft.public.mappoint.webservice
back
RE: Addresses not translated in GetLocationInfo
It's not true. We noticed that many, if not all, of the MapPoint Web Services
are translated into different languages such as driving directions,
definitely not just maps. As I mentioned, the returned places names of
GetLocationInfo are indeed translated into the language we specify, but the
returned addresses form GetLocationInfo are not translated. I believe it is a
bug, not supposed to be like that. It is especially important to have the
addresses in its native language, but our previous case only returns
addresses in English. We hope the bug will be fixed soon.
"Derek Chan" wrote:
> Hi,
>
> Specifying the language only determines the language the map is generated in
> and does not affect geocoding properties. Therefore what you are
> experiencing is not an error.
>
> Regards,
> --
> Infusion Development
> http://www.infusiondev.com
>
>
> "xshen" wrote:
>
> > We found that addresses returned from GetLocationInfo for the location in
> > Netherlands (lat=52.37552, lon=4.89289) are always the same no matter what
> > languages you specify (en, es, nl, de) while the returned places names are
> > translated in the corresponding language. Is it an error?
date: Wed, 3 Oct 2007 07:19:01 -0700
author: xshen
RE: Addresses not translated in GetLocationInfo
Sorry forgot to add that driving directions do get translated into the
language specified. I believe there is an issue with the language settings
for reverse geocodes as described and its best that you bring up the issue
with your Microsoft Representative so they can escalate appropriately.
Regards,
--
Infusion Development
http://www.infusiondev.com
"xshen" wrote:
> It's not true. We noticed that many, if not all, of the MapPoint Web Services
> are translated into different languages such as driving directions,
> definitely not just maps. As I mentioned, the returned places names of
> GetLocationInfo are indeed translated into the language we specify, but the
> returned addresses form GetLocationInfo are not translated. I believe it is a
> bug, not supposed to be like that. It is especially important to have the
> addresses in its native language, but our previous case only returns
> addresses in English. We hope the bug will be fixed soon.
>
> "Derek Chan" wrote:
>
> > Hi,
> >
> > Specifying the language only determines the language the map is generated in
> > and does not affect geocoding properties. Therefore what you are
> > experiencing is not an error.
> >
> > Regards,
> > --
> > Infusion Development
> > http://www.infusiondev.com
> >
> >
> > "xshen" wrote:
> >
> > > We found that addresses returned from GetLocationInfo for the location in
> > > Netherlands (lat=52.37552, lon=4.89289) are always the same no matter what
> > > languages you specify (en, es, nl, de) while the returned places names are
> > > translated in the corresponding language. Is it an error?
date: Thu, 4 Oct 2007 11:19:02 -0700
author: Derek Chan
RE: Addresses not translated in GetLocationInfo
Hello,
Street address are never translated regardless of the MP service only the
higher level geographic entities like countries, major bodies of water,
sometimes state/provinces. For instance, even if you set the a map to french
only those types of entities are translated, if you zoom down to the street
level you'll see that the streets are in the native language (with one little
caveat). The caveat that I mention is that some countries don't have the
street data in the native language but instead it's transliterated (not to be
confused with tranlation). You'll find that that in several countries in
Eastern Europe such as the Ukraine and Russia. Matter of fact, if you want
to geocode city names in those countries the geocoder is looking for the
transliterated strings, not native cyrillic (the capitals are probably
exceptions).
For directions only the fillers are translated and the street names remain
the same, which is completely logical because when navigating you need your
directions to reflect what's on the street signs, translating them makes
absolutely no sense.
The reverse geocoder is reflecting this.
Steven Pushee
"Derek Chan" wrote:
> Sorry forgot to add that driving directions do get translated into the
> language specified. I believe there is an issue with the language settings
> for reverse geocodes as described and its best that you bring up the issue
> with your Microsoft Representative so they can escalate appropriately.
>
> Regards,
> --
> Infusion Development
> http://www.infusiondev.com
>
>
> "xshen" wrote:
>
> > It's not true. We noticed that many, if not all, of the MapPoint Web Services
> > are translated into different languages such as driving directions,
> > definitely not just maps. As I mentioned, the returned places names of
> > GetLocationInfo are indeed translated into the language we specify, but the
> > returned addresses form GetLocationInfo are not translated. I believe it is a
> > bug, not supposed to be like that. It is especially important to have the
> > addresses in its native language, but our previous case only returns
> > addresses in English. We hope the bug will be fixed soon.
> >
> > "Derek Chan" wrote:
> >
> > > Hi,
> > >
> > > Specifying the language only determines the language the map is generated in
> > > and does not affect geocoding properties. Therefore what you are
> > > experiencing is not an error.
> > >
> > > Regards,
> > > --
> > > Infusion Development
> > > http://www.infusiondev.com
> > >
> > >
> > > "xshen" wrote:
> > >
> > > > We found that addresses returned from GetLocationInfo for the location in
> > > > Netherlands (lat=52.37552, lon=4.89289) are always the same no matter what
> > > > languages you specify (en, es, nl, de) while the returned places names are
> > > > translated in the corresponding language. Is it an error?
date: Mon, 15 Oct 2007 07:48:02 -0700
author: Steven Pushee
|
|
