Hi all! I don't know if this has been discussed before, I would like to report a new issue Some localizations are not working anymore
For example Using local "es" everything is working:
https://api.themoviedb.org/3/movie/340677?api_key=XXX&language=es
Using local "es-AR" I'm having the movie infos in English instead:
https://api.themoviedb.org/3/movie/340677?api_key=XXX&language=es-AR
Using local "es-ES" goes back to normal:
https://api.themoviedb.org/3/movie/340677?api_key=XXX&language=es-ES
I'm having many languages having the same issue.
The API docs seem unchanged, I'm using the standard ISO 639-1 language code.
Any help?
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by Travis Bell
on August 13, 2020 at 10:40 AM
Hi @Piplos,
es-AR
is not a valid translation here on TMDb. Why are you using that?Reply by Piplos
on August 13, 2020 at 12:51 PM
It's determined automatically by the user's locale. In this case it's an user in Argentina who speaks Spanish.
The point is it was correctly working until some weeks ago, then users began to complain about the content showing in English instead of their language (eg. Spanish, Russian, etc.)
I have to know if I have to fix this on client side (in this case I need a list of "allowed locales") or something else
Reply by ticao2 🇧🇷 pt-BR
on August 13, 2020 at 1:19 PM
This question interests me.
The program I use to make Scraper for my collection, MediaElch, is undergoing a redesign of the Movie Scraper interface.
If this rule change here at TMDb is final, it may be interesting for me to inform the programmer that there has been this change.
I have no idea if this will interfere, because I don't know what changes will be made to MediaElch.
MediaElch already uses this criterion to define the interface language based on the user's local language.
They may also want to use this criterion in defining the default language for Scraper.
Reply by Travis Bell
on August 13, 2020 at 2:07 PM
This list is available on the API here: https://developers.themoviedb.org/3/configuration/get-primary-translations
I'm not 100% sure what changed (I'll have to go digging) but none of this is new, I added this method over 3 years ago. I think I can assume the previous behaviour though. If you made a lookup for a translation that isn't official, it would have defaulted to the bare language lookup. What I mean by this is that
es-AR
would have defaulted back toes-ES
.Reply by Piplos
on August 15, 2020 at 1:49 PM
Hi @travisbell
I just realized the locales are working on some other API endpoints.
Example:
https://api.themoviedb.org/3/search/movie?query=it&api_key=XXX&language=es-AR
Here I'm using the same locale (
es-AR
) that doesn't work on the/movie/{movie_id}
endpoint.I don't know if there's some other endpoints involved, but it could be a start. When I search a movie, it correctly defaults the
es-AR
locale toes-ES
, but when I get the movie details it incorrectly defaults toen-US
.I can totally relate it's something happened recently, as I'm suddenly having a lot of complains from my users.
Reply by Qstick
on August 23, 2020 at 5:43 PM
Same, we’ve started seeing issues with localization on /movie/ endpoint with users. Seems like something definitely changed.
Reply by Travis Bell
on August 23, 2020 at 6:48 PM
Yes, and to confirm, what’s the language param you’re using?
Reply by Qstick
on August 23, 2020 at 7:48 PM
We just use the two digit iso code, maybe that doesn’t work anymore? Ex. fr
Reply by Travis Bell
on August 23, 2020 at 10:36 PM
I am not aware of any issues with a request to a language
fr
(as an example):Request
Response
Reply by Qstick
on August 23, 2020 at 11:33 PM
Thanks @travisbell, let me see if I can track down anything on our side.