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
Non podes atopar unha película ou serie? Inicia sesión para creala.
Queres valorar ou engadir o elemento a unha listaxe?
Non es membro?
Resposta de Travis Bell
no 18 de novembro do 2015 ás 11:31AM
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.
Resposta de Stephan Schück
no 19 de novembro do 2015 ás 8:07AM
Hi Travis
Thanks for the information.
Resposta de LordMike
no 19 de novembro do 2015 ás 12:29PM
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.
Resposta de Travis Bell
no 19 de novembro do 2015 ás 12:49PM
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.