What is the standard for API results? Encoded or decoded HTML tags?
This one has an decoded german title (&), but a encoded plot (amp): http://api.themoviedb.org/3/movie/168259?api_key=#####&language=de
Un film, une émission télévisée ou un artiste est introuvable ? Connectez-vous afin de créer une nouvelle fiche.
Vous souhaitez évaluer ou ajouter cet élément à une liste ?
Pas encore membre ?
Réponse de Travis Bell
le 18 novembre 2015 à 11h31
Hi Stephan,
Overviews have special treatment done to them in order to strip all of the garbage text that often gets entered. I guess this process encodes HTML entities. It is the only field that has this done, so titles will always be raw values.
Réponse de Stephan Schück
le 19 novembre 2015 à 08h07
Hi Travis
Thanks for the information.
Réponse de LordMike
le 19 novembre 2015 à 12h29
Travis, wouldn't it be in the best interest /not/ to encode anything on its way in to the database? Normally, data is encoded on its way in to a presentation...
This in general avoids double-encoding.
Réponse de Travis Bell
le 19 novembre 2015 à 12h49
Hey Mike,
If there is ever a v4, yes, this would change and be how it gets returned but at this point there's too many clients expecting the data back in the current format. I don't like to make to data changes if I don't have to. It's been this way since 2012 (when v3 launched) so I will leave it be for now.