I know I'm probably asking something obvious, but this whole Unicode area is something I haven't paid much attention to.
What I'm asking is, what's the harm in escaping Unicode characters everywhere, whether in string literals or not? Doing so will also escape those in string literals. And this can be done without parsing, and so even when a parser is absent. On Wed, Jun 12, 2013 at 7:42 AM, <[email protected]> wrote: > Interesting. So to recap: what I want to do is encode Unicode characters > *inside string literals* only. The parse tree rendering does this for me > for free; I just have to force it to happen when I see Unicode, which is > why I use the LIMIT_SRC regex. What would be the alternative? > > > https://codereview.appspot.**com/10205043/<https://codereview.appspot.com/10205043/> > > -- > > ---You received this message because you are subscribed to the Google > Groups "Google Caja Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > google-caja-discuss+**[email protected]<google-caja-discuss%[email protected]> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- Cheers, --MarkM -- --- You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
