self-synchronizing

The same is true of UTF-8 because it is self-synchronizing.

While CFB can be considered a self-synchronizing stream cipher, OFB is a typical synchronous stream cipher.

But note that UTF-8 is self-synchronizing, so no encoding of one character contains the encoding of another as a subsequence.

In 10G ethernet phy's, it's a multiplicative (self-synchronizing) scramblers [1] and does not use line code.

Obviously not as good as UTF-8 or UTF-16 which are self-synchronizing, but it can be implemented efficiently and cut encoding size.

The exception is finding the midpoint, which should be provided as an API function (bisect?) that takes the midpoint in bytes and then uses UTF-8's self-synchronizing property to find the nearest legal codepoint.

That’s roughly how UTF-8 works, with some tweaks to make it self-synchronizing.

Furthermore, it's a practical requirement of Unicode that all encodings be self-synchronizing.

So I’m contrasting this to things that are self-synchronizing or which allow processing chunks in isolation.

I think this just goes to illustrate that not only are non-self-synchronizing instruction sets bad for decoding, they're also bad for security.

Watch this video of metronomes self-synchronizing.[1] That's a pervasive phenomenon.

Unfortunately this isn't quite self-synchronizing in the world we currently live in.

This is referred to as UTF-8 being "self-synchronizing".

It's pretty good, Wikipedia has a brief section explaining how Ken Thompson for example made it self-synchronizing, which seems like a "duh" feature today but the concept before Ken touched it didn't have this.