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
Nevari atrast filmu vai TV pārraidi? Jāpiesakās, lai to izveidotu.
Vēlies novērtēt šo vienumu vai pievienot to sarakstam?
Neesi dalībnieks?
Atbilde no Travis Bell
on novembris 18, 2015 at 11:31 AM
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.
Atbilde no Stephan Schück
on novembris 19, 2015 at 8:07 AM
Hi Travis
Thanks for the information.
Atbilde no LordMike
on novembris 19, 2015 at 12:29 PM
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.
Atbilde no Travis Bell
on novembris 19, 2015 at 12:49 PM
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.