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
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por Travis Bell
el 18 de noviembre de 2015 a las 11:31
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.
Contestado por Stephan Schück
el 19 de noviembre de 2015 a las 08:07
Hi Travis
Thanks for the information.
Contestado por LordMike
el 19 de noviembre de 2015 a las 12:29
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.
Contestado por Travis Bell
el 19 de noviembre de 2015 a las 12:49
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.