23:26 <mort___> Drup: there? got another tyxml question…

23:31 <Drup> mort___: just ask :p

23:31 <mort___> ah was just filing issue :)

23:32 <mort___> i want to inline some javascript

23:32 <mort___> inside <script> tags

23:32 <mort___> which I think means i just put <![CDATA[ … ]]> around it

23:32 <mort___> but if i do that, chromium complains about an unexpected <

23:32 <mort___> so i then think i should // comment out the <![CDATA[ and ]]> lines

23:32 <mort___> but i can't see how

23:32 <mort___> any suggestions? :)

23:33 <mort___> Xml.comment and Html.cdata both take strings so can't be combined directly, i think

23:34 <Drup> not sure why you need the CDATA thingy

23:34 <mort___> because otherwise the script characters seem to get parsed

23:34 <mort___> and so < turns into &lt; and so on

23:34 <mort___> which doesn't make javascript happy

23:35 <mort___> sorry, that's not quite right

23:35 <mort___> i mean — how do i pass a string to `script`? it seems i need to convert to an elt via either pcdata (turns < into &lt; etc) or cdata (doesn't but triggers the unexpected < error)

23:37 <Drup> Html.Unsafe.data ? :p

23:37 <mort___> aha

23:38 <Drup> script elements are a bit weird, I don't remember if there is special handling for them

23:38 <mort___> whee that works

23:38 <mort___> thanks :)

23:38 <mort___> i think the usual idiom is either nothing (via unsafe as you just suggested) or to add script comments around the CDATA markers

23:39 <Drup> I see