This whole thread doesn't make a lot of sense to me. If the DOM goes to
the trouble of converting ^L into &#12 why can't it also say, "&#12 will
never be parsable"? I guess I just don't understand why the DOM goes to
all the trouble to convert a character that it will never be able to
parse.

I also don't understand why it can't parse it. I could understand why a
DOM couldn't parse ^L, but why can't it put the &#12 back to a ^L? What
could be the confusion or ambiguity or performance issue with changing
it back?
-Robert


>Is XOM slow?  Is anyone out there complaining about it being so?  Not 
>trying to start an argument, just curious.
>
>Jake


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to