(2013-06-05, 00:42:04)shawn_a Wrote: No it is not.
So explain what this does, and what problem it fixes, or is it a move towards more standardized data, we use cdata in xml now, so stripslashes is no longer required either. Does this mean we would have to do some encoding on output that we might not be already? Or perhaps decoding we are already doing might have to be removed ?
There's no crushing argument for that.
Some advanced users propounded to store special chars without encoding into entities. Mostly for SEO purposes. But yeah, there were problems with stripslashes afair until GS3.0.
If anyone wants to get some xml data from page files, decoding entities is of course a must, as chars like "< in html tags are encoded anyway (I'm not sure if it's a GS or simplexml lib manner). Thus I assume that language specific chars are also processed with or without converting them by CKE.
I can say that I did not focus on what is being saved in .xml files for long time, as I'm adding some options to CKE's config right after installing GS. It's about CKE 4.1 that got a huge update, and I had to look a bit deeper into it to get rid of some of its irritating behaviours at last. Those which should be default, like line breaks you pointed earlier. But tbh. if one wants to get a beatifuly formatted code, one condition is not enough, and final result depends on many factors, on which most people don't give a single buck.
I think I'm somewhat a html purist.
Addons: blue business theme, Online Visitors, Notepad