default text - need formatting/parsing?

When I invoke FCKEditor with some default text (I'm using the ColdFusion CFC - fckEditor.value) it displays fine.

BUT: if there is an "@" symbol in the text, the editor basically craps itself.

Internet Explorer 6.0.2900.2180.xpsp_sp2_rtm.040803-2158 (phew!) produces two errors:

Line 22, Char 1233
Error: This name may not contain the '@' character:
test-->@<--test.com
Code: 0

Line 24, Char 964
Error: Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus.
Code: 0

FireFox Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041005 Firefox/0.10.1

Error: uncaught exception: [Exception... "String contains an invalid character" code: "5" nsresult: "0x80530005 (NS_ERROR_DOM_INVALID_CHARACTER_ERR)" location: "http://192.168.0.169:8500/fckeditor/editor/js/fckeditorcode_gecko_1.js Line: 21"]

The invoke:

The HTML output:

<div>
<input type="hidden" id="emailBody" name="emailBody" value="&lt;pre&gt;
------------ Original Message From : tony hoad &lt;test@test.com&gt; ------------

Hi
Please
advise how to get the right forms up to proceed
&lt;/pre&gt;" />

<input type="hidden" id="emailBody___Config" value="" />
<iframe id="emailBody___Frame" src="../../fckeditor/editor/fckeditor.html?InstanceName=emailBody&Toolbar=Default" width="650" height="400" frameborder="no" scrolling="no"></iframe>
</div>

<cfscript>
fckEditor = createObject("component", "core.fckeditor");
fckEditor.instanceName = "emailBody";
fckEditor.basePath = "../../fckeditor";
fckEditor.width = 650;
fckEditor.height = 400;
if (url.process NEQ ""){
if (isDefined("emailMsg.htmlBody") and emailMsg.htmlBody NEQ ""){
fckEditor.value = htmlForwardingText;
} else if (isDefined("emailMsg.textBody") and emailMsg.textBody NEQ "") {
fckEditor.value = textForwardingText;
}
}
fckEditor.create(); // create the editor.
</cfscript>


My question: does the "loaded" text/html when the editor is invoked have to be parsed in any way? AFAIK, @ is not a special HTML entity.

If not, should I file this as a bug? Any chance of an urgent patch?