LiveDocs Comments - coldfusion - 6.1 - htmldocs - funca110.htm

coldfusion/6.1/htmldocs/funca110.htm

TacoBell — 2004-12-16T14:31:41

When I call toStirng() on a valid XML document that contains

it converts it to
whats up with that? I did not tell it I wanted HTML..
I'm still trying to find a way to overcome this huge problem.

coldfusion/6.1/htmldocs/funca110.htm

clinecorp — 2004-06-25T17:51:13

when an XML object is dumped using toString(), all ' entity values are replaced with single quotes ('). This is undesirable behaviour as it creates a technically invalid XML document and confuses those trying to keep XML specific chars as entities within the database.

coldfusion/6.1/htmldocs/funca110.htm

Iceborer — 2004-06-17T08:17:27

When converting an XML document object using toString, I cannot specify encoding (apparently an XML Doc is not considered a binary object). Because of this I run into the following issue:

results in a file which has an XML header specifying UTF-8 enconding
()
in which all of the data is written in UTF-16

00000000h: FF FE 3C 00 3F 00 78 00 6D 00 6C 00 20 00 76 00 ; ÿþ<.?.x.m.l. .v.

If I can't specify an encoding when I toString an XML Doc, how do I fix this?

coldfusion/6.1/htmldocs/funca110.htm

halL — 2003-09-05T14:25:23

The current version of the documentation is missing the following:

You can use the Encoding parameter only when you convert binary data to string data.
If you specify an encoding when you convert any other type of data to a string, ToString generates an error.

Explanation:
When converting binary data to a string, the internal conversion routine must know the original textual encoding of the data so that it can properly transform it to a ColdFusion (actually Java) internal string representation, which is encoded in UTF-16.
For example, if binary data represents ISO 8859-1 (8 bit) characters, the conversion routine must convert and expand each 8-bit byte into a 16-bit UTF-16 character,
whereas if the binary data represents UTF-16, no conversion is necessary (other than removing any byte order mark).
When converting non-binary data, the data format is already known, so specifying the original encoding is not appropriate