The UTF-8 bytes have decoded back to our original string. This is because the UTF-8
encoding supports the E-acute character, and it does so by inserting two bytes into the
array: 195 137.
On the other hand, our ASCII bytes have been decoded and we see that the first char-
acter has become a question mark.
If you look at the encoded bytes, you’ll see that the first byte is 63, which (if you look
it up in an ASCII table somewhere) corresponds to the question mark character. So this
isn’t the fault of the decoder. The encoder, when faced with a character it didn’t un-
derstand, inserted a question mark.
---->
The UTF-8 bytes have decoded back to our original string. This is because the UTF-8 encoding supports the E-acute character, and it does so by inserting two bytes into the array: 195 137. On the other hand, our ASCII bytes have been decoded and we see that the first character has become a question mark. If you look at the encoded bytes, you’ll see that the first byte is 63, which (if you look it up in an ASCII table somewhere) corresponds to the question mark character. So this isn’t the fault of the decoder. The encoder, when faced with a character it didn’t understand, inserted a question mark.
