domingo, 27 de Janeiro de 2019 às 03:00:24 UTC, mightybyte escreveu: > > It seems like we could just change our definition of "looks like an > entity" to not require the semicolon. If any valid entity is a prefix of > the characters following the ampersand, then we would consider it > ambiguous. Do you think that would solve your problem? I don't see any > problem with this because it would still conform to the spec. > > I would accept a pull request implementing this. > Yes, I think this would solve it; what about just escaping "&" when immediately followed by alphabetic characters? This would avoid the need to explicitly list all legacy entities.
-- --- You received this message because you are subscribed to the Google Groups "Snap Framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to snap_framework+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
