I've noticed that if I create a Radio field and enter text including an apostrophe in the Custom Field Content box, the value is being escaped when saved to the database and the backslash is then rendered on the frontend. So, for example, text to save to the database set in Custom Field Content as Lady's Watch will be saved as Lady\'s Watch and will be displayed as Lady\'s Watch on the frontend.
Hi, I think the main difference here is that radio field contents are expected to be stored as simple text for ease of filtering. For example, it would be more appropriate to store the contents of a radio field without capitalization or special characters so it is easier to compare those values when performing a custom search based on the radio field selection. That's why I always recommend using simple text characters and numbers in the values of a radio or select custom field - it makes filtering and sorting easier and more intuitive for the system. Otherwise you have to worry about escaped characters and so forth, which makes the filtering mechanism unnecessarily complex. The raw database values should be simple for this reason. That's my understanding of the difference here.
I can see why it makes sense to keep radio field values simple. Why though are apostrophes in those fields escaped when saved to the database but apostrophes in single and multiple line fields are not? (I'm not trying to build a case for the radio field behaviour to be changed, I'm just looking to understand).