Hello!
I'm seeing another error when extracting the translated information.
When the information is requested in Spanish (Spain) it is obtained correctly. https://api.themoviedb.org/3/tv/30984/season/1/episode/1?api_key=THE_KEY&&language=es-es
{ "episode_number": 1, "name": "El día que me convertí en Shinigami", "overview": "Ichigo Kurosaki es un chico de 15 años que puede ver espíritus. Intentando proteger el espíritu de una niña pequeña de un hollow, tiene un encuentro con un espíritu malvado y una shinigami. Después Ichigo Kurosaki encuentra a la chica en su habitación, ella se presenta como Rukia Kuchiki, y explica el objetivo de los shinigami. El hollow vuelve y deja a Rukia Kuchiki herida, para salvar a la familia de Ichigo Rukia le traspasa sus poderes y así se convierte en un shinigami.", }
But when it is obtained in Spanish (Mexico), the name and overview are not loaded. https://api.themoviedb.org/3/tv/30984/season/1/episode/1?api_key=THE_KEY&&language=es-mx
{ "episode_number": 1, "name": "Episodio 1", "overview": "", }
The website says that if the name is the same as Spanish (Spain) it should be left blank, but I see that the blank space is automatically replaced with: "Episode ##" by the system. And this is what the API is returning
找不到电影或节目?登录并创建它吧。
superboy97 的回复
于 2024 年 09 月 17 日 12:40下午
The fallback language is not yet working on the API. That mean that currently, if you receive this result, you should manually redo the query with es-ES.
By the way, correct queries are es-ES and es-MX instead of es-es and es-mx. The country code should always be in capital letters.
jorensanbar 的回复
于 2024 年 09 月 17 日 12:47下午
I see that the page includes a new language: Spanish - Argentina.
If you call the API with this language, the information for spanish (Spain) is returned.
https://api.themoviedb.org/3/tv/30984/season/1/episode/1?api_key=THE_KEY&&language=es-AR
{ "episode_number": 1, "name": "El día que me convertí en Shinigami", "overview": "Ichigo Kurosaki es un chico de 15 años que puede ver espíritus. Intentando proteger el espíritu de una niña pequeña de un hollow, tiene un encuentro con un espíritu malvado y una shinigami. Después Ichigo Kurosaki encuentra a la chica en su habitación, ella se presenta como Rukia Kuchiki, y explica el objetivo de los shinigami. El hollow vuelve y deja a Rukia Kuchiki herida, para salvar a la familia de Ichigo Rukia le traspasa sus poderes y así se convierte en un shinigami.", }
So if it works to return information from a native language, why doesn't it do this with es-MX?
superboy97 的回复
于 2024 年 09 月 17 日 12:52下午
Did you try with es-MX ? In your first message, you have written es-mx in your query.
jorensanbar 的回复
于 2024 年 09 月 17 日 12:55下午
Yes, return Name: Episodio 1 and empty Overview.
superboy97 的回复
于 2024 年 09 月 17 日 1:04下午
This query is wrong as it is written with "&&" instead of "&". So, I'm not sure which language is taken in account.
Note : I don't see an es-AR language on that page.
jorensanbar 的回复
于 2024 年 09 月 17 日 1:14下午
In the main settings: Spanish (Argentina)
https://api.themoviedb.org/3/tv/30984/season/1/episode/1?api_key=THE_KEY&language=es-AR Call the API with es-AR language return Spanish-Spain information: es-ES return
https://api.themoviedb.org/3/tv/30984/season/1/episode/1?api_key=THE_KEY&language=es-MX Call the API with es-MX language return empty values: es-MX return
superboy97 的回复
于 2024 年 09 月 17 日 1:23下午
This dropbox is not the language in which the series is available, but the language in which you can see the website.
The languages available for the series are the ones listed in the first dropbox, above this one, as visible in my screenshot.
Consequently :
jorensanbar 的回复
于 2024 年 09 月 17 日 1:48下午
:( So the solution would be to load the database and copy the information from es-ES to es-MX, so that the API can return the correct information. At least the name, as the other values can be obtained from other places like TVDB
superboy97 的回复
于 2024 年 09 月 17 日 1:52下午
No, as the data stored in the database are correct. This is purely an API problem.
The correct solution, as long as the fallback is not working correctly on the server side of the API, is to manage the fallback on the client side of the API as this is done by other applications.