Meanwhile, my problem is solved. Receiving end found a free stored
procedure / function that decodes the R:BASE XML data very nicely.

Bill

(sent from Android mobile device)
On Apr 17, 2012 6:32 PM, "Lawrence Lustig" <[email protected]> wrote:

> <<
> I'm not sure why the CDATA section in this case is Base64 encoded since
> that would seem to be necessary only for a standard XML element (where the
> Base64 encoding would eliminate not only any non-ASCII characters but also
> the problematic symbols <, >, and &.
> >>
>
> I did a little more research.  The purpose of Base64 encoding the CDATA
> section is to eliminate the possibility that the VarChar data contains the
> string "]]>", which is the CDATA section terminator (and which would cause
> the XML file to be malformed).
> --
> Larry
>

Reply via email to