Поддержка The Movie Database
Поддержка → Поддержка API
Why query with two-letter language code returns different result then four-letter ones?
опубликовано GregSTAFFMOD, 26 февраля 2017 в 03:33
Let's use https://www.themoviedb.org/tv/65249 as example.
- Query: https://api.themoviedb.org/3/tv/65249/season/1/episode/1?api_key=key&language=en
- Episode Name: "Flashing Before My Eyes"
- OK
- Query: https://api.themoviedb.org/3/tv/65249/season/1/episode/1?api_key=key&language=en-US
- Episode Name: "Flashing Before My Eyes"
- OK
- Query: https://api.themoviedb.org/3/tv/65249/season/1/episode/1?api_key=key&language=zh-CN
- Episode Name: "走马灯"
- OK
- Query: https://api.themoviedb.org/3/tv/65249/season/1/episode/1?api_key=key&language=zh-HK
- Episode Name: "走马灯"
- OK
- Query: https://api.themoviedb.org/3/tv/65249/season/1/episode/1?api_key=key&language=zh-TW
- Episode Name: ""
- OK, since there is no record for
zh-TW
- Query: https://api.themoviedb.org/3/tv/65249/season/1/episode/1?api_key=key&language=zh
- Episode Name: "Episode 1"
- WHY?
I cannot think of where could the API get the "Episode 1" value. I also don't know how to correct it, since we only support four-letter language+country code. Shouldn't we just fallback two-letter language code to the closest match?
This particular issue affects Plex TMDb agent since Plex only has setting for language, but not country. So their queries to TMDb use two-letter language code. As the result, I found the data I added in Mandarin (zh-CN) does not reflects in my Plex db 
.
Ответ от Greg
, 28 февраля 2017 в 12:55
Anybody?
Ответ от Travis Bell
, 1 марта 2017 в 18:48
The fallback data you were seeing was because there was a translation created but the data was empty. The data is now showing correctly of course, because the translation was filled in.
Ответ от Greg
, 2 марта 2017 в 03:03
@travisbell could any one create a translation for "zh" without country code?
Ответ от Travis Bell
, 2 марта 2017 в 10:34
zhdefaults tozh-CN. But I think it's the same thing I mentioned above.zhwas cached on the API already so when you did your investigating, you were getting data from before you made your edits.zh-CNwas not cached so you saw the correct data right away.Ответ от Greg
, 3 марта 2017 в 15:20
@travisbell gotcha, so it is basically cache delay. The API result looks good now. However my Plex server is still not picking up the right data
. Will have to debug more there. Thanks for explaining it!