Re: unescaped ampersands was: several messages

On Mon, 01 Jun 2009 20:39:56 +0100, Julian Reschke <julian.reschke@gmx.de>  
wrote:

> As far as I can tell, it increases the complexity of recipients that  
> choose only to support conforming documents.

Increase in complexity is minimal.

If you only support conforming documents, then you can simplify it to: "&"  
followed by something that's not entity should be treated as text. To do  
this you need to buffer at most 32 alphanumeric characters (that's length  
of longest entity name), so this shouldn't burden even streaming parsers  
with hard memory constraints.

Even if you happen to have HTML5-before-that-change parser that only  
supports conforming documents, you can "fix" them with:

perl -pe 's/&(?=[a-zA-Z0-9]+=)/&amp;/g'

-- 
regards, Kornel Lesinski

Received on Monday, 1 June 2009 20:34:26 UTC