If your format supports non-canonical encodings you're in for a bad time no matter what, so a whole lot of that simplicity is fake.
> And it also means you're dealing with three classes of byte now.
If you're working a byte at a time you're doing it wrong, unless you're re-syncing an invalid stream in which case it's as simple as a continuation bit (specifically, it's two continuation bits).
> If you're working a byte at a time you're doing it wrong, unless you're re-syncing an invalid stream
It's very relevant to explaining the encoding and it matters if you're worried that invalid bytes might exist. You can't just ignore the extra complexity.
Also if you're not working a byte at a time, that kind of implies you parsed the characters? In which case non-canonical encodings are a non-problem.
Unless you want to actually do anything with the string beyond decode a codepoint.
Non-canonical encodings make it difficult to do things without decoding, but you have bigger problems to deal with in that situation, and the non-canonical encodings don't make it much worse. Don't get into that situation!
Specifically, even with only canonical encodings, one and two byte characters can appear inside the encoding of two and three byte characters. You can't do anything byte-wise at all, unlike UTF-8. But you already said "If you're working a byte at a time you're doing it wrong" so I hope that's not too big of an issue?
Except when it's 1, because that's an invalid start, and except when it's 0, because that means the character is a single byte.
And it also means you're dealing with three classes of byte now.
Plus UTF-8 has more invalid encodings to deal with than a super-simple format.