Mr Black, thanks for the reply. Perhaps it is a semantic
distinction, whether the problem has to do with XMLFormat or the
encoding process. From my point of view, I epxect CF to handle it.
I have some "raw material", whether it's rows from a query or
text read in from a file, whatever. At some point, I decide "Yes,
put this string into the space between an opening and closing
element". I use the XMLFormat function to make the string
acceptable to the XML specification. I then have CF make the XML
document using the cfxml tag.
Whether I specify the encoding or not, I expect CF to create
a well-formed XML object. It should not be including "illegal"
characters, or being confused by them in any way.
In this case, I can pass the offending string to an OPTION
tag, or display it in a cfoutput block, use it in an SQL operation
via ODBC (actually, JDBC which is even more picky than ODBC), write
it to a text file, seemingly anything one can do with a string,
without problem. Except for putting it into an XML element.
I believe CF shouild handle this.