Re: BOM ambiguity?

On Jul 13, 2012, at 4:54 PM, Stephan Stiller wrote:
> As an aside to the BOM discussion - something I've always been meaning to ask.
>
> So there is a BOM-ambiguity when a file starts with
> FF FE
> and then a couple of U+0000 characters, yes? Because this could be either UTF-16 or UTF-32 under little-endianness. Has this been pointed out and discussed beforehand?
>
> Because the set of BOMs in different encodings don't constitute a prefix-free code.

Isn't this why UTF-32 is forbidden for HTML 5?

-- 
John W Kennedy
Having switched to a Mac in disgust at Microsoft's combination of incompetence and criminality.