Hello, first of all, thanks for your great service! Is there any way to get all the movie titles in every language using the API (i mean any other way rather than specifying "language='XXXX'" for every language)? It seems people are manually adding language specific titles in the "alternate_title" field, but I think the "alternate_title" should be a good place to list all the movie titles in every language, pretty much like IMDB is doing with the "AKA" table: http://www.imdb.com/title/tt2310332/releaseinfo/#akas
找不到电影或节目?登录并创建它吧。
Travis Bell 的回复
于 2015 年 01 月 19 日 2:12下午
Hi Gabriele,
There's 3 types of title fields.
ISO-639-1
field. It will get returned alongside theoriginal_title
field in all results.Alternative titles. These titles are added and attached to countries. They can be called via the
/alternative_titles
method.https://api.themoviedb.org/3/movie/550/alternative_titles?api_key=###
Or include them in your main query with
append_to_response
:Cheers.
Gabriele 的回复
于 2015 年 01 月 19 日 2:20下午
thanks travis, but still, it seems there's no way to retrieve every "translated title" with a single api query, which would be very useful:
I'd like something like https://api.themoviedb.org/3/movie/550?api_key=###&language=all that would return the original title, together with a list of ALL translated titles, one entry per language, each line attached with the ISO-639-1 field, this isn't possible right now correct?
Travis Bell 的回复
于 2015 年 01 月 19 日 2:23下午
Ah, I see what you meant. Sorry, I missed that in your original question.
I'm not sure I would ever make that possible or not. You can call
/translations
right now which will at least show what translations have been created, but it doesn't currently return the titles. I will think about this for sure, thanks for the heads up.Gabriele 的回复
于 2015 年 01 月 19 日 3:00下午
ok thanks! It would really be useful, if you look at it, many people now (including me) are editing the movies and adding title translation to the "alternative title" field
pr0j3ctx 的回复
于 2015 年 01 月 28 日 4:32上午
Hi. I think this feature would be great, too. Also If I call http://api.themoviedb.org/3/movie/tt0230011?api_key=XXX&append_to_response=alternative_titles There are no german / austrian Titile
The german title is under translated and the austrian under alternative Titles. The Api call didn´t list one of them.
Gabriele 的回复
于 2015 年 01 月 29 日 2:52上午
Townes, you're doing the right thing, I didn't get the difference between alternative titles and "translations" and many software that use themoviedb apis only extract the original title and the alternative titles, adding translations to the alternative titles was the only way to have them show other title languages. Of course that's other software's fault, but since the only option is to issue an api call to get a list of all available translations + issue additional api queries, one for each translation, you can understand that it isn't a viable solution since it's way too slow for the other software. Hence my request to have a way to get, with a single "movie.get" query, the full list of translated titles, this could very well be an extension to the "append_to_response=translations" api parameter, but where the "translation" returns, together with the ISO-639-1 field, the actual translated title for that language.
Travis Bell 的回复
于 2015 年 01 月 29 日 9:58上午
Keep in mind that there's a few more things that change by using the
language
param in your API call.Not only does it change the title field (if a translated title is present) but it also grabs the poster for that language (if one is present) as well as the overview. Most of our users use the
language
param to get the these 3 pieces of data. And eventually, when we tie the proper IETF codes together, we'll be returning the proper release date as well.Gabriele 的回复
于 2015 年 01 月 29 日 2:12下午
this is to say, one more reason to implement the title translations api parameter? :-)
clapton 的回复
于 2016 年 06 月 17 日 4:44上午
This would be really useful, I was surprised to see that a title showed up in japanese if I request it with
language=ja
but didn't show up in thealternative_titles
if I request it withlanguage=en
agrmbl 的回复
于 2016 年 06 月 17 日 5:46下午
Just my 2 cents, it seems to be related to https://www.themoviedb.org/talk/57582aad92514130700016c0, Travis added it to icebox here: https://tmdb.lighthouseapp.com/projects/83077-api/tickets/531
Getting available translations for title in one request would be awesome (not mentioning that for many Russian movies originalTitle is transliterated and originalLanguage is "en", go figure).
And indeed many people use alternativeTitle for title translations (it's accessible in API after all). Doing 10-20 API calls to get different titles for a single movie (not mentioning that you don't easily know which langs are available) would be way too heavy.
letterboxd 的回复
于 2016 年 11 月 01 日 7:10下午
@agrmbl it does seem to be available with
append_to_response=translations
, e.g.letterboxd 的回复
于 2016 年 11 月 01 日 7:11下午
However, it is surprising that some translated titles appear in the
alternative_titles
but these are unlikely to contain the "official" translated title, e.g. the Japanese film "Gyakufunsha kazoku" has a Germanalternative_title
:...but the official German name for the film ("Die Familie mit dem umgekehrten Düsenantrieb") is only found in the
title
field when using&language=de
.letterboxd 的回复
于 2016 年 11 月 01 日 7:21下午
For completeness, I'll just add that this thread is a duplicate of both https://www.themoviedb.org/talk/531da443c3a3685c3700831f and https://www.themoviedb.org/talk/51c83c27760ee36f011e414e
Travis Bell 的回复
于 2016 年 11 月 01 日 8:08下午
Hey there,
This post might also be of some use. The short and sweet of it is that alternative titles more or less, have nothing to do with translations. There will no doubt be some overlap because not every movie only has a single translated title but the "official translated" title should go in the translation, everything else (mis-spelling, stylized versions, alternative names in general) should go in alternatives.
If there's a case of this that is wrong, it's probably just a bad data issue and needs to be corrected.