In my experience, NULL is the least-supported UTF-8 character. Whenever software claims conformance, that's the first thing I check. Personally, I'd have prefe

In my experience, NULL is the least-supported UTF-8 character. Whenever software claims conformance, that's the first thing I check. Personally, I'd have preferred they disallowed it in the standard, but it's too late for that now. Anyone know why it was included (other than the obvious reason that it obeys the encoding rules)?