So there is a BOM-ambiguity when a file starts with FF FEand 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.
Stephan