Latin1 was the early default character set for encoding documents delivered via HTTP for MIME types beginning with /text . Today, only around only 1.1% of websites on the internet use the encoding, along with some older applications. However, it is still the most popular single-byte character encoding scheme in use today. A funny thing about Latin1 encoding is that it maps every byte from 0 to 255 to a valid character. This means that literally any sequence of bytes can be interpreted as a valid string. The main drawback is that it only supports characters from Western European languages. The same is not true for UTF8. Unlike Latin1, UTF8 supports a vastly broader range of characters from different languages and scripts. But as a consequence, not every byte sequence is valid. This fact is due to UTF8's added complexity, using multi-byte sequences for characters beyond the general ASCII range. This is also why you can't just throw any sequence of bytes at it and ex...
Lately, I've been tightening my own personal feedback loops. And working out. I've also been thinking about how sometimes it can be positive to forget things. For example, I've been almost entirely abstinent from alcohol so long now that I can't remember exactly when I first stopped drinking. Maybe it was three or four years ago? I've also spent a lot of time thinking about the quality of habits. A few weeks ago, my mind handed me a big thought—that how we do one thing tends to become how we do everything. I'd like to close out the year by continuing to stay in shape, working on more software, and publishing some new security research about operating systems and browsers.
Comments
Post a Comment