I think another solution is an Unparsed node. When the XML is converted to a
string it will be outputed verbatim.
-
jackjack.wid...@gmail.com wrote:
Let's say source.body is ahref=google.comSearch/a. If I put
source.body in a span like this -
On Tue, Oct 20, 2009 at 10:16 PM, jack jack.wid...@gmail.com wrote:
OK, I see why this is happening. the {exp} in the NodeSeq convert exp
to a String. So I did by creating a string and then converting it to a
NodeSeq at the end. Is there a way to do this without using and
intermediary
Let's say source.body is ahref=google.comSearch/a. If I put
source.body in a span like this -
span{source.body}/span
source.body will be converted to text and the actual link tags will be
displayed. What is the right way to do this?
On Oct 21, 9:06 am, David Pollak
On Wed, Oct 21, 2009 at 6:32 AM, jack jack.wid...@gmail.com wrote:
Let's say source.body is ahref=google.comSearch/a. If I put
source.body in a span like this -
span{source.body}/span
source.body will be converted to text and the actual link tags will be
displayed. What is the right way
Oops. I just noticed I made source.body a String and not a NodeSeq.
Sometimes source.body is text with html tags in it. Like -
Hey dude, bwhat/b are you doing?
I guess I should make it a NodeSeq. Sorry about that.
Jack
On Wed, Oct 21, 2009 at 9:33 AM, David Pollak feeder.of.the.be...@gmail.com
Like David said, be very careful about using NodeSeqs if you're taking
user-generated content, since that can lead directly to cross-site scripting
attacks and other nastiness.
Derek
On Wed, Oct 21, 2009 at 7:41 AM, Jack Widman jack.wid...@gmail.com wrote:
Oops. I just noticed I made
