--- In [email protected], "Amy" <[EMAIL PROTECTED]> wrote:
>
> --- In [email protected], "Tracy Spratt" <tspratt@> wrote:
> >
> > I am doing this successfully, by encoding the markup, and keeping 
> it in
> > an attribute(description, below).  
> > 
> > <dest category="Directions to Hotel" title="West to Atlanta"
> > mapimage="maps/Exit249B_Map.swf" 
> destimage="maps/DirectionsWest.swf" 
> > 
> >       description="&lt;TEXTFORMAT LEADING=&quot;2&quot;>&lt;P
> > ALIGN=&quot;LEFT&quot;>&lt;FONT FACE=&quot;Helvetica&quot;
> > SIZE=&quot;14&quot; COLOR=&quot;#0B333C&quot;
> > LETTERSPACING=&quot;0&quot; KERNING=&quot;0&quot;>&lt;B>West to
> > Atlanta&lt;/B>&lt;FONT ...
> 
> I can get it to work fine if I encode everything, as you have.  
> However, my users are not going to be able to encode special 
> characters and I don't want to get blamed if they make a mistake.  
I 
> thought this was what CDATA is supposed to be for, but it is pretty 
> useless if the XML function breaks the string around the tags.  I 
can 
> work with stripping the CDATA off before it gets to the screen, but 
I 
> can't know what line breaks were added by the XML function and 
which 
> were added by the user.  I'm sorry, but this seems like a huge bug 
to 
> me!

Update:

It looks like the line breaks are getting introduced when the text is 
passed through ExternalInterface, not when I use the XML function on 
the text that should still be a string at that point.  Any thoughts 
on how to get the ExternalInterface not to insert line breaks into my 
XML?

TIA;

Amy

Reply via email to