Misspelling of new city name.

[Andre Tannus]

Hi everyone.

I've just updated my list of API Geotargets with the file available here:

https://developers.google.com/adwords/api/docs/appendix/geotargeting

It contains a new city record:

9047706,Assu,"Assu,State of Rio Grande do Norte,Brazil",20103,BR,City,Active

with the city is misspelled.

The correct spelling according to current portuguese spelling rules, IBGE, Wikipedia (despite the title) and even Google Maps is "Açu".

Perhaps there is a good reason (profuse use of the wrong spelling) for this decision, or perhaps it is a bug.

Is this the proper place to report such a thing?

Thanks in advance,
André.

[Nadine Sundquist (AdWords API Team)]

Hello André,

I have good news! It's not conflicting with Google Maps. I've attached a screenshot of the place in Google Maps. The place may have Açu, but if you look underneath it, you'll see that the official name that Google Maps is keying off of is the same as what you're seeing in API geotargets. You're probably wondering why this happens. If you look through the geotargets list, you'll see that everything is using ASCII. For example, you don't see Moscow in the Russian language, and you don't see Beijing in the Chinese language. The Açu spelling is considered to be in the local language with the 'ç' character in there. For geotargets, all the names are changed to match an ASCII standard for that location. I hope that clears that up for you!

Best,

Nadine Sundquist, AdWords API Team

P.S. I totally love that you cited Google Trends. Very cool!

[Andre Tannus]

I can't say I understand. Wouldn't 'Acu' be the ASCII version of 'Açu'? Or is there an effort to preserve phonetics?

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "AdWords API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/vbDzHzss7Xo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adwords-api+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.

To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/2eedf81e-f589-45e0-979c-4240853d2627%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

André Tannús | Epungo | +55 11 2389-4360

We are a layer

[Nadine Sundquist (AdWords API Team)]

Greetings André,

I would be glad to clarify! I can see how it would be confusing. The ç characters is considered an extended ASCII character already. It's just not a part of the original printable set. I first wanted to clarify that when I was talking about ASCII characters earlier in the thread. You're lucky that I'm interested in linguistics and travel because I happen to know the answer to this one. Yes, you are very likely correct in that it is trying to preserve phonetics. Many English speakers would not recognize the sound that this character would make, so I've observed it changes to an 's' or a 'ss' to help someone pronounce it correctly. That may not always be the case for every location in the world, but it definitely appears to be the case for this location.

Take care,

Nadine, AdWords API Team

[Andre Tannus]

Thanks for the clarification, Nadine.

André.

To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/8a3d2331-3e59-4a7a-af7f-7647206deb05%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.