|
If I make the following request with the Russian realm and Russian character:
http://eu.battle.net/api/wow/character/cвежеватель-душ/Фриттерус It returns the English localized realm name in the data. Seems like a bug, but maybe that was intended. Fortunately I translated all the realm names a few years ago in our database for display purposes so correcting the look ups on our end is not difficult. |
|
|
Edited by Azxiana on 1/2/12 10:06 AM (PST)
Same thing for the teams.
http://eu.battle.net/api/wow/arena/cвежеватель-душ/3v3/mесто-для-вашей-рекламы/ |
|
Try the realm with the locale parameter at the end.
Eg: http://eu.battle.net/api/wow/character/howling-fjord/Оливин?locale=ru_RU |
|
|
Edited by Azxiana on 1/2/12 1:01 PM (PST)
Try the realm with the locale parameter at the end. Only if that was consistent would that be useful... http://eu.battle.net/api/wow/character/culte-de-la-rive-noire/sounya?locale=en_US Culte de la Rive noire returns French all the time. |
|
I came across that the other day and discovered some dupes in my DB. Ended up just dropping anyone with a Russian realm name after queuing them for an update, then storing the English name.
|
|
|
Personally I don't use Russian, Korean, or Taiwanese characters in my realm slugs for API requests, so I can't reproduce the problem you're having.
|
|
if this is a guild name, charactor name, team name or realm name it is not translated in a locale return only locals on a given battle.net realm can be used .. you cant get russion on the us.battle.net so it returns english and so on so on |
|
Wasn't there a note somewhere saying that all the Russian realm names had been translated into English?
Note a reference but someone referencing it: http://us.battle.net/wow/en/forum/topic/3657285639 |
|
|
that is in realmstatus you can use the slug name if you choose..
|
Web & Mobile Team
|
Unless I'm not understanding something correctly, this is working as intended. The API doesn't do any sort of language detection to translate requests into one language or another based on where the character is. The only way you'll get back RU is to explicitly request it as Lunarhawk stated.
As for the url in the example, Ulminia is correct in pointing out that the character name is in french and won't/can't be translated. http://eu.battle.net/api/wow/character/culte-de-la-rive-noire/sounya?fields=items http://eu.battle.net/api/wow/character/culte-de-la-rive-noire/sounya?fields=items&locale=fr_FR |
#10
1/3/2012
|
|
|
Unless I'm not understanding something correctly, this is working as intended. The API doesn't do any sort of language detection to translate requests into one language or another based on where the character is. The only way you'll get back RU is to explicitly request it as Lunarhawk stated. I am referring to the realm names returned in the JSON data only. If you do not specify a language, taking whatever the default is, you get an English realm name when requesting information from a Russian realm. However, when requesting information from a French realm, you get the French name. On the other side of that, if you specify English when requesting a Russian realm, you do get English realm name. However, when specifying English with a French realm you still get the French realm name. So there are some inconsistencies in what data is returned. |
|
Edited by Kaelum on 1/7/12 8:04 PM (PST)
As stated my others, each region server has a specific set of languages (locales) that it supports. The European server does not support US English (en_US), it only supports UK English (en_GB), which is why en_US does not work. Since you are getting French back when using en_US, I would guess that French is the default locale for that server. Prior to the first release of my client (openSourceC.WorldOfWarcraft), I created the following mapping, which allows my client to validate locales:
<regions default="us">
|
