Hey, I'm confused about the behavior of the "translations" on the site. I'm looking at the following movie entry which has a "title" for en-US and ta-IN as shown on the website.
If I'm looking at the API response the "ta-IN" object actually has no "title" set:
"translations": {
"translations": [
{
"iso_3166_1": "US",
"iso_639_1": "en",
"name": "English",
"english_name": "English",
"data": {
"homepage": "",
"overview": "For Kathiravan, who lost his left leg in an accident,his 8-year-old daughter is his world. She is diagnosed with a congenital heart problem and 7 Million INR is needed to save his daughter. Unable to raise such a huge amount, he plans to kidnap businessman Rudra's daughter. Instead Kathir becomes embroiled in his own kidnapping plot.",
"runtime": 117,
"tagline": "",
"title": "Poikkal Kuthirai"
}
},
{
"iso_3166_1": "IN",
"iso_639_1": "ta",
"name": "தமிழ்",
"english_name": "Tamil",
"data": {
"homepage": "",
"overview": "",
"runtime": 0,
"tagline": "",
"title": ""
}
}
]
}
My guess is that the website somehow has a fallback based on the data in the "original_title" field, and as original_language matches the object in the "translations" array it falls back to that.
"original_language": "ta",
"original_title": "பொய்க்கால் குதிரை",
Is this the correct assumption? Is that a bug or expected behaviour? I think it would be less confusing if the API response resembles what's on the website, but I might be missing some complexity there.
Thanks!
찾으시는 영화나 TV 프로그램이 없나요? 로그인 하셔서 직접 만들어주세요.
이 항목을 평가하거나 목록에 추가할까요?
회원이 아닌가요?
Travis Bell님의 댓글
11월 29, 2023 at 11:19 오전
Hi @clapton, on the API this is expected. We do not support fallback queries on the API at this time.
We have an open ticket to think about adding this here.
With regards to the original title, you'll have to look at the "primary info" data to glean that right now. The website tries to infer the connection, but it's not stored in the DB that way, which is what is being returned on the API.