Thread

derek,

i think you got the answer i had been looking for the whole day… i just want to clarify….

so you are saying that this is a NORMAL behavior for EE, even with my installation, and that i actually did not screw something up on my end with the database?

also, as a general rule, i should always use xml_encode with protect_entities=“yes” parameter for titles (and other data fields) where i anticipate that there will be symbols such as & ” and so on…

is this right?

regardless, props to lisa! go, lisa, go! the goddess of EE!

Thanks, P.J. - but it’s really Derek that did all the work here. =)

Yes, this is normal intended behavior for the parsing of the {title} variable, as well as the XML conversion method.  The difference in whether the & conversion in entities is desirable or not comes from how the information will be used.  For visual display in a feed reader or browser, chances are that you do not want it converted, even though most readers will convert and interpret it for you anyway (as Lisa was seeing in Safari 3).  For transporting the data, however, the “double” conversion is desired, so that for instance, when interpreted after being read, … does not get lost and turned into …