--- In [email protected], "Amy" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "Amy" <amyblankenship@> 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="<TEXTFORMAT LEADING="2"><P > > > ALIGN="LEFT"><FONT FACE="Helvetica" > > > SIZE="14" COLOR="#0B333C" > > > LETTERSPACING="0" KERNING="0"><B>West to > > > Atlanta</B><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?
Update 2: I replaced all "<" in the XML with "<" when passing them through the ExternalInterface, and that prevented the line breaks from being added _before_ the XML function got hold of the string. However, when I used the XML function, the line breaks were added again. Any ideas? -Amy
