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.
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...
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.
Travis Bell 的回复
于 2015 年 11 月 18 日 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.
Stephan Schück 的回复
于 2015 年 11 月 19 日 8:07上午
Hi Travis
Thanks for the information.
LordMike 的回复
于 2015 年 11 月 19 日 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.
Travis Bell 的回复
于 2015 年 11 月 19 日 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.