Right. My understanding increases bit by bit.
I’m using response/xexpr, which — unlike your xexpr->html — doesn’t
special-case script and style tags. Funny, I had read through your txexpr docs,
but the special-casing of script and style didn’t jump out at me at the time,
and I had forgotten it by the time I needed it.
cdata it is. Thanks to people like you, Racket does what I need, as usual. The
problem is I don’t always know what I need.
> On Sep 19, 2017, at 4:53 PM, Matthew Butterick <m...@mbtype.com> wrote:
>> On Sep 19, 2017, at 1:36 PM, Byron Davies <byrondav...@starshine.us
>> <mailto:byrondav...@starshine.us>> wrote:
>> In strings, xexpr->xml converts "<>&” into <, etc. I’m sure this was
>> does not grok the transformed text “i < n”. I tried workarounds for as
>> long as I could (e.g, using the “for key in lst” style of loops), but I
>> reached the end of the line when I wanted to change the contents of a table
>> cell using “cell.innerHTML = ‘<div …>’.
> HTML ≠ XML. You probably want `xexpr->html`. 
> `script` and `style` blocks in HTML aren't declared as CDATA because they're
> already deemed to be CDATA. 
> But in XML, they have no special status. Therefore, `xexpr->xml` is not
> merely "well-intentioned" — it's doing what it promises.
>  https://www.w3.org/TR/html4/types.html#h-6.2
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.