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
Kan ’n rolprent of TV-program nie vind nie? Teken aan om dit te skep.
Wil u hierdie item gradeer of tot ’n lys toevoeg?
Nie ’n lid nie?
Antwoord deur Travis Bell
op 18 November 2015 om 11:31 VM
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.
Antwoord deur Stephan Schück
op 19 November 2015 om 8:07 VM
Hi Travis
Thanks for the information.
Antwoord deur LordMike
op 19 November 2015 om 12:29 NM
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.
Antwoord deur Travis Bell
op 19 November 2015 om 12:49 NM
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.